13 Nov
2011
13 Nov
'11
10:53 a.m.
Hi, as for the MSE importer I cannot help you. as for verveinej, there is one option you
can use: it will generate a smaller mse which may be what you need. However keep n mind
that this mean the MSE will not have all information. So if you later need more details,
they will not be available without a new parsing. Whereas tweaking the mse importer means
you have all the information in the mse and don't need to reparse if you want more
details, you only need to reload ... So, this said, and without further ado ... you can
use "-summary" which will generate a MSE at the class level, that is to say it
does not save members within classes (methods and attributes). It does not generate access
(because there are not attributes) not any invocations (because there are no methods)
instead, these are uplifted as dependencies between classes. Another possible (not
currently implemented) thing to do would be to add a "-noanchor" parameter that
would export all informations but not generate any source anchor. There are typically a
good number of these, so it should save a good deal of space. However, this could also
mean moose cannot compute LOC any more ... nicolas ----- Mail original -----
De: "Santiago Vidal"
<santiago.a.vidal(a)gmail.com>
À: "Moose-related development" <moose-dev(a)iam.unibe.ch>
Cc: "Moose-related development" <moose-dev(a)iam.unibe.ch>
Envoyé: Samedi 12 Novembre 2011 02:05:01
Objet: [Moose-dev] Re: Help with VerveineJ
Yep, thanks Alexandre
Enviado desde mi iPad
El 11/11/2011, a las 20:06, Alexandre Bergel < alexandre.bergel(a)me.com
escribió:
I think that what Santiago is saying, is whether there is a way to
customize the import context when loading an mse model
Alexandre
Le 11 nov. 2011 à 10:43, Santiago Vidal < santiago.a.vidal(a)gmail.com
a écrit :
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Hi,
I had create several MSE files of different versions of a Java
system
using VerveineJ. Then, I had tried to load them to the Moose Panel
but
after load two of them I run out of memory in Moose (The Pharo
error
is " Space is Low" ).
I had the same problem when loading several versions of Mondrian
to
Moose Panel. However, we solved it by using the following script
(we
select only those thing in which we are interested):
| mooseModel packages task |
#('2.10' '2.13' '2.100') do: [:version |
| project |
project := (ConfigurationOfMondrian project version: version).
[
project load.
"This is necessary by Moose to properly import"
Gofer new
url: ' http://www.squeaksource.com/CollectionExtensions ';
version: 'CollectionExtensions-TudorGirba.29';
load.
packages := (project packages collect: #name) select: [:p | p
beginsWith: 'Mondrian'].
mooseModel := MooseModel new.
task := MooseSqueakClassCategoryImporterTask new.
task importerClass: SmalltalkImporter.
task importingContext mergeClassAndMetaclass.
task model: mooseModel.
task runCandidateOperator.
task addFromPackagesNamed: packages.
task runWithProgress.
mooseModel name: 'Mondrian ', version.
mooseModel allMethods do: #numberOfLinesOfCode.
mooseModel install.
] on: Error do: [ :ex | self halt. Transcript show: 'cannot load
version ', version, ' ', ex printString. ].
]
Is there any way to do the same with VerveineJ (that is, reduce
the
size of the MSE files)? Or is there a way to expand the memory of
Moose?
Thanks
--
Santiago Vidal
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev