OK
thanks Cedric.
I will look into that when I have time which means probably only monday.
Still we have a real issue here: how to get the model of a big (10K classes) system?
compilers don't have this problem because they use incremental compilation (e.g. one java file at a time).
But in our case, we want the entire famix model in memory so what can we do?
- any tricks we could use to improve memory usage?
- may be the complete model solution is not the right one?
- or may be it is the right one and there is no good solution?
nicolas
De: "Cedric Dumoulin" <cedric.dumoulin@lifl.fr>
À: "Nicolas Anquetil" <nicolas.anquetil@inria.fr>
Cc: "Stéphane Ducasse" <stephane.ducasse@inria.fr>, "Laval Jannik" <jannik.laval@inria.fr>, "Tudor Girba" <tudor@tudorgirba.com>
Envoyé: Vendredi 1 Juillet 2011 12:39:05
Objet: Re: Doru would like to participate to the effort
Hi,
About the 'uml' directory:
This directory contains diagrams' code generated by GMF. GMF generate numerous classes.
It should be possible to parse only a subset of 'uml', for example the oep.uml.diagram.clazz and all the required plugins.
I join a class diagram showing all of the required plugins, from 'uml', of diagram.clazz. On its left, plugins from 'uml', on its right, plugin from 'core'. Some required plugins from 'core' are missing in the diagram.
I suppose that the dependencies are the same for each diagram (oep.uml.diagram.[diagramnam]).
Steph, which mailing list are you talking about ?
Cedric
)
Nicolas Anquetil a écrit :Welcome, state of affairs: - we have implemented Eclipse plugins in Moose - we have an exporter to generate the information in MSE - wednesday I implemented a new option in verveineJ that allows to not export "local references/entities" On my computer I have source code in 7 directories: core, developer, ocl, others, profile-tool, sysml, uml I can parse 'core' (1383 java files), 5 others would probably not raise any problem: 'developer'=155 files, 'ocl'=6 files, 'others'=115 files, 'profile-tool'=20 files and 'sysml'=780 files. The difficulty is with 'uml': 6269 java files. I cannot even parse it alone ... despite incremental (separate) parsing and the 'no-locals' option, I still cannot generate data for this 'uml' directory, let alone the entire Papyrus (JDT explodes the memory). so, I am welcoming any idea on how to solve this problem ... nicolas PS: the 'no-locals' option needs to be better tested. It works on a small project (~= 10 classes), but we should watch it carefully on real projects. (Removing locals is not as simple as it may appear) ----- Mail original -----De: "Stéphane Ducasse" <stephane.ducasse@inria.fr> À: "Cedric Dumoulin" <cedric.dumoulin@lifl.fr> Cc: "Nicolas Anquetil" <Nicolas.Anquetil@inria.fr>, "Laval Jannik" <jannik.laval@inria.fr>, "Tudor Girba" <tudor@tudorgirba.com> Envoyé: Jeudi 30 Juin 2011 23:51:01 Objet: Doru would like to participate to the effort Hi guys I'm at doru place and he would like to help for the papyrus case. What would be good is also to have the discussion via the mailing-list so that people can follow. Stef