Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <4161867.1172481185538.JavaMail.jira@brutus>
Date: Mon, 26 Feb 2007 01:13:05 -0800 (PST)
From: "Jukka Zitting (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Resolved: (JCR-767) Use Maven dependency management
In-Reply-To: <27270271.1172442966471.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/JCR-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting resolved JCR-767.
-------------------------------

    Resolution: Fixed

Switched to Maven <dependenyManagement/> in revision 511761.

> Use Maven dependency management
> -------------------------------
>
>                 Key: JCR-767
>                 URL: https://issues.apache.org/jira/browse/JCR-767
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: maven
>            Reporter: Jukka Zitting
>         Assigned To: Jukka Zitting
>            Priority: Minor
>             Fix For: 1.3
>
>
> Many of the Jackrabbit components have dependencies to each other and to external libraries,
> whose versions should ideally be the same for all the Jackrabbit components. To guarantee
> the use of same depedency versions and to simplify overall depedency management we should
> start using the Maven depedencyManagement feature in the Jackrabbit parent pom.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.