[Moose-dev] Re: To a unified software model repository for Moose.

I think that if we do not want to have a FAMIX entity and do not have to change the importer/exporter to write an header containing the meta data we will have to get it in another file. No Did you look at the famix 2.1 document - project name - location of the original files: URI? - version of the project - language - version of the original language: Java but which one - description - author: email - extractor: Moose42 on Pharo1.4 - date - mse file name (if this is external Why? If I extract a model using Moose does it make sense not to be able to reload it because the model change. Try to come up with a meta data that is not just for Java because soon there is scala, java, cobol and many more out there. yes Jannik? But normally it should work. Now I do not know if orion covers all the famix entities but extending it should not be a problem, What would be good is that orion gets the trick that andy and veronica implemented in their implementation of Orion yes but in that case you should also have in the meta data - fuel version Apparently you did not check Fuel :) You can reload Pharo completely in 10-15 seconds with Fuel.