Closed jecisc closed 5 years ago
To clarify, when I say "Use the cypress support", I mean implementing this method in the baseline:
projectClass
^ [ self class environment at: #MetacelloCypressBaselineProject ]
on: NotFound
do: [ super projectClass ]
@dalehenrich check out pharo-project/pharo#2173 . With this change at least we're able to use the copy project functionality with Cypress based projects.
@jecisc does this patch resolve your problem?
@dalehenrich Yes! I added back the support for a project and it's all right in P7 and broken in P6.1.
I got esteban approval to backport this fix in 6.1.
It was the last thing I was missing to use this in all my project :) When it will be in 6.1 I'll also update the baseline guide I wrote to help new members of the community to includes it:
https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/Baselines.md
It's more pharo oriented but I guess it can also help people from other smalltalks. (And also git oriented. I do not cover configurations)
@jecisc very good! ...
I need to have a configuration with a dependency on a project. But some packages need to depend on the group "Minimal" of this project and others need to depend on the "Presentation" group.
I tried to use this code:
If I use a classic project class for the baseline it works. But if I use the Metacello cypress support I get this error:
Error: The project spec 'MyProjectName' in project BaselineOfMyCurrentProject has incompatible specs. MetacelloMCBaselineOfProjectSpec and MetacelloCypressBaselineProjectSpec are not compatible.