3 Dec
2009
3 Dec
'09
8:04 p.m.
I took a fresh 10496 image, and opened a workspace and did a doit:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Gofer new
squeaksource: 'Moose';
addPackage: 'ConfigurationOfMoose';
load.
(Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault.
Gofer new
squeaksource: 'CAnalyzer';
addPackage: 'ConfigurationOfCAnalyzer';
load.
(Smalltalk at: #ConfigurationOfCAnalyzer) perform: #loadVersion: with:
'1.3'
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
It run as one would expect.
What are the steps to reproduce the problem you encountered?
Alexandre
On 3 Dec 2009, at 12:15, Simon Denier wrote:
Now what I did this morning (reproducible) (same thing
I did last
week):
1) create a new folder (so that there is no package cache)
2) put a fresh 10496 dev image
3) add (manually) the repository Moose and load ConfigurationOfMoose
3bis) wait for Moose to load
4) add the CAnalyser repository, load ConfigurationOfCAnalyzer-
Alexandre_Bergel.16 (NOT ConfigurationOfCAnalyzer-StephaneDucasse.17)
5) run the tests: all green except 2, which were expected in this
version of CAnalyzer
I cant debug something which I cant reproduce.
Now what happens yesterday: with Alex we spent some time figuring
out how to change the importer to that it accepts the new spec for
FAMIXFile and FAMIXFolder (following changes from Doru last week).
Finally I spent my evening refactoring
the logic of the importer to make it work. Now for me, it's still a
dev version, not a release, so ConfigurationOfCAnalyzer was not up
to date with respect to this change. But if you want, you can always
do
ConfigurationOfCAnalyzer project lastVersion load
On 3 déc. 2009, at 09:21, Tudor Girba wrote:
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Indeed.
Because the current tools are not as supportive as they should be,
it is important that after changing a configuration to try it in a
new image. It takes a bit of time, but it saves the time of
everyone else.
At this time, I am maintaining ConfigurationOfMoose and all
depending configurations. For each of the rest, we need a
responsible.
Cheers,
Doru
On 3 Dec 2009, at 10:05, Stéphane Ducasse wrote:
--
Simon
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
for example ConfigurationOfCAnalyzer was not.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Sometimes the best solution is not the best solution."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev