On Jan 19, 2011, at 11:43 AM, Tudor Girba wrote:
> Indeed, this is a problem for Moose in general. We depend on XMLSupport, but
> now we cannot update it in PharoDev. I would also strongly support the idea
> of removing XMLSupport from PharoDev.
>
What would be important: we need the latest version in Pharo 1.2... else how
can we ever have a version where the tests are green?
(not of XML, but in general)
Marcus
> Cheers,
> Doru
>
>
> On 19 Jan 2011, at 11:32, Fabrizio Perin wrote:
>
>> Hi,
>>
>> I have a problem with the XMLSupport version from Pharo 1.2.
>>
>> The problem is that I need to work with one of the last version of
>> XMLSupport but in the pharo image 1.2 is loaded an old version of XMLSupport
>> (I mean a version from Jan 2010). I did try to load a newer version of
>> XMLSupport using ConfigurationOfXMLSupport but some errors make this
>> operation impossible.
>> So either Pharo-dev 1.2 load a newer (possibly the last) version of
>> XMLSupport by default or Pharo-dev 1.2 should not load XMLSupport at all.
>>
>> I think that doesn't make sense to use by default such an old version, also
>> considering that the last XMLSupport has nice and useful features like the
>> XMLPluggableElementFactory.
>>
>> By avoiding to load XMLSupport in Pharo-dev 1.2 by default you let people
>> free to use the version that they like.
>>
>> Thanks,
>>
>> Fabrizio
>>
>
> --
> www.tudorgirba.com
>
> "We cannot reach the flow of things unless we let go."
>
>
>
>
--
Marcus Denker -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.
