On Fri, Apr 8, 2011 at 10:22 AM, Simon Denier <simon.denier@gmail.com> wrote:


On Fri, Apr 8, 2011 at 9:58 AM, Nicolas Anquetil <nicolas.anquetil@inria.fr> wrote:

Simon, verveineJ is on gforge.inria.fr

It is publicly available, and you are also one of the happy few that can commit.

svn checkout svn+ssh:/scm.gforge.inria.fr/svn/verveinej



Well, I know that, but the VerveineJ webpage was a bit unclear and just gave the link to the verveine.extractor.java so I was under the false assumption that core was still private (also verveine.extractor.java also contains the jar of core and famix and can be run as a stand alone project).

I updated the page so that it gives the links to the two projects:
http://www.moosetechnology.org/tools/verveinej

Will try to check that tonight, I don't even have my mac here.



Poking around, I see that at least some annotation types are imported as stub FamixNamespaces. Any idea where to look in the code which could lead to such a behaviour?


 
 

But the problem may be somewhere else.

----- Mail original -----
> De: "Tudor Girba" <tudor.girba@gmail.com>
> À: "Moose-related development" <moose-dev@iam.unibe.ch>
> Envoyé: Vendredi 8 Avril 2011 00:47:24
> Objet: [Moose-dev] Re: Status of Java annotation import with infusion/VerveineJ?
> Hi,
>
> I just redid the build on hudson, and there are still 17 tests.
>
> I also tried with the latest version locally to parse:
> svn co
> https://www.iam.unibe.ch/scg/svn_repos/Lectures/P2/Examples/Annotations/
>
> But, I got an error:
> Exception in thread "main" java.lang.ClassCastException:
> fr.inria.verveine.core.gen.famix.AnnotationTypeAttribute cannot be
> cast to fr.inria.verveine.core.gen.famix.Method
> at
> fr.inria.verveine.extractor.java.JavaDictionary.ensureFamixMethod(Unknown
> Source)
> at
> fr.inria.verveine.extractor.java.VerveineVisitor.methodInvocation(Unknown
> Source)
> at fr.inria.verveine.extractor.java.VerveineVisitor.visit(Unknown
> Source)
> 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.ExpressionStatement.accept0(ExpressionStatement.java:144)
> 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.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(Unknown
> Source)
> 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(Unknown
> Source)
> at fr.inria.verveine.extractor.java.VerveineJParser.main(Unknown
> Source)
>
>
> Cheers,
> Doru
>
>
> On 8 Apr 2011, at 00:35, Nicolas Anquetil wrote:
>
> >
> > Howdy Simon,
> >
> > Hummm, VerveineJ should not be broken.
> > At least, it is not on my computer :-)
> >
> > And it should output annotation declaration and uses.
> > At least the subset defined in the metamodel (an annotation argument
> > value is always a string).
> >
> > What version did you test? I commited a running version yesterday
> > evening (but it is still not built on Hudson yet, any problem with
> > that?).
> >
> > The only two red tests, are things not implemented yet (e.g.
> > enumeration access)
> >
> > If it still does not work, can you send me an URL for your test case
> > (I could search for it but I am lazy)
> >
> > nicolas
> >
> >
> > ----- Mail original -----
> >> De: "Tudor Girba" <tudor.girba@gmail.com>
> >> À: "Moose-related development" <moose-dev@iam.unibe.ch>
> >> Envoyé: Vendredi 8 Avril 2011 00:22:12
> >> Objet: [Moose-dev] Re: Status of Java annotation import with
> >> infusion/VerveineJ?
> >> Actually, I think VerveineJ is broken now.
> >>
> >> Cheers,
> >> Doru
> >>
> >>
> >> On 8 Apr 2011, at 00:19, Tudor Girba wrote:
> >>
> >>> Hi Simon,
> >>>
> >>> On 8 Apr 2011, at 00:08, Simon Denier wrote:
> >>>
> >>>> Hello
> >>>>
> >>>> What's the status of Java annotation import with
> >>>> infusion/VerveineJ? I have seen some mails in the past weeks but
> >>>> didn't take a close look.
> >>>> Now I would like to use such information to draw dependencies
> >>>> linked to Spring annotations (for dependency injection).
> >>>>
> >>>> I tried both infusion and verveinej on the sample petclinic app
> >>>> for
> >>>> Spring but both returned a minimalistic set of annotation types
> >>>> (Override, SuppressWarnings, XmlElement, and XmlRootElement)
> >>>
> >>> inFusion is not yet released. The one you are using is version
> >>> 7.*.
> >>> For this one you need to add the jars where the annotations are
> >>> defined (the jars should be in a folder somewhere below the root
> >>> folder you give as input).
> >>>
> >>> However, VerveineJ should already provide this info. What version
> >>> are you using? Nicolas, did I understand this part wrong?
> >>>
> >>> Cheers,
> >>> Doru
> >>>
> >>>
> >>>> Any idea what is going wrong?
> >>>>
> >>>> --
> >>>> Simon Denier
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> Moose-dev mailing list
> >>>> Moose-dev@iam.unibe.ch
> >>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >>>
> >>> --
> >>> www.tudorgirba.com
> >>>
> >>> "Value is always contextual."
> >>>
> >>>
> >>>
> >>
> >> --
> >> www.tudorgirba.com
> >>
> >> "Obvious things are difficult to teach."
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> Moose-dev mailing list
> >> Moose-dev@iam.unibe.ch
> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> > _______________________________________________
> > Moose-dev mailing list
> > Moose-dev@iam.unibe.ch
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "Every thing should have the right to be different."
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev@iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev