incubator-jspwiki-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Mazza (JIRA)" <>
Subject [jira] [Commented] (JSPWIKI-651) Convert JSPWiki to a Maven project
Date Sun, 16 Dec 2012 21:20:12 GMT


Glen Mazza commented on JSPWIKI-651:

Oh, for that issue "However, if I make an "ant compile; mvn clean test" then I only get 21
failures (related to hsqldb), and 94 errors, most of them because "JSPWiki: Unable to load
and setup properties from Failed to start managers:
Unable to find web.xml for processing."  that's because we don't have a WAR yet for testing
-- those are the web (integration) tests in item (4) in my posting at 15:42.  If we can identify
the tests which are web tests, and rename those with the "IT" extension, Maven will ignore
them during unit testing (mvn test) but run them during later integration testing (mvn integration-test,
see the links I provided at (4) above) once a WAR is created (using the commented-out maven-war-plugin
in the pom).  The Ant script would just need a minor tweaking to run tests that end with "IT"
in addition to just "Test", so it will run as before.  (We also should eventually upgrade
the JUnit tests to JUnit 4, I don't know when that can be factored it.)
> Convert JSPWiki to a Maven project
> ----------------------------------
>                 Key: JSPWIKI-651
>                 URL:
>             Project: JSPWiki
>          Issue Type: Improvement
>            Reporter: Daniel Johansson
>            Priority: Trivial
>              Labels: ant, build, ivy, maven
>         Attachments: pom.xml
> Hello there, I was hoping to maybe one day contribute to the JSPWiki project and after
having checked out the trunk code and played around somewhat I was thinking it would be very
nice if this project used Maven.
> I'm sure most of you are familiar with Maven in one way or another, you might even have
a really good reason for not doing this to JSPWiki.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message