However, please let’s redo this. I do not want to have groups in the ConfigurationOfMoose.
I know some people have a different, but groups are difficult to manage, and in our case,
we certainly need explicit artifacts that should be modeled with configurations.
On May 2, 2016, at 10:58 AM, Cyril Ferlicot Delbecque
As we talked in another thread I tried to look at the configuration of
Moose to be able to load Famix without every Moose tool (Glamour, Roassal…).
As Stephan said, since Famix is an inactive project for now groups are
enough to manage Famix. So I made some groups to be able to get only
Famix and the moose packages needed by famix.
There is 3 groups:
- Famix (Which is only the two following groups together)
So if you have a Tool that use Famix but not Moose tools you can had
spec project: 'Famix' with: [
loads: #( #'Famix' );
repository: 'http://smalltalkhub.com/mc/Moose/Moose/main' ].
The only problem during the loading is about MalGraphBuilderStrategy
that is missing, but this was already the case in Moose.
I hope this will help you.
165 Avenue Bretagne
Lille 59000 France
Moose-dev mailing list
"It's not how it is, it is how we see it."