You are viewing a plain text version of this content. The canonical link for it is here.
Posted to m2-dev@maven.apache.org by ji...@codehaus.org on 2005/02/07 00:02:14 UTC
[jira] Updated: (MNG-96) Define a clear best practice for dependency version management
The following issue has been updated:
Updater: Brett Porter (mailto:brett@codehaus.org)
Date: Sun, 6 Feb 2005 6:01 PM
Changes:
Fix Version changed to 1.0-alpha-1
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/browse/MNG-96?page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MNG-96
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MNG-96
Summary: Define a clear best practice for dependency version management
Type: Task
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: m2
Fix Fors:
1.0-alpha-1
Assignee:
Reporter: Jason van Zyl
Created: Sat, 16 Oct 2004 12:06 AM
Updated: Sun, 6 Feb 2005 6:01 PM
Description:
Currently in m1 this can be accomplished with entities (which is awful), the regular properties file coupled with standard interpolation and the JAR override feature.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira