Re: [Pharo-project] Pharo 1.2 broken on Hudson due to XMLSupport changes
On Feb 25, 2011, at 5:42 PM, laurent laffont wrote:
On Fri, Feb 25, 2011 at 5:11 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
On Feb 25, 2011, at 2:10 PM, Torsten Bergmann wrote:
Markus wrote:
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.
It's not that the package is problematic - the Configs are problematic
Exact But still can't Pharo Dev focuses on tools and not frameworks that we should load by ourselves. Because else why not loading, cassandra, coucdb, opendbx, magma....
Because many more people are manipulating XML every day than connecting to Cassandra ?
So now XML is fixed, not it fails due to a problem in the Mock package... We can not delay a release to fix all foreign packages. This makes no sense. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
On 25.02.2011, at 17:48, Marcus Denker wrote:
On Feb 25, 2011, at 5:42 PM, laurent laffont wrote:
On Fri, Feb 25, 2011 at 5:11 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
On Feb 25, 2011, at 2:10 PM, Torsten Bergmann wrote:
Markus wrote:
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.
It's not that the package is problematic - the Configs are problematic
Exact But still can't Pharo Dev focuses on tools and not frameworks that we should load by ourselves. Because else why not loading, cassandra, coucdb, opendbx, magma....
Because many more people are manipulating XML every day than connecting to Cassandra ?
So now XML is fixed, not it fails due to a problem in the Mock package...
We can not delay a release to fix all foreign packages. This makes no sense.
Absolutely not. Otto did a mistake so this caused problems. So isn't it obvious to rollback the configuration back to the point it worked. Norbert
I think the build will become unstable with every package update... So maybe we should update every ConfigurationOf used by pharo, and put symbolic versions into it Guille On Fri, Feb 25, 2011 at 1:50 PM, Norbert Hartl <norbert@hartl.name> wrote:
On 25.02.2011, at 17:48, Marcus Denker wrote:
On Feb 25, 2011, at 5:42 PM, laurent laffont wrote:
On Fri, Feb 25, 2011 at 5:11 PM, Stéphane Ducasse < stephane.ducasse@inria.fr> wrote:
On Feb 25, 2011, at 2:10 PM, Torsten Bergmann wrote:
Markus wrote:
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.
It's not that the package is problematic - the Configs are problematic
Exact But still can't Pharo Dev focuses on tools and not frameworks that we should load by ourselves. Because else why not loading, cassandra, coucdb, opendbx, magma....
Because many more people are manipulating XML every day than connecting to Cassandra ?
So now XML is fixed, not it fails due to a problem in the Mock package...
We can not delay a release to fix all foreign packages. This makes no sense.
Absolutely not. Otto did a mistake so this caused problems. So isn't it obvious to rollback the configuration back to the point it worked.
Norbert
On Feb 25, 2011, at 5:48 PM, Marcus Denker wrote:
Exact But still can't Pharo Dev focuses on tools and not frameworks that we should load by ourselves. Because else why not loading, cassandra, coucdb, opendbx, magma....
Because many more people are manipulating XML every day than connecting to Cassandra ?
So now XML is fixed, not it fails due to a problem in the Mock package...
We can not delay a release to fix all foreign packages. This makes no sense.
I removed Mocketry for now... and the build works. current TODO: http://code.google.com/p/pharo/issues/list?cursor=3652&q=milestone%3D1.2-Dev... -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
participants (3)
-
Guillermo Polito -
Marcus Denker -
Norbert Hartl