[gatein-dev] Fwd: Japex issue

From: Santiago Pericas-Geertsen <santiago.pericasgeertsen(a)oracle.com&gt; Date: September 22, 2011 6:18:54 PM GMT+02:00 To: Julien Viet <julien(a)julienviet.com&gt; Subject: Re: Japex issue Julien, Just deployed Japex 1.2.4 to java.net [1]. It should be synched to Maven Central in some time (not sure how long, though). Thanks. -- Santiago [1] https://maven.java.net/content/repositories/releases/com/sun/japex/japex-... On Sep 21, 2011, at 3:24 PM, Julien Viet wrote: > Hi Santiago, > > I confirm it does fix the problem, I attached the trivial patch to the mail. > > could you tell me when this would be available in a version (preferably available on maven central like other release are). > > Julien > > > <patch.txt> > > On Sep 21, 2011, at 7:53 PM, Santiago Pericas-Geertsen wrote: > >> Julien, >> >> Looks like it may be a 1-line fix. Do you want to try it by pulling the Japex sources and compiling it [1]? The class is called JapexMojo. >> >> With Javaone and other deadlines, it will be hard for me to test this. But I'd be happy to commit a patch if the fix works for you. >> >> Thanks. >> >> -- Santiago >> >> [1] http://java.net/projects/japex/sources/svn/show >> >> On Sep 21, 2011, at 1:33 PM, Julien Viet wrote: >> >>> Hi, >>> >>> I had issues to make the maven japex plugin run with Maven 3 due to a classpath issue that make the maven runtime to resolve the classpath to the "target/test-classes" only and not the transitive maven dependencies resolved by the test scope of the module. >>> >>> The issue lies in the fact that the MOJO does not declare the "requiresDependencyResolution" / "requiresDependencyCollection" meta data. >>> >>> I found someone describing a solution for this issue here : http://www.mail-archive.com/users@maven.apache.org/msg115700.html >>> >>> this is a quite short reading fortunately. >>> >>> to reproduce the issue, a simple japex driver that uses a dependency external dependency will show the failure with maven 3. >>> >>> cheers >>> >>> Julien >> >