Hi,
I had a similar problem before with the new inFusion which is also based on JDT. In that
case, the problem was due to inFusion relying on an Eclipse project and it got confused
because of the .project file from the root folder.
Nicolas, would VerveineJ not be affected by a .project?
Cheers,
Doru
On 27 Apr 2011, at 07:47, Matthias Junker wrote:
Yes, i give mainProject as argument. It seems to
finish normally. I can load the output.mse in Moose without problem, but i only have the
classes from one subproject in it. Also in the output of verveinej.sh i can only see the
classes from this subproject. It looks as if it wouldn't find the other classes.
Unfortunately i can't give out the sources, but i'll try to build a small test
project and see if it works there.
Cheers,
Matt
On Wed, Apr 27, 2011 at 12:49 AM, Nicolas Anquetil <nicolas.anquetil(a)inria.fr>
wrote:
It should be able to parse everything.
what do you give it as argument? "mainProject"?
But basically, it should be called as a compiler: you tells it where the sources are and
what class path it needs to parse these sources.
When it stops does it crashes?
Is it a memory problem as with Doru?
nicolas
De: "Matthias Junker" <junker.matt(a)gmail.com>
À: "Moose-related development" <moose-dev(a)iam.unibe.ch>
Envoyé: Mardi 26 Avril 2011 18:59:29
Objet: [Moose-dev] Re: VerveineJ problem
Sorry for that partial message. Accidentaly hit send.
Our project is structured like this:
mainProject
subproject1
src
main
java
<sources here>
subproject2
src
main
java
<sources here>
etc
VerveineJ only seems to parse one subproject and then stops. Is there a way to configure
that it parses all subprojects?
Cheers
Matt
On Tue, Apr 26, 2011 at 6:52 PM, Matthias Junker <junker.matt(a)gmail.com> wrote:
Hi,
I tested again and the loading works now. Thanks.
Now i have another problem. I try to parse a maven multi-module
project which is organized like this:
mainProject
On Tue, Apr 26, 2011 at 8:29 AM, Nicolas Anquetil
<nicolas.anquetil(a)inria.fr> wrote:
Hi, Matthias,
apparently you invoked verveineJ the right way.
would you mind testing again with the latest VerveineJ (as of this morning).
I just finished correcting some bugs so maybe your's was covered.
Otherwise, would it be possible to have access to the code parsed?
So that I can reproduce the error?
thanks for helping
nicolas
----- Mail original -----
De: "Matthias Junker"
<junker.matt(a)gmail.com>
À: "Moose-related development" <moose-dev(a)iam.unibe.ch>
Envoyé: Dimanche 24 Avril 2011 14:51:51
Objet: [Moose-dev] VerveineJ problem
Hey,
i tried to load a project with verveinej.sh and get a
NullPointerException. I only provided the path to the sources as an
argument:
Exception in thread "main" java.lang.NullPointerException
at
org.eclipse.jdt.core.dom.MethodBinding.isAnnotationMember(MethodBinding.java:55)
at
fr.inria.verveine.extractor.java.VerveineVisitor.methodInvocation(VerveineVisitor.java:554)
at
fr.inria.verveine.extractor.java.VerveineVisitor.visit(VerveineVisitor.java:497)
at
org.eclipse.jdt.core.dom.MethodInvocation.accept0(MethodInvocation.java:237)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2480)
at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2551)
at
org.eclipse.jdt.core.dom.MethodInvocation.accept0(MethodInvocation.java:245)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2480)
at org.eclipse.jdt.core.dom.ASTNode.acceptChild(ASTNode.java:2528)
at
org.eclipse.jdt.core.dom.VariableDeclarationFragment.accept0(VariableDeclarationFragment.java:225)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2480)
at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2551)
at
org.eclipse.jdt.core.dom.VariableDeclarationStatement.accept0(VariableDeclarationStatement.java:273)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2480)
at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2551)
at org.eclipse.jdt.core.dom.Block.accept0(Block.java:136)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2480)
at org.eclipse.jdt.core.dom.ASTNode.acceptChild(ASTNode.java:2528)
at
org.eclipse.jdt.core.dom.TryStatement.accept0(TryStatement.java:195)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2480)
at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2551)
at org.eclipse.jdt.core.dom.Block.accept0(Block.java:136)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2480)
at org.eclipse.jdt.core.dom.ASTNode.acceptChild(ASTNode.java:2528)
Disconnected from the target VM, address: '127.0.0.1:51367',
transport: 'socket'
at
org.eclipse.jdt.core.dom.MethodDeclaration.accept0(MethodDeclaration.java:504)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2480)
at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2551)
at
org.eclipse.jdt.core.dom.TypeDeclaration.accept0(TypeDeclaration.java:484)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2480)
at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2551)
at
org.eclipse.jdt.core.dom.CompilationUnit.accept0(CompilationUnit.java:219)
at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2480)
at
fr.inria.verveine.extractor.java.FamixRequestor.acceptAST(FamixRequestor.java:31)
at
org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:1016)
at
org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:628)
at org.eclipse.jdt.core.dom.ASTParser.createASTs(ASTParser.java:982)
at
fr.inria.verveine.extractor.java.VerveineJParser.parse(VerveineJParser.java:169)
at
fr.inria.verveine.extractor.java.VerveineJParser.main(VerveineJParser.java:153)
This is the MethodBinding where i get the NullPointer:
• this = {org.eclipse.jdt.core.dom.MethodBinding@1077}"public
java.lang.String getName() "
• binding =
{org.eclipse.jdt.internal.compiler.lookup.ParameterizedMethodBinding@1808}"public
java.lang.String getName() "
• resolver = {org.eclipse.jdt.core.dom.DefaultBindingResolver@1809}
• parameterTypes = null
• exceptionTypes = null
• name = null
• declaringClass = null
• returnType = null
• key = null
• typeParameters = null
• typeArguments = null
• annotations = null
• parameterAnnotations = null
Did anybody have similar problems?
Cheers
Matt
_______________________________________________
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
_______________________________________________
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
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev