maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason van Zyl (JIRA)" <>
Subject [jira] Updated: (MPA-30) Create new top-level SVN space for shared Maven-ish code
Date Wed, 04 Jan 2006 04:31:12 GMT
     [ ]

Jason van Zyl updated MPA-30:

    Fix Version:     (was: 2006-q1)

perms updated

> Create new top-level SVN space for shared Maven-ish code
> --------------------------------------------------------
>          Key: MPA-30
>          URL:
>      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:
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message