[
https://issues.apache.org/jira/browse/JCR-2757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Douglas Jose updated JCR-2757:
------------------------------
Attachment: maven.log
Maven 3.0 was released on 8 October 2010. No compatibility issues were observed.
No warnings could be found when running 'clean install' goals on trunk with
Maven 3.0 (see attached output).
> Maven 3 cleanups
> ----------------
>
> Key: JCR-2757
> URL: https://issues.apache.org/jira/browse/JCR-2757
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: maven
> Reporter: Jukka Zitting
> Priority: Minor
> Attachments: maven.log
>
>
> Maven 3 is already in the beta phase and Jackrabbit builds fine with it, but
> there are a few warnings about deprecated or otherwise troublesome POM
> features that we use. I'd like to get rid of these wrarnings, to avoid
> problems down the line with Maven 3 builds or other tools like IDE
> integration that leverages Maven 3.
> For now it looks like there aren't any major new POM-level features in Maven
> 3 that would justify upgrading from our current requirement of Maven 2.0.9 or
> higher. I expect people to upgrade to Maven 3 incrementally based on the
> improveed speed and flexibility it offers. We can consider a forced upgrade
> later on when there are significant new features or bug fixes that we want to
> leverage.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
