Thanks. Indeed, it is strange. Btw, I am on a Mac OS X Lion.
I will try again and get back to you later.
But, coming back to the issue, the goal of the script is to provide a set of possible
methods that are misplaced (that is methods that should appear in another class than where
they are actually defined). The issue is that if we have the source for the class, it
means we should have parsed it and have the proper information about its methods. So, how
could then methods appear inside without source code?
On 1 Nov 2011, at 10:35, Nicolas Anquetil wrote:
what I did:
- download ArgoUML-0.32-src.tar.gz (sources of ArgoUML) from the web site you gave
- download ArgoUML-0.32-libs.tar.gz (libraries needed by ArgoUML) from the web site you
- update verveinej to get your new shell script
- rm -f output.mse
- create MSE file:"verveinej.sh -autocp ArgoUML-0.32-libs ArgoUML-0.32-src"
- load MSE in Moose panel
- ran your script in workspace
When calling verveineJ, "-autocp ArgoUML-0.32-libs" is important.
Without it, JDT is not able to resolve a lot of types names, and as a consequence, a lot
of source methods that use these types (e.g. as parameter type).
And without JDT's name resolution, verveineJ is not able to link a method call to a
With the autocp, I found 13 methods with problems.
Without it, I found 473 (or something like that) methods with problems.
Not your 575 ones, but closer to it.
No idea how we can get so different results with the same data and program !!!
----- Mail original -----
> De: moose-technology(a)googlecode.com
> À: moose-dev(a)iam.unibe.ch
> Envoyé: Mardi 1 Novembre 2011 07:40:20
> Objet: [Moose-dev] Re: Issue 728 in moose-technology: VerveineJ places methods in the
> Status: Started
> Comment #7 on issue 728 by tudor.gi...(a)gmail.com: VerveineJ places
> in the wrong classes
> Hmm, I just tried. First, I fixed the shell script (verveinej.sh) to
> collect the jars automatically from the lib folder. Then I removed the
> obsolete jars.
> But, still, if I run the following experiment, I get 575 potentially
> problematic methods:
> - download ArgoUML 0.32 from:
> - parse, load in Moose, and then execute:
> (MooseModel root allModels first allMethods select: [:each |
> each sourceAnchor isNil and: [
> each parentType sourceAnchor notNil and: [
> '<Initializer>' ~= each name and: [
> each name ~= each parentType name ]]]]) openInMoose
> Am I doing something wrong?
> Moose-dev mailing list
Moose-dev mailing list
"We cannot reach the flow of things unless we let go."