Closed GoogleCodeExporter closed 9 years ago
Johan, How are you using the repositoryOverrides:? What expression do you use
to launch the load?
Original comment by henrichs...@gmail.com
on 12 Aug 2011 at 4:50
Original comment by henrichs...@gmail.com
on 12 Aug 2011 at 4:53
Hi Dale,
Here is how I am using this in a class method of a metacello configuration:
|repos|
repos := OrderedCollection new.
repos add: (MCHttpRepository
location: 'http://dev.inceptive.be/common'
user: Username
password: Pasword).
... (add more repositories) ...
(self project version: '1.0.3')
repositoryOverrides: repos;
load: 'NextPlan-Dev'.
The configuration references the seaside and other configurations as a project
with an explicit version.
Hope this helps in reconstructing.
Original comment by johanbri...@gmail.com
on 12 Aug 2011 at 6:19
Johan,
What does the project reference to ConfigurationOfSeaside30 look like?
Presumably you have a reference in ConfigurationOfNextPlan that looks like this:
project: 'Seaside30' with: [
spec
className: 'ConfigurationOfSeaside30';
versionString: #'stable';
loads: #('Base' 'JQuery-UI' );
repository: 'http://www.squeaksource.com/Seaside30' ]
or this:
spec
project: 'Grease'
with: [
spec
className: 'ConfigurationOfGrease';
versionString: '1.0-alpha1-baseline';
loads: #('Grease-Core');
projectPackage: [
spec
name: 'ConfigurationOfGrease';
repository: 'http://seaside.gemstone.com/ss/Seaside30' ] ]
I'm also interested in how the ConfigurationOfGrease reference looks, since it
appears that the repository override worked for Grease, but didn't work for
Seaside...
Original comment by henrichs...@gmail.com
on 8 Sep 2011 at 7:26
Dale,
This is the one:
spec
project: 'Seaside30'
with:
[ spec
className: 'ConfigurationOfSeaside30';
versionString: '3.0.5';
file: 'ConfigurationOfSeaside30';
loads: #('Core');
repository: 'http://www.squeaksource.com/MetacelloRepository'].
Grease is not referenced by this Configuration. It is done through the
Seaside30 configuration.
I will send you the ConfigurationOfNextPlan file in a private email...
Original comment by johanbri...@gmail.com
on 12 Sep 2011 at 11:25
This issue was either not reproducing or was resolved before we had chacterized
the problem ... during SqueakSource3 upgrade planning[1], I ran into a similar
problem and recorded it as Issue 163
[1] http://code.google.com/p/squeaksource3/wiki/UpgradeToDoSs3ToRc2
Original comment by henrichs...@gmail.com
on 16 Dec 2011 at 7:01
Original issue reported on code.google.com by
johanbri...@gmail.com
on 12 Aug 2011 at 10:05