On 4/13/07, Torsten Krah <[EMAIL PROTECTED]> wrote:
Yet i did the -U switch, but this should be the same like removing .m2
and let it recreate by mvn install.
No i dont use a http proxy - direct connection. I dont know how to use a
"maven-proxy", dont know what it is - all i did is checkout the svn
repository and "mvn clean install".
Well, this one is definitely a mystery ... according to the -X output
you posted (thanks for that!) it appears that none of the profiles
which trigger inclusion of the JSF API classes are getting triggered
on your build of shale-test. Those profiles are activated by either
compiling under a 1.4 or a 1.5 JDK, which will pick MyFaces (for JSF
1.1) or the RI (for JSF 1.2), respectively.
You wouldn't happen to be trying to compile under 1.6, would you? I
suspect the current build scripts will not work in that case.
Craig
Torsten
Am Freitag, den 13.04.2007, 15:42 +0200 schrieb Hermod Opstvedt:
> Hi
>
> Have you tried the mvn -U clean install? -U forces update.
>
> Also: Are you using a maven-proxy by chance?
>
> Hermod
>
>
> -----Opprinnelig melding-----
> Fra: Torsten Krah [mailto:[EMAIL PROTECTED]
> Sendt: 13. april 2007 10:12
> Til: [EMAIL PROTECTED]
> Emne: Re: Shale Build Error - Lifecycle class not found
>
> I got no directory ~/.m2/repository/org/apache/myfaces
>
> Output of mvn -X install:
>
> http://fachschaft.imn.htwk-leipzig.de/~tkrah/mvn.out.gz
>
> Maven does not want to download anything extra, although myfaces is
> missing.
> Deleted .m2 already but myfaces does not get fetched.
>
> Torsten
>
> Am Donnerstag, den 12.04.2007, 20:28 -0700 schrieb Craig McClanahan:
> > On 4/12/07, Torsten Krah <[EMAIL PROTECTED]> wrote:
> > > cd ~/Development/src/shale-parent <- top lvl directory of svn checkout
> > >
> > > mvn clean install
> > >
> > > Whats "interesting" is - it seams the complete jsf spec api is not
> > > found.
> > > Searching ~/.m2 for a myfaces api i got:
> > >
> > > Nothing ...
> > >
> >
> > Hmm ... for me, it's in:
> >
> > ~/.m2/repository/org/apache/myfaces/core/myfaces-api
> >
> > The build defaults to version 1.1.4 of this artifact. This was
> > downloaded initially from the standard Maven public repository.
> >
> > One thing you might try is using the -X option on your "mvn" command.
> > It will create a very copious amount of debugging output, including
> > which dependencies it thinks you need, and which repositories it is
> > searching for them.
> >
> > (I also presume that you're connected to the Internet when running
> > your build, so that new dependencies can be downloaded automatically.)
> >
> > Craig
> >
> >
> > > Have i have to provide it myself anywhere - thought maven would fetch it
> > > if needed.
> > >
> > > Torsten
> > >
> > > Am Mittwoch, den 11.04.2007, 13:34 -0700 schrieb Craig McClanahan:
> > > > Hmm ... building the current trunk code (with Maven 2.0.4) works for
> > > > me when I do the following:
> > > >
> > > > cd ..../framework <-- top level directory of my SVN checkout
> > > > mvn clean install
> > > >
> > > > Could you describe a little more about what commands you used to
> > > > initiate the build that is breaking like this?
> > > >
> > > > Craig
> > > >
> > > > On 4/10/07, Torsten Krah <[EMAIL PROTECTED]> wrote:
> > > > > Trying to build latest SVN Snapshot, i get:
> > > > >
> > > > > [INFO] Surefire report directory:
> > > > >
> /home/tkrah/Development/src/shale-parent/shale-test/target/surefire-reports
> > > > > org.apache.maven.surefire.booter.SurefireExecutionException:
> > > > > javax/faces/lifecycle/Lifecycle; nested exception is
> > > > > java.lang.NoClassDefFoundError: javax/faces/lifecycle/Lifecycle
> > > > > java.lang.NoClassDefFoundError: javax/faces/lifecycle/Lifecycle
> > > > > at java.lang.Class.getDeclaredMethods0(Native Method)
> > > > > at
> java.lang.Class.privateGetDeclaredMethods(Class.java:2427)
> > > > > at java.lang.Class.getMethod0(Class.java:2670)
> > > > > at java.lang.Class.getMethod(Class.java:1603)
> > > > > at
> > > > >
> org.apache.maven.surefire.junit.JUnitTestSet.createInstanceFromSuiteMethod(J
> UnitTestSet.java:176)
> > > > > at
> > > > >
> org.apache.maven.surefire.junit.JUnitTestSet.constructTestObject(JUnitTestSe
> t.java:140)
> > > > > at
> > > > >
> org.apache.maven.surefire.junit.JUnitTestSet.getTestCount(JUnitTestSet.java:
> 247)
> > > > > at
> > > > >
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.locateTestSets(Ab
> stractDirectoryTestSuite.java:104)
> > > > > at
> > > > >
> org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:1
> 50)
> > > > > at org.apache.maven.surefire.Surefire.run(Surefire.java:111)
> > > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> > > > > at
> > > > >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
> )
> > > > > at
> > > > >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
> .java:25)
> > > > > at java.lang.reflect.Method.invoke(Method.java:597)
> > > > > at
> > > > >
> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireB
> ooter.java:290)
> > > > > at
> > > > >
> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:818
> )
> > > > > [INFO]
> ------------------------------------------------------------------------
> > > > > [ERROR] BUILD FAILURE
> > > > > [INFO]
> ------------------------------------------------------------------------
> > > > >
> > > > >
> > > > > Can anyone confirm this or is my maven broken again?
> > > > >
> > > > > Torsten
> > > > >
> > > > >
> > >
> > >
>
