Bill,
sorry, I was a little overworked that day and forgot to mention -
anonymous CVS has a lag of at least a few hours, so you couldn't see
my changes immediately. In fact I did bring the project in line with
the Maven standard (so the test directory is "test" and test files
are *Test.java).
What I couldn't figure out is the right command line options to
generate report. The one below works like a charm. Thanks!
Andrus
On Mar 3, 2006, at 1:00 AM, Bill Dudney wrote:
> 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-
> <pom.xml.patch>
> 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 : Fri Mar 03 2006 - 01:14:54 EST