You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Julian Wood (JIRA)" <ji...@codehaus.org> on 2005/10/27 02:05:11 UTC
[jira] Created: (MNG-1336) the issue management report should handle more issue management systems
the issue management report should handle more issue management systems
-----------------------------------------------------------------------
Key: MNG-1336
URL: http://jira.codehaus.org/browse/MNG-1336
Project: Maven 2
Type: Improvement
Components: maven-project-info-reports-plugin
Versions: 2.0 (RC)
Environment: osx 10.4.2, java 1.4.2_09
Reporter: Julian Wood
Priority: Trivial
Fix For: 2.0.1
We use mantis as an issue-tracking management system, and I wanted this report to reflect that choice. Before I get into that though, one tiny grammar mistake should be fixed first in the project-info-report.properties:
report.issuetracking.general.intro=This project uses an Issue Management System to manage its issues.
Note the "an Issue", rather than "a issue". This led me to believe that maven was not grabbing the system I specified in the pom and making the proper substitution (ie ... a Mantis Issue Management ...). Of course that wasn't at all the case.
Looking at the code, it was easy to add Mantis as an option, but why should one need to specify a valid system in code, and then in the properties file? And then make my customized version of the plugin available to the team? Just so that we can have a custom link to our IM system.
Well, I don't think that is going to get fixed, because that would mean a change in the POM, so if Mantis can simply be added to the list of valid IM systems:
report.issuetracking.mantis.intro=This project uses {Mantis, http://www.mantisbt.org/}.
and then the corresponding change in IssueTrackingReport.renderBody()
Thanks.
--
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: (MNG-1336) the issue management report should handle more issue management systems
Posted by "Julian Wood (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1336?page=comments#action_49515 ]
Julian Wood commented on MNG-1336:
----------------------------------
This patch works fine for me, though unlike the other systems, you can't specify a URL, AFAICT. But maybe that is just to nitpicky :-)
Cheers,
J
> the issue management report should handle more issue management systems
> -----------------------------------------------------------------------
>
> Key: MNG-1336
> URL: http://jira.codehaus.org/browse/MNG-1336
> Project: Maven 2
> Type: Improvement
> Components: maven-project-info-reports-plugin
> Versions: 2.0 (RC)
> Environment: osx 10.4.2, java 1.4.2_09
> Reporter: Julian Wood
> Assignee: Johnny R. Ruiz III
> Priority: Trivial
> Fix For: 2.0.1
> Attachments: MNG-1336-project-info-reports-plugin.patch
>
> Original Estimate: 3 hours
> Remaining: 3 hours
>
> We use mantis as an issue-tracking management system, and I wanted this report to reflect that choice. Before I get into that though, one tiny grammar mistake should be fixed first in the project-info-report.properties:
> report.issuetracking.general.intro=This project uses an Issue Management System to manage its issues.
> Note the "an Issue", rather than "a issue". This led me to believe that maven was not grabbing the system I specified in the pom and making the proper substitution (ie ... a Mantis Issue Management ...). Of course that wasn't at all the case.
> Looking at the code, it was easy to add Mantis as an option, but why should one need to specify a valid system in code, and then in the properties file? And then make my customized version of the plugin available to the team? Just so that we can have a custom link to our IM system.
> Well, I don't think that is going to get fixed, because that would mean a change in the POM, so if Mantis can simply be added to the list of valid IM systems:
> report.issuetracking.mantis.intro=This project uses {Mantis, http://www.mantisbt.org/}.
> and then the corresponding change in IssueTrackingReport.renderBody()
> Thanks.
--
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: (MNG-1336) the issue management report should handle more issue management systems
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1336?page=all ]
Brett Porter reopened MNG-1336:
-------------------------------
I don't think this was applied yet?
> the issue management report should handle more issue management systems
> -----------------------------------------------------------------------
>
> Key: MNG-1336
> URL: http://jira.codehaus.org/browse/MNG-1336
> Project: Maven 2
> Type: Improvement
> Components: maven-project-info-reports-plugin
> Versions: 2.0 (RC)
> Environment: osx 10.4.2, java 1.4.2_09
> Reporter: Julian Wood
> Assignee: Johnny R. Ruiz III
> Priority: Trivial
> Fix For: 2.0.1
> Attachments: MNG-1336-project-info-reports-plugin.patch
>
> Original Estimate: 3 hours
> Remaining: 3 hours
>
> We use mantis as an issue-tracking management system, and I wanted this report to reflect that choice. Before I get into that though, one tiny grammar mistake should be fixed first in the project-info-report.properties:
> report.issuetracking.general.intro=This project uses an Issue Management System to manage its issues.
> Note the "an Issue", rather than "a issue". This led me to believe that maven was not grabbing the system I specified in the pom and making the proper substitution (ie ... a Mantis Issue Management ...). Of course that wasn't at all the case.
> Looking at the code, it was easy to add Mantis as an option, but why should one need to specify a valid system in code, and then in the properties file? And then make my customized version of the plugin available to the team? Just so that we can have a custom link to our IM system.
> Well, I don't think that is going to get fixed, because that would mean a change in the POM, so if Mantis can simply be added to the list of valid IM systems:
> report.issuetracking.mantis.intro=This project uses {Mantis, http://www.mantisbt.org/}.
> and then the corresponding change in IssueTrackingReport.renderBody()
> Thanks.
--
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: (MNG-1336) the issue management report should handle more issue management systems
Posted by "Julian Wood (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1336?page=all ]
Julian Wood closed MNG-1336:
----------------------------
Resolution: Fixed
> the issue management report should handle more issue management systems
> -----------------------------------------------------------------------
>
> Key: MNG-1336
> URL: http://jira.codehaus.org/browse/MNG-1336
> Project: Maven 2
> Type: Improvement
> Components: maven-project-info-reports-plugin
> Versions: 2.0 (RC)
> Environment: osx 10.4.2, java 1.4.2_09
> Reporter: Julian Wood
> Assignee: Johnny R. Ruiz III
> Priority: Trivial
> Fix For: 2.0.1
> Attachments: MNG-1336-project-info-reports-plugin.patch
>
> Original Estimate: 3 hours
> Remaining: 3 hours
>
> We use mantis as an issue-tracking management system, and I wanted this report to reflect that choice. Before I get into that though, one tiny grammar mistake should be fixed first in the project-info-report.properties:
> report.issuetracking.general.intro=This project uses an Issue Management System to manage its issues.
> Note the "an Issue", rather than "a issue". This led me to believe that maven was not grabbing the system I specified in the pom and making the proper substitution (ie ... a Mantis Issue Management ...). Of course that wasn't at all the case.
> Looking at the code, it was easy to add Mantis as an option, but why should one need to specify a valid system in code, and then in the properties file? And then make my customized version of the plugin available to the team? Just so that we can have a custom link to our IM system.
> Well, I don't think that is going to get fixed, because that would mean a change in the POM, so if Mantis can simply be added to the list of valid IM systems:
> report.issuetracking.mantis.intro=This project uses {Mantis, http://www.mantisbt.org/}.
> and then the corresponding change in IssueTrackingReport.renderBody()
> Thanks.
--
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: (MNG-1336) the issue management report should handle more issue management systems
Posted by "Julian Wood (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1336?page=comments#action_52372 ]
Julian Wood commented on MNG-1336:
----------------------------------
Yes quite right - sorry about that.
> the issue management report should handle more issue management systems
> -----------------------------------------------------------------------
>
> Key: MNG-1336
> URL: http://jira.codehaus.org/browse/MNG-1336
> Project: Maven 2
> Type: Improvement
> Components: maven-project-info-reports-plugin
> Versions: 2.0 (RC)
> Environment: osx 10.4.2, java 1.4.2_09
> Reporter: Julian Wood
> Assignee: Johnny R. Ruiz III
> Priority: Trivial
> Fix For: 2.0.1
> Attachments: MNG-1336-project-info-reports-plugin.patch
>
> Original Estimate: 3 hours
> Remaining: 3 hours
>
> We use mantis as an issue-tracking management system, and I wanted this report to reflect that choice. Before I get into that though, one tiny grammar mistake should be fixed first in the project-info-report.properties:
> report.issuetracking.general.intro=This project uses an Issue Management System to manage its issues.
> Note the "an Issue", rather than "a issue". This led me to believe that maven was not grabbing the system I specified in the pom and making the proper substitution (ie ... a Mantis Issue Management ...). Of course that wasn't at all the case.
> Looking at the code, it was easy to add Mantis as an option, but why should one need to specify a valid system in code, and then in the properties file? And then make my customized version of the plugin available to the team? Just so that we can have a custom link to our IM system.
> Well, I don't think that is going to get fixed, because that would mean a change in the POM, so if Mantis can simply be added to the list of valid IM systems:
> report.issuetracking.mantis.intro=This project uses {Mantis, http://www.mantisbt.org/}.
> and then the corresponding change in IssueTrackingReport.renderBody()
> Thanks.
--
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: (MNG-1336) the issue management report should handle more issue management systems
Posted by "Johnny R. Ruiz III (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1336?page=all ]
Johnny R. Ruiz III closed MNG-1336:
-----------------------------------
Resolution: Fixed
Applied and Fixed
> the issue management report should handle more issue management systems
> -----------------------------------------------------------------------
>
> Key: MNG-1336
> URL: http://jira.codehaus.org/browse/MNG-1336
> Project: Maven 2
> Type: Improvement
> Components: maven-project-info-reports-plugin
> Versions: 2.0 (RC)
> Environment: osx 10.4.2, java 1.4.2_09
> Reporter: Julian Wood
> Assignee: Johnny R. Ruiz III
> Priority: Trivial
> Fix For: 2.0.1
> Attachments: MNG-1336-project-info-reports-plugin.patch
>
> Original Estimate: 3 hours
> Remaining: 3 hours
>
> We use mantis as an issue-tracking management system, and I wanted this report to reflect that choice. Before I get into that though, one tiny grammar mistake should be fixed first in the project-info-report.properties:
> report.issuetracking.general.intro=This project uses an Issue Management System to manage its issues.
> Note the "an Issue", rather than "a issue". This led me to believe that maven was not grabbing the system I specified in the pom and making the proper substitution (ie ... a Mantis Issue Management ...). Of course that wasn't at all the case.
> Looking at the code, it was easy to add Mantis as an option, but why should one need to specify a valid system in code, and then in the properties file? And then make my customized version of the plugin available to the team? Just so that we can have a custom link to our IM system.
> Well, I don't think that is going to get fixed, because that would mean a change in the POM, so if Mantis can simply be added to the list of valid IM systems:
> report.issuetracking.mantis.intro=This project uses {Mantis, http://www.mantisbt.org/}.
> and then the corresponding change in IssueTrackingReport.renderBody()
> Thanks.
--
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: (MNG-1336) the issue management report should handle more issue management systems
Posted by "Johnny R. Ruiz III (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1336?page=all ]
Johnny R. Ruiz III updated MNG-1336:
------------------------------------
Attachment: MNG-1336-project-info-reports-plugin.patch
This patch enables other Issue Management System to be displayed in the report.
Please apply, thanks.
> the issue management report should handle more issue management systems
> -----------------------------------------------------------------------
>
> Key: MNG-1336
> URL: http://jira.codehaus.org/browse/MNG-1336
> Project: Maven 2
> Type: Improvement
> Components: maven-project-info-reports-plugin
> Versions: 2.0 (RC)
> Environment: osx 10.4.2, java 1.4.2_09
> Reporter: Julian Wood
> Assignee: Johnny R. Ruiz III
> Priority: Trivial
> Fix For: 2.0.1
> Attachments: MNG-1336-project-info-reports-plugin.patch
>
> Original Estimate: 3 hours
> Remaining: 3 hours
>
> We use mantis as an issue-tracking management system, and I wanted this report to reflect that choice. Before I get into that though, one tiny grammar mistake should be fixed first in the project-info-report.properties:
> report.issuetracking.general.intro=This project uses an Issue Management System to manage its issues.
> Note the "an Issue", rather than "a issue". This led me to believe that maven was not grabbing the system I specified in the pom and making the proper substitution (ie ... a Mantis Issue Management ...). Of course that wasn't at all the case.
> Looking at the code, it was easy to add Mantis as an option, but why should one need to specify a valid system in code, and then in the properties file? And then make my customized version of the plugin available to the team? Just so that we can have a custom link to our IM system.
> Well, I don't think that is going to get fixed, because that would mean a change in the POM, so if Mantis can simply be added to the list of valid IM systems:
> report.issuetracking.mantis.intro=This project uses {Mantis, http://www.mantisbt.org/}.
> and then the corresponding change in IssueTrackingReport.renderBody()
> Thanks.
--
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: (MNG-1336) the issue management report should handle more issue management systems
Posted by "Johnny R. Ruiz III (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1336?page=all ]
Johnny R. Ruiz III updated MNG-1336:
------------------------------------
Assign To: Johnny R. Ruiz III
Remaining Estimate: 3 hours
Original Estimate: 10800
> the issue management report should handle more issue management systems
> -----------------------------------------------------------------------
>
> Key: MNG-1336
> URL: http://jira.codehaus.org/browse/MNG-1336
> Project: Maven 2
> Type: Improvement
> Components: maven-project-info-reports-plugin
> Versions: 2.0 (RC)
> Environment: osx 10.4.2, java 1.4.2_09
> Reporter: Julian Wood
> Assignee: Johnny R. Ruiz III
> Priority: Trivial
> Fix For: 2.0.1
>
> Original Estimate: 3 hours
> Remaining: 3 hours
>
> We use mantis as an issue-tracking management system, and I wanted this report to reflect that choice. Before I get into that though, one tiny grammar mistake should be fixed first in the project-info-report.properties:
> report.issuetracking.general.intro=This project uses an Issue Management System to manage its issues.
> Note the "an Issue", rather than "a issue". This led me to believe that maven was not grabbing the system I specified in the pom and making the proper substitution (ie ... a Mantis Issue Management ...). Of course that wasn't at all the case.
> Looking at the code, it was easy to add Mantis as an option, but why should one need to specify a valid system in code, and then in the properties file? And then make my customized version of the plugin available to the team? Just so that we can have a custom link to our IM system.
> Well, I don't think that is going to get fixed, because that would mean a change in the POM, so if Mantis can simply be added to the list of valid IM systems:
> report.issuetracking.mantis.intro=This project uses {Mantis, http://www.mantisbt.org/}.
> and then the corresponding change in IssueTrackingReport.renderBody()
> Thanks.
--
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