[jira] Updated: (JCR-332) maven2 pom contribution

["Przemo Pakulski (JIRA)" <ji...@apache.org>]

     [ http://issues.apache.org/jira/browse/JCR-332?page=all ]

Przemo Pakulski updated JCR-332:
--------------------------------

    Attachment: maven2-test.patch

Patch (maven2-test.patch) containing following changes added:
- dependencies to xerces, xercesXMLApis added again (jackrabbit-core is still dependent on Xerces directly during runtime, I post some comments on JCR-367),
- deleteSources, prepareTestRepository, cleanTestData ant targets added to make possible running tests on Maven2, all ant targets extracted to external build.xml file (as suggested by Maven docs),
- maven-surefire-plugin configuration changed (to run initialization tests first before others), 
- minor changes in resources, test-resources (based maven1 project.xml file),
- minor changes in javacc goal (to reuse single directory for generated sources and timestamps).

> maven2 pom contribution
> -----------------------
>
>                 Key: JCR-332
>                 URL: http://issues.apache.org/jira/browse/JCR-332
>             Project: Jackrabbit
>          Issue Type: New Feature
>          Components: maven
>    Affects Versions: 0.9, 1.0, 1.0.1
>            Reporter: fabrizio giustina
>         Assigned To: Jukka Zitting
>            Priority: Minor
>         Attachments: jackrabbit-core_single-line-description_pom.xml.patch, jackrabbit-jcr-rmi_scm.patch, jackrabbit-jcr-rmi_single-line-description-and-rmic_pom.xml.patch, jcr-rmi-pom.xml, maven2-test.patch, pom.xml, pom.xml, pom.xml.patch
>
>
> If you are interested in migrating to maven2 (or adding optional maven 2 build scripts) this is a full maven 2 pom.xml for the main jackrabbit jar.
> All the xpath/javacc stuff, previously done in maven.xml, was pretty painfull to reproduce in maven2... the attached pom exactly reproduces the m1 build by using the maven2 javacc plugin + a couple of antrun executions.
> Test configuration is not yet complete, I think it will be a lot better to reproduce the previous behaviour (init tests run first) without any customization (maybe using a single junit test suite with setUp tasks). Also custom packaging goals added to maven.xml (that can be esily done in m2 by using the assembly plugin) are not yet reproduced too.
> If there is interest, I can also provide poms for the contribution projects (that will be easy, the only complex pom is the main one).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira