You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2005/11/28 22:12:06 UTC
[jira] Created: (MPA-30) Create new top-level SVN space for shared Maven-ish code
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
Assigned to: John Casey
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
[jira] Commented: (MPA-30) Create new top-level SVN space for shared Maven-ish code
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPA-30?page=comments#action_52232 ]
John Casey commented on MPA-30:
-------------------------------
the original discussion is here: http://marc.theaimsgroup.com/?t=113078654300003&r=1&w=2
> 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: John Casey
>
> Original Estimate: 30 minutes
> Remaining: 30 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
[jira] Updated: (MPA-30) Create new top-level SVN space for shared
Maven-ish code
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPA-30?page=all ]
Jason van Zyl updated MPA-30:
-----------------------------
Fix Version: 2006-q1
> 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: 2006-q1
>
> 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
[jira] Closed: (MPA-30) Create new top-level SVN space for shared
Maven-ish code
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Closed: (MPA-30) Create new top-level SVN space for shared Maven-ish code
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPA-30?page=all ]
John Casey 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: John Casey
>
> 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
[jira] Commented: (MPA-30) Create new top-level SVN space for shared Maven-ish code
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPA-30?page=comments#action_52235 ]
John Casey commented on MPA-30:
-------------------------------
new space is at: https://svn.apache.org/repos/asf/maven/shared
/trunk
/branches
/tags
> 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: John Casey
>
> 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
[jira] Updated: (MPA-30) Create new top-level SVN space for shared
Maven-ish code
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPA-30?page=all ]
Jason van Zyl updated MPA-30:
-----------------------------
Fix Version: (was: 2006-q1)
2005-q4
perms updated
> 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
[jira] Reopened: (MPA-30) Create new top-level SVN space for shared Maven-ish code
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPA-30?page=all ]
Brett Porter reopened MPA-30:
-----------------------------
do we need Jason to allocate permissions other than maven-pmc? Maybe all plugins committers?
> 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: John Casey
>
> 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
[jira] Commented: (MPA-30) Create new top-level SVN space for shared Maven-ish code
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPA-30?page=comments#action_52251 ]
John Casey commented on MPA-30:
-------------------------------
right, forgot that. Yeah, I think all plugins committers should have access.
> 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: John Casey
>
> 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