Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <24636401.1154430198228.JavaMail.jira@brutus>
Date: Tue, 1 Aug 2006 04:03:18 -0700 (PDT)
From: "Christoph Kiehl (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Updated: (JCR-332) maven2 pom contribution
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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

Christoph Kiehl updated JCR-332:
--------------------------------

    Attachment: pom.xml.patch

Added a patch which does the following:

- Change artifactId from "jackrabbit" to "jackrabbit-core"
- Omit generating XPath.jjt 
- Use javacc 3.2 because with 4.0 I got syntax errors
- Set system properties for unit tests

There is still some work to do to get the tests running, but at least I can build jackrabbit with "maven -Dmaven.test.skip=true install"

> 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: 1.0, 1.0.1, 0.9
>            Reporter: fabrizio giustina
>         Assigned To: Jukka Zitting
>            Priority: Minor
>             Fix For: 1.1
>
>         Attachments: 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