You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/12/23 06:56:45 UTC
[jira] Created: (MPA-36) associate Maven svn with JIRA projects
associate Maven svn with JIRA projects
--------------------------------------
Key: MPA-36
URL: http://jira.codehaus.org/browse/MPA-36
Project: Maven Project Administration
Type: Task
Components: issue management
Reporter: Brett Porter
Assigned to: Vincent Massol
Let's do this so we can view related commits from JIRA.
First need some advice on how it needs to be done: can we assign http://svn.apache.org/repos/asf/maven to all the Maven 1.x and Maven 2.x projects, or is this really bad for performance? It would still give the right results.
If it needs to be separated, these are the patterns:
MNG - maven/components (trunk and branches) and maven/site (if possible)
MAVEN - maven/maven-1.x/core (trunk and branches)
MPxxx - maven/maven-1.x/plugins/trunk/PLUGIN-NAME
Mxxx - maven/plugins/trunk/PLUGIN-NAME
WAGON, WAGONFTP, WAGONSSH, WAGONHTTP - maven/wagon (trunk and branches)
SCM - maven/scm (trunk and branches)
CONTINUUM - maven/continuum (trunk and branches)
MRM - maven/repository-manager (trunk and branches)
JXR - maven/jxr (trunk and branches)
ARCHETYPE - maven/archetype (trunk and branches)
DOXIA - maven/doxia (trunk and branches)
SUREFIRE - maven/surefire (trunk and branches)
--
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-36) associate Maven svn with JIRA projects
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPA-36?page=comments#action_54151 ]
Brett Porter commented on MPA-36:
---------------------------------
since it's not associated with individual projects, then we'd just be adding:
svn.root.6=http://svn.apache.org/repos/asf/maven
viewcvs.url.6=http://svn.apache.org/viewcvs.cgi/maven
I think this is fine. We can turn it off if there are any performance concerns.
> associate Maven svn with JIRA projects
> --------------------------------------
>
> Key: MPA-36
> URL: http://jira.codehaus.org/browse/MPA-36
> Project: Maven Project Administration
> Type: Task
> Components: issue management
> Reporter: Brett Porter
> Assignee: Vincent Massol
> Attachments: subversion-jira-plugin.properties
>
>
> Let's do this so we can view related commits from JIRA.
> First need some advice on how it needs to be done: can we assign http://svn.apache.org/repos/asf/maven to all the Maven 1.x and Maven 2.x projects, or is this really bad for performance? It would still give the right results.
> If it needs to be separated, these are the patterns:
> MNG - maven/components (trunk and branches) and maven/site (if possible)
> MAVEN - maven/maven-1.x/core (trunk and branches)
> MPxxx - maven/maven-1.x/plugins/trunk/PLUGIN-NAME
> Mxxx - maven/plugins/trunk/PLUGIN-NAME
> WAGON, WAGONFTP, WAGONSSH, WAGONHTTP - maven/wagon (trunk and branches)
> SCM - maven/scm (trunk and branches)
> CONTINUUM - maven/continuum (trunk and branches)
> MRM - maven/repository-manager (trunk and branches)
> JXR - maven/jxr (trunk and branches)
> ARCHETYPE - maven/archetype (trunk and branches)
> DOXIA - maven/doxia (trunk and branches)
> SUREFIRE - maven/surefire (trunk and branches)
--
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-36) associate Maven svn with JIRA projects
Posted by "Vincent Massol (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPA-36?page=all ]
Vincent Massol updated MPA-36:
------------------------------
Attachment: subversion-jira-plugin.properties
> associate Maven svn with JIRA projects
> --------------------------------------
>
> Key: MPA-36
> URL: http://jira.codehaus.org/browse/MPA-36
> Project: Maven Project Administration
> Type: Task
> Components: issue management
> Reporter: Brett Porter
> Assignee: Vincent Massol
> Attachments: subversion-jira-plugin.properties
>
>
> Let's do this so we can view related commits from JIRA.
> First need some advice on how it needs to be done: can we assign http://svn.apache.org/repos/asf/maven to all the Maven 1.x and Maven 2.x projects, or is this really bad for performance? It would still give the right results.
> If it needs to be separated, these are the patterns:
> MNG - maven/components (trunk and branches) and maven/site (if possible)
> MAVEN - maven/maven-1.x/core (trunk and branches)
> MPxxx - maven/maven-1.x/plugins/trunk/PLUGIN-NAME
> Mxxx - maven/plugins/trunk/PLUGIN-NAME
> WAGON, WAGONFTP, WAGONSSH, WAGONHTTP - maven/wagon (trunk and branches)
> SCM - maven/scm (trunk and branches)
> CONTINUUM - maven/continuum (trunk and branches)
> MRM - maven/repository-manager (trunk and branches)
> JXR - maven/jxr (trunk and branches)
> ARCHETYPE - maven/archetype (trunk and branches)
> DOXIA - maven/doxia (trunk and branches)
> SUREFIRE - maven/surefire (trunk and branches)
--
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-36) associate Maven svn with JIRA projects
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPA-36?page=all ]
Jason van Zyl updated MPA-36:
-----------------------------
Fix Version: 2006-q1
> associate Maven svn with JIRA projects
> --------------------------------------
>
> Key: MPA-36
> URL: http://jira.codehaus.org/browse/MPA-36
> Project: Maven Project Administration
> Type: Task
> Components: issue management
> Reporter: Brett Porter
> Assignee: Vincent Massol
> Fix For: 2006-q1
> Attachments: subversion-jira-plugin.properties
>
>
> Let's do this so we can view related commits from JIRA.
> First need some advice on how it needs to be done: can we assign http://svn.apache.org/repos/asf/maven to all the Maven 1.x and Maven 2.x projects, or is this really bad for performance? It would still give the right results.
> If it needs to be separated, these are the patterns:
> MNG - maven/components (trunk and branches) and maven/site (if possible)
> MAVEN - maven/maven-1.x/core (trunk and branches)
> MPxxx - maven/maven-1.x/plugins/trunk/PLUGIN-NAME
> Mxxx - maven/plugins/trunk/PLUGIN-NAME
> WAGON, WAGONFTP, WAGONSSH, WAGONHTTP - maven/wagon (trunk and branches)
> SCM - maven/scm (trunk and branches)
> CONTINUUM - maven/continuum (trunk and branches)
> MRM - maven/repository-manager (trunk and branches)
> JXR - maven/jxr (trunk and branches)
> ARCHETYPE - maven/archetype (trunk and branches)
> DOXIA - maven/doxia (trunk and branches)
> SUREFIRE - maven/surefire (trunk and branches)
--
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-36) associate Maven svn with JIRA projects
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPA-36?page=all ]
Brett Porter closed MPA-36:
---------------------------
Assign To: Brett Porter (was: Vincent Massol)
Resolution: Fixed
> associate Maven svn with JIRA projects
> --------------------------------------
>
> Key: MPA-36
> URL: http://jira.codehaus.org/browse/MPA-36
> Project: Maven Project Administration
> Type: Task
> Components: issue management
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 2006-q1
> Attachments: subversion-jira-plugin.properties
>
>
> Let's do this so we can view related commits from JIRA.
> First need some advice on how it needs to be done: can we assign http://svn.apache.org/repos/asf/maven to all the Maven 1.x and Maven 2.x projects, or is this really bad for performance? It would still give the right results.
> If it needs to be separated, these are the patterns:
> MNG - maven/components (trunk and branches) and maven/site (if possible)
> MAVEN - maven/maven-1.x/core (trunk and branches)
> MPxxx - maven/maven-1.x/plugins/trunk/PLUGIN-NAME
> Mxxx - maven/plugins/trunk/PLUGIN-NAME
> WAGON, WAGONFTP, WAGONSSH, WAGONHTTP - maven/wagon (trunk and branches)
> SCM - maven/scm (trunk and branches)
> CONTINUUM - maven/continuum (trunk and branches)
> MRM - maven/repository-manager (trunk and branches)
> JXR - maven/jxr (trunk and branches)
> ARCHETYPE - maven/archetype (trunk and branches)
> DOXIA - maven/doxia (trunk and branches)
> SUREFIRE - maven/surefire (trunk and branches)
--
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