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.