Mailing-List: contact jackrabbit-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jackrabbit-dev@incubator.apache.org
Message-ID: <388527119.1142190459503.JavaMail.jira@ajax>
Date: Sun, 12 Mar 2006 19:07:39 +0000 (GMT)
From: "Jukka Zitting (JIRA)" <jira@apache.org>
To: jackrabbit-dev@incubator.apache.org
Subject: [jira] Commented: (JCR-332) maven2 pom contribution
In-Reply-To: <1203744276.1141497701384.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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

Jukka Zitting commented on JCR-332:
-----------------------------------

Great work! I'd be happy to migrate to Maven2 once the 1.0 release is out.

What do you think would be the best way to handle the JTA and JCR dependencies? In the current Maven1 project.xml we are pointing to the JTA jar in geronimo-spec to avoid forcing the user to manually download the API jar. Should we do that as well in the Maven2 pom.xml? The Maven2 configuration also complains about the POM of the JCR API jar. Should Day provide a Maven2 version of the JCR API POM or can we work around this?

I like your idea about the test configuration. The test suite could do with some simple restructuring in any case, but we are somewhat constrained by the JSR TCK test cases being hosted in org.apache.jackrabbit.test.

> maven2 pom contribution
> -----------------------
>
>          Key: JCR-332
>          URL: http://issues.apache.org/jira/browse/JCR-332
>      Project: Jackrabbit
>         Type: New Feature
>   Components: maven
>     Reporter: fabrizio giustina
>     Priority: Minor
>  Attachments: pom.xml, pom.xml
>
> 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