You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2006/01/04 05:37:12 UTC
[jira] Closed: (MPA-30) Create new top-level SVN space for shared
Maven-ish code
[ http://jira.codehaus.org/browse/MPA-30?page=all ]
Jason van Zyl closed MPA-30:
----------------------------
Resolution: Fixed
> Create new top-level SVN space for shared Maven-ish code
> --------------------------------------------------------
>
> Key: MPA-30
> URL: http://jira.codehaus.org/browse/MPA-30
> Project: Maven Project Administration
> Type: New Feature
> Components: new projects
> Reporter: John Casey
> Assignee: Jason van Zyl
> Fix For: 2005-q4
>
> Original Estimate: 30 minutes
> Time Spent: 30 minutes
> Remaining: 0 minutes
>
> The upshot of this issue is that we have an opportunity to consolidate APIs used by many plugins and other tools tangential to Maven itself. These supporting projects should have release cycles largely independent of Maven, so we don' t have to wait for a new release of Maven to take advantage of new features/bugfixes in these libraries.
> Think Jakarta commons, only for Maven.
> I've asked for a vote to setup a new top-level SVN space for such projects, alongside components/ and plugins/. Following the template used for the mojo project at codehaus, this space will entail a single trunk/branches/tags structure.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org