Marcus, I've worked on this this week: - I've fixed ReleaseTest.testUndeclared and RBInlineMethodFromComponentTest.testInlineEmptyComponentMethod - For all Metacello tests, the fix is available but Dale said: "I haven't released my changes yet ... once I'm satisfied with the the behavior on PharoCore1.2 (that's where I'm doing development) I now have to get the new version of Gofer ported to Squeak and GemStone before I can make the full release ... otherwise the tests will be failing on Squeak/GemStone ..." I think this is really problematic to wait for Squeak/GemStone but one way to go forward is to put them in #expectedFailures - For XML I can fix this tonight if Otto don't want / can do it. So there's only one failing test without fix awaiting: ReleaseTest.testObsoleteClasses. Guillermo and I had a look at it on Monday: GuilleP: Ok, obsoletes come from: ClassRenameFixTest seems to be creating an AutoGeneratedClassForTestingSystemChanges GuilleP: But I can't find the source of AnObsoleteMCMockClassG :( laurentlaffont: it comes from MCMockPackageInfo>>#classNames laurentlaffont: see also the comment in MCPackageTest>>#tearDown some work needed to fix this. But I agree that it seems few people care about 1.2. Sad, I like it far better than 1.1.1. Laurent. On Fri, Feb 25, 2011 at 1:18 PM, Marcus Denker <marcus.denker@inria.fr>wrote:
I personally thing if we ever want to release 1.2, we need to start to be more radical.
The XML package breaks the build? So let's remove it completely. Let's ship 1.2, but without all the packages that are problematic.
Same for any other package that has a failing test.
Marcus
On Feb 25, 2011, at 1:12 PM, Torsten Bergmann wrote:
Still I do not understand:
Evaluate this in an updated Pharo core 1.2:
------------------------------------------------------------------------ Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfXMLSupport'; load.
(Smalltalk at: #ConfigurationOfXMLSupport) project latestVersion ------------------------------------------------------------------------
returns 1.1.8 [ConfigurationOfXMLSupport]
This is now broken by Otto. OK, he broke it, he has to repair it ;)
But independent from that, the method in:
ConfigurationOfPharo>>version12beta2:
includes the following:
project: 'XMLSupport' with: '1.1.6'.
So I would have expected that for Pharo "1.2-beta2" the 1.1.6 (and not the 1.1.8) of XMLSupport gets loaded and Hudson should have been green.
Why does Metacello load the 1.1.8 when a previous project version (1.1.6) is referenced?
Dale, any comments?
Bye T.
-- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
-- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.