Hi,

As Stéphane announced it, we have an engineer position for two years to modify FAME and FAMIX to make them more easily adaptable… and to adapt existing tools to this new core. So perhaps, somethings could be done in parallel, but in the opposite, perhaps, we should not take too much time to modify the current version since we will rebuild a new one.

Anne
PS: I am writing the position description to send it to the list and audition interested people in ESUG.


Le 21 juil. 2016 à 16:04, Guillaume Larcheveque <guillaume.larcheveque@gmail.com> a écrit :

I think there is a problem calling MooseEntity and everything in the Moose-Core package as Moose...

Basically, we should rename everything that concern the MetaModel as FAMIX and so rename Moose-Core in FAMIX-Abstract for example.

Then we should split the actual Moose-Core in different packages such as FAMIX-Importers...

Maybe we should talk about that at ESUG :-D

2016-07-21 15:32 GMT+02:00 Tudor Girba <tudor@tudorgirba.com>:
Hi,



> On Jul 21, 2016, at 6:43 AM, Cyril Ferlicot Delbecque <cyril.ferlicot@gmail.com> wrote:
>
>
>
> On 21/07/2016 14:38, Tudor Girba wrote:
>> 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.
>>
>>
>>> 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.
>>
>
> 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.

FAMIX depends on Moose-Core
Importers depend on FAMIX and Moose-Core
So, we will always have a dependency to Moose-Core.

Doru


> 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.
>
>>
>>> - 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@list.inf.unibe.ch
>> https://www.list.inf.unibe.ch/listinfo/moose-dev
>>
>
> --
> Cyril Ferlicot
>
> http://www.synectique.eu
>
> 165 Avenue Bretagne
> Lille 59000 France
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev@list.inf.unibe.ch
> https://www.list.inf.unibe.ch/listinfo/moose-dev

--
www.tudorgirba.com
www.feenk.com

"We are all great at making mistakes."








_______________________________________________
Moose-dev mailing list
Moose-dev@list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev



--
Guillaume Larcheveque

_______________________________________________
Moose-dev mailing list
Moose-dev@list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev