Hi,
It looks like loading the latest XMLSupport raises some problems: http://hudson.moosetechnology.org/job/moose-latest-dev/448/console
Could anyone take a look at that?
Cheers, Doru
-- www.tudorgirba.com
"Presenting is storytelling."
---- On Wed, 17 Nov 2010 23:33:47 -0800 Tudor Girba wrote ----
Hi,
It looks like loading the latest XMLSupport raises some problems: http://hudson.moosetechnology.org/job/moose-latest-dev/448/console
Could anyone take a look at that?
I have been trying to make XML-Support more modular. XMLWriter is now stored separately at squeaksource.com/XMLWriter, and the tests are being separated into separate packages as well.
This: Gofer new squeaksource: 'XMLSupport'; package: 'ConfigurationOfXMLSupport'; load. (Smalltalk at: #ConfigurationOfXMLSupport) perform: #loadDefault
works fine for me. Please try building it again and report back any errors.
Cheers, Doru
-- www.tudorgirba.com
"Presenting is storytelling."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
HI,
I did execute
Gofer new squeaksource: 'XMLSupport'; package: 'ConfigurationOfXMLSupport'; load. (Smalltalk at: #ConfigurationOfXMLSupport) perform: #loadDefault
into a Pharo 1.1.1 and it doesn't work. I got this error:
Error: Could not resolve: ConfigurationOfXMLWriter.
Cheers,
Fabrizio
On 18 Nov 2010, at 13:38, jaayer wrote:
---- On Wed, 17 Nov 2010 23:33:47 -0800 Tudor Girba wrote ----
Hi,
It looks like loading the latest XMLSupport raises some problems: http://hudson.moosetechnology.org/job/moose-latest-dev/448/console
Could anyone take a look at that?
I have been trying to make XML-Support more modular. XMLWriter is now stored separately at squeaksource.com/XMLWriter, and the tests are being separated into separate packages as well.
This: Gofer new squeaksource: 'XMLSupport'; package: 'ConfigurationOfXMLSupport'; load. (Smalltalk at: #ConfigurationOfXMLSupport) perform: #loadDefault
works fine for me. Please try building it again and report back any errors.
Cheers, Doru
-- www.tudorgirba.com
"Presenting is storytelling."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
---- On Thu, 18 Nov 2010 04:56:45 -0800 Fabrizio Perin wrote ----
HI,
I did execute
Gofer new squeaksource: 'XMLSupport'; package: 'ConfigurationOfXMLSupport'; load. (Smalltalk at: #ConfigurationOfXMLSupport) perform: #loadDefault
into a Pharo 1.1.1 and it doesn't work. I got this error:
Error: Could not resolve: ConfigurationOfXMLWriter.
You're right; it appears my package cache was playing tricks on me. I think I know what the problem is now. I was using #repositories: incorrectly. Apparently specifying multiple repositories via #repositories: does... something, but not what I though it did. I have changed it so each package outside of XML-Support has an explicit repository reference. I just tried loading it into a clean image with an empty package cache, and this time everything seemed to work. I will contact Dale just to make sure I did not uncover a bug.
Thanks for the feedback, and please follow up if you have any additional issues.
Fabrizio
On 18 Nov 2010, at 13:38, jaayer wrote:
---- On Wed, 17 Nov 2010 23:33:47 -0800 Tudor Girba wrote ----
Hi,
It looks like loading the latest XMLSupport raises some problems: http://hudson.moosetechnology.org/job/moose-latest-dev/448/console
Could anyone take a look at that?
I have been trying to make XML-Support more modular. XMLWriter is now stored separately at squeaksource.com/XMLWriter, and the tests are being separated into separate packages as well.
This: Gofer new squeaksource: 'XMLSupport'; package: 'ConfigurationOfXMLSupport'; load. (Smalltalk at: #ConfigurationOfXMLSupport) perform: #loadDefault
works fine for me. Please try building it again and report back any errors.
Cheers, Doru
-- www.tudorgirba.com
"Presenting is storytelling."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Thanks! Now it loads without problems. Just a question: what about the tests? Is it possible to have them by default? Or is it possible to have something like #loadDefaultForDevelopment where you have also the test loaded?
Cheers,
Fabrizio
On 18 Nov 2010, at 14:36, jaayer wrote:
---- On Thu, 18 Nov 2010 04:56:45 -0800 Fabrizio Perin wrote ----
HI,
I did execute
Gofer new squeaksource: 'XMLSupport'; package: 'ConfigurationOfXMLSupport'; load. (Smalltalk at: #ConfigurationOfXMLSupport) perform: #loadDefault
into a Pharo 1.1.1 and it doesn't work. I got this error:
Error: Could not resolve: ConfigurationOfXMLWriter.
You're right; it appears my package cache was playing tricks on me. I think I know what the problem is now. I was using #repositories: incorrectly. Apparently specifying multiple repositories via #repositories: does... something, but not what I though it did. I have changed it so each package outside of XML-Support has an explicit repository reference. I just tried loading it into a clean image with an empty package cache, and this time everything seemed to work. I will contact Dale just to make sure I did not uncover a bug.
Thanks for the feedback, and please follow up if you have any additional issues.
Fabrizio
On 18 Nov 2010, at 13:38, jaayer wrote:
---- On Wed, 17 Nov 2010 23:33:47 -0800 Tudor Girba wrote ----
Hi,
It looks like loading the latest XMLSupport raises some problems: http://hudson.moosetechnology.org/job/moose-latest-dev/448/console
Could anyone take a look at that?
I have been trying to make XML-Support more modular. XMLWriter is now stored separately at squeaksource.com/XMLWriter, and the tests are being separated into separate packages as well.
This: Gofer new squeaksource: 'XMLSupport'; package: 'ConfigurationOfXMLSupport'; load. (Smalltalk at: #ConfigurationOfXMLSupport) perform: #loadDefault
works fine for me. Please try building it again and report back any errors.
Cheers, Doru
-- www.tudorgirba.com
"Presenting is storytelling."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
---- On Thu, 18 Nov 2010 07:18:06 -0800 Fabrizio Perin wrote ----
Thanks! Now it loads without problems. Just a question: what about the tests? Is it possible to have them by default? Or is it possible to have something like #loadDefaultForDevelopment where you have also the test loaded?
Sure. I'll change #loadDefault in the next release to load both "Core" and "Tests".
Cheers,
Fabrizio
On 18 Nov 2010, at 14:36, jaayer wrote:
---- On Thu, 18 Nov 2010 04:56:45 -0800 Fabrizio Perin wrote ----
HI,
I did execute
Gofer new squeaksource: 'XMLSupport'; package: 'ConfigurationOfXMLSupport'; load. (Smalltalk at: #ConfigurationOfXMLSupport) perform: #loadDefault
into a Pharo 1.1.1 and it doesn't work. I got this error:
Error: Could not resolve: ConfigurationOfXMLWriter.
You're right; it appears my package cache was playing tricks on me. I think I know what the problem is now. I was using #repositories: incorrectly. Apparently specifying multiple repositories via #repositories: does... something, but not what I though it did. I have changed it so each package outside of XML-Support has an explicit repository reference. I just tried loading it into a clean image with an empty package cache, and this time everything seemed to work. I will contact Dale just to make sure I did not uncover a bug.
Thanks for the feedback, and please follow up if you have any additional issues.
Fabrizio
On 18 Nov 2010, at 13:38, jaayer wrote:
---- On Wed, 17 Nov 2010 23:33:47 -0800 Tudor Girba wrote ----
Hi,
It looks like loading the latest XMLSupport raises some problems: http://hudson.moosetechnology.org/job/moose-latest-dev/448/console
Could anyone take a look at that?
I have been trying to make XML-Support more modular. XMLWriter is now stored separately at squeaksource.com/XMLWriter, and the tests are being separated into separate packages as well.
This: Gofer new squeaksource: 'XMLSupport'; package: 'ConfigurationOfXMLSupport'; load. (Smalltalk at: #ConfigurationOfXMLSupport) perform: #loadDefault
works fine for me. Please try building it again and report back any errors.
Cheers, Doru
-- www.tudorgirba.com
"Presenting is storytelling."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
ConfigurationOfXMLWriter is not found.
Cheers, Alexandre
On 18 Nov 2010, at 09:38, jaayer wrote:
---- On Wed, 17 Nov 2010 23:33:47 -0800 Tudor Girba wrote ----
Hi,
It looks like loading the latest XMLSupport raises some problems: http://hudson.moosetechnology.org/job/moose-latest-dev/448/console
Could anyone take a look at that?
I have been trying to make XML-Support more modular. XMLWriter is now stored separately at squeaksource.com/XMLWriter, and the tests are being separated into separate packages as well.
This: Gofer new squeaksource: 'XMLSupport'; package: 'ConfigurationOfXMLSupport'; load. (Smalltalk at: #ConfigurationOfXMLSupport) perform: #loadDefault
works fine for me. Please try building it again and report back any errors.
Cheers, Doru
-- www.tudorgirba.com
"Presenting is storytelling."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
---- On Wed, 17 Nov 2010 23:33:47 -0800 Tudor Girba wrote ----
Hi,
It looks like loading the latest XMLSupport raises some problems: http://hudson.moosetechnology.org/job/moose-latest-dev/448/console
Could anyone take a look at that?
I narrowed it down: if you try to load the XML-Parser package by itself without first loading its prerequisites, you get that exact error. So either the build process isn't loading XML-Support via Metacello and no dependency resolution is being done, or it is using Metacello and the configuration was broken. The dependency in question used to be a Monticello required package, but that dependency was removed in favor of a Metacello dependency.
Cheers, Doru
-- www.tudorgirba.com
"Presenting is storytelling."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Alexandre Bergel -
Fabrizio Perin -
jaayer -
Tudor Girba