Hi All,
Another problem - the test directory is named 'tests' instead of
'test' which will keep the automatic test pick up from working.
Also - the tests are named *Tst.java which will also keep the default
from working.
http://maven.apache.org/plugins/maven-surefire-plugin/howto.html
has the info on how to make it work for those interested.
I've attached a pom that runs the tests. There are several failures
though so you must tell mvn to ingore the failures like this;
mvn -Dmaven.test.failure.ignore=true surefire-report:report
after it completes you can open;
target/site/surefire-report.html
to see the reports.
let me know how it works for you...
TTFN,
-bd-
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.
>
> 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
>
> Andrus
>
>
This archive was generated by hypermail 2.0.0 : Thu Mar 02 2006 - 17:00:31 EST