On Mar 2, 2006, at 1:13 PM, Andrus Adamchik wrote:
> I just refactored the JPA project to fully rely on maven pom. So
> command line builds are now pretty simple ("mvn package"). Maven
> still mystifies me. Working with pom is like editing a Word
> document in vi. Although once you figure it out, it works.
>
> Now you'll need a Maven Eclipse plugin to work with the project:
>
> http://maven.apache.org/eclipse-plugin.html
>
> Regarding the plugin, I noticed that it overwrites JRE_LIB_15 in
> ".classpath" when you do "Update Source Folders". Also feels like
> alpha quality technology. If it gets too much in the way, we can
> just define a variable pointing to the local m2 repo and switch
> back to vanilla Eclipse.
>
The plugin is alpha/beta so expect some stuff to work too well. Most
day to day simple stuff works fine for me though.
Remember with mvn you can always get a good eclipse project and class
path with;
mvn eclipse:clean eclipse:eclipse
>
> I will update Wiki with the new setup requirements soon and then
> will move on to CAY-458 - the tck. I'll probably set it up as an
> independent m2 project, as the test fixtures setup is somewhat
> involved.
>
> M2 question to Bill or anyone more knowledgeable - how do we
> generate an HTML report for the unit tests? Current POM seems to
> have everything needed (judging from the docs), still no report is
> generated on mvn test
>
>
Its a setting in the pom, add
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
</plugin>
to the build/plugins element just past the 1.5 compiler setting
That will cause the xml reports to get generated, the html reports
will take me a few minutes to get looked up.
I would be glad to submit this as a patch if that is better.
TTFN,
-bd-
> Andrus
>
>
>
Bill Dudney
MyFaces - myfaces.apache.org
Wadi - incubator.apache.org/wadi
This archive was generated by hypermail 2.0.0 : Thu Mar 02 2006 - 15:43:49 EST