21 Jul
2016
21 Jul
'16
2:43 p.m.
On 21/07/2016 14:38, Tudor Girba wrote:
--
Cyril Ferlicot
http://www.synectique.eu
165 Avenue Bretagne
Lille 59000 France
Hi Cyril,
Everyone agrees that we need to create better configurations, and there were multiple
calls for help in the past but until now nobody answered :).
But, I am happy that you want to invest time in this.
Most of the Famix tests are still in the Moose configuration and not in
the Famix one. This is caused by the fact that Famix tests have
dependencies on Moose packages. We cannot launch the tests of Famix
without Moose for now.
This should be cleaned. Some dependencies need to be cut. Some things
that are in Moose's packages need to move on Famix. Maybe some packages
might need to be cut into smaller ones.
I agree that the first step is to get a good
ConfigurationOfFame and
ConfigurationOfFamix.
For the ConfigurationOfFamix I think the steps are:
- Clean cyclic dependencies
Yes.
- Cleans the tests packages of FAMIX that are
still in the Moose
configuration since they depend on Moose
I do not understand this part. We should rename the importer and test packages to not
have Moose in the name, but Famix.
- Remove all the problem we see in Jenkins logs:
https://ci.inria.fr/moose/job/Famix/PHARO=60,VERSION=development/21/console
Ok.
- I also think that Famix should not have the
importers directly and we
should have a ConfigurationOfFamixImporters.
Agreed.
Doru
--
www.tudorgirba.com
www.feenk.com
"Problem solving should be focused on describing
the problem in a way that makes the solution obvious."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev