[jira] [Comment Edited] (MCHANGES-388) Add option to include issues using the -SNAPSHOT suffix for version/milestone
[ https://issues.apache.org/jira/browse/MCHANGES-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16476702#comment-16476702 ] Marcelo Riss edited comment on MCHANGES-388 at 5/16/18 1:29 AM: I already have a solution at this commit at a fork in my github account: [https://github.com/MRISS-Projects/maven-changes-plugin/commit/90aa0b1b8817e9dc7e7c0ac93799e965957cd584]. Just ignore the changes at the pom.xml file, which I needed to change in order to make an specific deployment for testing. I also haven't implemented any integration test. was (Author: mriss): I already have a solution at this commit at a fork in my github account: [https://github.com/MRISS-Projects/maven-changes-plugin/commit/90aa0b1b8817e9dc7e7c0ac93799e965957cd584]. Just ignore the changes at the pom.xml file, which I need to change to do an specific deployment for testing. I also haven't implemented any integration test. > Add option to include issues using the -SNAPSHOT suffix for version/milestone > - > > Key: MCHANGES-388 > URL: https://issues.apache.org/jira/browse/MCHANGES-388 > Project: Maven Changes Plugin > Issue Type: Wish > Components: github >Reporter: Marcelo Riss >Priority: Minor > Attachments: pom.xml > > > I have a use case where the version id/name at the issue tracking system > (GHE) will have the -SNAPSHOT suffix. Currently, when setting GHE as issue > tracking system and the parameter > *[onlyCurrentVersion|http://maven.apache.org/plugins/maven-changes-plugin/github-report-mojo.html#onlyCurrentVersion]* > to true, the -SNAPSHOT suffix is removed when filtering the issues. My > suggestion is to add a configuration parameter allowing to consider or not > the -SNAPSHOT suffix as the version id/name when searching for issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (MCHANGES-388) Add option to include issues using the -SNAPSHOT suffix for version/milestone
[ https://issues.apache.org/jira/browse/MCHANGES-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16476702#comment-16476702 ] Marcelo Riss edited comment on MCHANGES-388 at 5/16/18 1:28 AM: I already have a solution at this commit at a fork in my github account: [https://github.com/MRISS-Projects/maven-changes-plugin/commit/90aa0b1b8817e9dc7e7c0ac93799e965957cd584]. Just ignore the changes at the pom.xml file, which I need to change to do an specific deployment for testing. I also haven't implemented any integration test. was (Author: mriss): I already have a solution at this commit at a fork in my github account: [https://github.com/MRISS-Projects/maven-changes-plugin/commit/90aa0b1b8817e9dc7e7c0ac93799e965957cd584.] Just ignore the changes at the pom.xml file, which I need to change to do an specific deployment for testing. I also haven't implemented any integration test. > Add option to include issues using the -SNAPSHOT suffix for version/milestone > - > > Key: MCHANGES-388 > URL: https://issues.apache.org/jira/browse/MCHANGES-388 > Project: Maven Changes Plugin > Issue Type: Wish > Components: github >Reporter: Marcelo Riss >Priority: Minor > Attachments: pom.xml > > > I have a use case where the version id/name at the issue tracking system > (GHE) will have the -SNAPSHOT suffix. Currently, when setting GHE as issue > tracking system and the parameter > *[onlyCurrentVersion|http://maven.apache.org/plugins/maven-changes-plugin/github-report-mojo.html#onlyCurrentVersion]* > to true, the -SNAPSHOT suffix is removed when filtering the issues. My > suggestion is to add a configuration parameter allowing to consider or not > the -SNAPSHOT suffix as the version id/name when searching for issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MCHANGES-388) Add option to include issues using the -SNAPSHOT suffix for version/milestone
[ https://issues.apache.org/jira/browse/MCHANGES-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16476702#comment-16476702 ] Marcelo Riss commented on MCHANGES-388: --- I already have a solution at this commit at a fork in my github account: [https://github.com/MRISS-Projects/maven-changes-plugin/commit/90aa0b1b8817e9dc7e7c0ac93799e965957cd584.] Just ignore the changes at the pom.xml file, which I need to change to do an specific deployment for testing. I also haven't implemented any integration test. > Add option to include issues using the -SNAPSHOT suffix for version/milestone > - > > Key: MCHANGES-388 > URL: https://issues.apache.org/jira/browse/MCHANGES-388 > Project: Maven Changes Plugin > Issue Type: Wish > Components: github >Reporter: Marcelo Riss >Priority: Minor > Attachments: pom.xml > > > I have a use case where the version id/name at the issue tracking system > (GHE) will have the -SNAPSHOT suffix. Currently, when setting GHE as issue > tracking system and the parameter > *[onlyCurrentVersion|http://maven.apache.org/plugins/maven-changes-plugin/github-report-mojo.html#onlyCurrentVersion]* > to true, the -SNAPSHOT suffix is removed when filtering the issues. My > suggestion is to add a configuration parameter allowing to consider or not > the -SNAPSHOT suffix as the version id/name when searching for issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MCHANGES-388) Add option to include issues using the -SNAPSHOT suffix for version/milestone
[ https://issues.apache.org/jira/browse/MCHANGES-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcelo Riss updated MCHANGES-388: -- Attachment: pom.xml > Add option to include issues using the -SNAPSHOT suffix for version/milestone > - > > Key: MCHANGES-388 > URL: https://issues.apache.org/jira/browse/MCHANGES-388 > Project: Maven Changes Plugin > Issue Type: Wish > Components: github >Reporter: Marcelo Riss >Priority: Minor > Attachments: pom.xml > > > I have a use case where the version id/name at the issue tracking system > (GHE) will have the -SNAPSHOT suffix. Currently, when setting GHE as issue > tracking system and the parameter > *[onlyCurrentVersion|http://maven.apache.org/plugins/maven-changes-plugin/github-report-mojo.html#onlyCurrentVersion]* > to true, the -SNAPSHOT suffix is removed when filtering the issues. My > suggestion is to add a configuration parameter allowing to consider or not > the -SNAPSHOT suffix as the version id/name when searching for issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MCHANGES-388) Add option to include issues using the -SNAPSHOT suffix for version/milestone
[
https://issues.apache.org/jira/browse/MCHANGES-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16473306#comment-16473306
]
Marcelo Riss commented on MCHANGES-388:
---
Adding a sample pom.xm file, showing how this flag is intended to be used. For
snapshots, we manually call {{mvn -P snapshot,announcement clean install}}. For
official releases, the {{announcement}} and {{release}} profiles are
automatically added to the {{}} configuration section at maven
release plugin.
> Add option to include issues using the -SNAPSHOT suffix for version/milestone
> -
>
> Key: MCHANGES-388
> URL: https://issues.apache.org/jira/browse/MCHANGES-388
> Project: Maven Changes Plugin
> Issue Type: Wish
> Components: github
>Reporter: Marcelo Riss
>Priority: Minor
>
> I have a use case where the version id/name at the issue tracking system
> (GHE) will have the -SNAPSHOT suffix. Currently, when setting GHE as issue
> tracking system and the parameter
> *[onlyCurrentVersion|http://maven.apache.org/plugins/maven-changes-plugin/github-report-mojo.html#onlyCurrentVersion]*
> to true, the -SNAPSHOT suffix is removed when filtering the issues. My
> suggestion is to add a configuration parameter allowing to consider or not
> the -SNAPSHOT suffix as the version id/name when searching for issues.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (MCHANGES-388) Add option to include issues using the -SNAPSHOT suffix for version/milestone
[ https://issues.apache.org/jira/browse/MCHANGES-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469615#comment-16469615 ] Marcelo Riss edited comment on MCHANGES-388 at 5/9/18 10:33 PM: I have a use case where a number of SNAPSHOTS will require changes to be documented before the final release. It is to allow fast prototyping, where snapshots are less tested, but their changes still need to be documented. was (Author: mriss): I have a use case where a number of SNAPSHOTS will require changes to be documented before the final release. It is to allow fast prototyping, where snapshots are less tested, but still need to be documented. > Add option to include issues using the -SNAPSHOT suffix for version/milestone > - > > Key: MCHANGES-388 > URL: https://issues.apache.org/jira/browse/MCHANGES-388 > Project: Maven Changes Plugin > Issue Type: Wish >Reporter: Marcelo Riss >Priority: Minor > > I have a use case where the version id/name at the issue tracking system > (GHE) will have the -SNAPSHOT suffix. Currently, when setting GHE as issue > tracking system and the parameter > *[onlyCurrentVersion|http://maven.apache.org/plugins/maven-changes-plugin/github-report-mojo.html#onlyCurrentVersion]* > to true, the -SNAPSHOT suffix is removed when filtering the issues. My > suggestion is to add a configuration parameter allowing to consider or not > the -SNAPSHOT suffix as the version id/name when searching for issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MCHANGES-388) Add option to include issues using the -SNAPSHOT suffix for version/milestone
[ https://issues.apache.org/jira/browse/MCHANGES-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469615#comment-16469615 ] Marcelo Riss commented on MCHANGES-388: --- I have a use case where a number of SNAPSHOTS will require changes to be documented before the final release. It is to allow fast prototyping, where snapshots are less tested, but still need to be documented. > Add option to include issues using the -SNAPSHOT suffix for version/milestone > - > > Key: MCHANGES-388 > URL: https://issues.apache.org/jira/browse/MCHANGES-388 > Project: Maven Changes Plugin > Issue Type: Wish >Reporter: Marcelo Riss >Priority: Minor > > I have a use case where the version id/name at the issue tracking system > (GHE) will have the -SNAPSHOT suffix. Currently, when setting GHE as issue > tracking system and the parameter > *[onlyCurrentVersion|http://maven.apache.org/plugins/maven-changes-plugin/github-report-mojo.html#onlyCurrentVersion]* > to true, the -SNAPSHOT suffix is removed when filtering the issues. My > suggestion is to add a configuration parameter allowing to consider or not > the -SNAPSHOT suffix as the version id/name when searching for issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MCHANGES-388) Add option to include issues using the -SNAPSHOT suffix for version/milestone
[ https://issues.apache.org/jira/browse/MCHANGES-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468774#comment-16468774 ] Marcelo Riss commented on MCHANGES-388: --- I already have a proposal for a solution for this issue in a forked version of mvn changes plugin at github. > Add option to include issues using the -SNAPSHOT suffix for version/milestone > - > > Key: MCHANGES-388 > URL: https://issues.apache.org/jira/browse/MCHANGES-388 > Project: Maven Changes Plugin > Issue Type: Wish >Reporter: Marcelo Riss >Priority: Minor > > I have a use case where the version id/name at the issue tracking system > (GHE) will have the -SNAPSHOT suffix. Currently, when setting GHE as issue > tracking system and the parameter > *[onlyCurrentVersion|http://maven.apache.org/plugins/maven-changes-plugin/github-report-mojo.html#onlyCurrentVersion]* > to true, the -SNAPSHOT suffix is removed when filtering the issues. My > suggestion is to add a configuration parameter allowing to consider or not > the -SNAPSHOT suffix as the version id/name when searching for issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MCHANGES-388) Add option to include issues using the -SNAPSHOT suffix for version/milestone
[ https://issues.apache.org/jira/browse/MCHANGES-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcelo Riss updated MCHANGES-388: -- Priority: Minor (was: Major) > Add option to include issues using the -SNAPSHOT suffix for version/milestone > - > > Key: MCHANGES-388 > URL: https://issues.apache.org/jira/browse/MCHANGES-388 > Project: Maven Changes Plugin > Issue Type: Wish >Reporter: Marcelo Riss >Priority: Minor > > I have a use case where the version id/name at the issue tracking system > (GHE) will have the -SNAPSHOT suffix. Currently, when setting GHE as issue > tracking system and the parameter > *[onlyCurrentVersion|http://maven.apache.org/plugins/maven-changes-plugin/github-report-mojo.html#onlyCurrentVersion]* > to true, the -SNAPSHOT suffix is removed when filtering the issues. My > suggestion is to add a configuration parameter allowing to consider or not > the -SNAPSHOT suffix as the version id/name when searching for issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MCHANGES-388) Add option to include issues using the -SNAPSHOT suffix for version/milestone
[ https://issues.apache.org/jira/browse/MCHANGES-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcelo Riss updated MCHANGES-388: -- Description: I have a use case where the version id/name at the issue tracking system (GHE) will have the -SNAPSHOT suffix. Currently, when setting GHE as issue tracking system and the parameter *[onlyCurrentVersion|http://maven.apache.org/plugins/maven-changes-plugin/github-report-mojo.html#onlyCurrentVersion]* to true, the -SNAPSHOT suffix is removed when filtering the issues. My suggestion is to add a configuration parameter allowing to consider or not the -SNAPSHOT suffix as the version id/name when searching for issues. > Add option to include issues using the -SNAPSHOT suffix for version/milestone > - > > Key: MCHANGES-388 > URL: https://issues.apache.org/jira/browse/MCHANGES-388 > Project: Maven Changes Plugin > Issue Type: Wish >Reporter: Marcelo Riss >Priority: Major > > I have a use case where the version id/name at the issue tracking system > (GHE) will have the -SNAPSHOT suffix. Currently, when setting GHE as issue > tracking system and the parameter > *[onlyCurrentVersion|http://maven.apache.org/plugins/maven-changes-plugin/github-report-mojo.html#onlyCurrentVersion]* > to true, the -SNAPSHOT suffix is removed when filtering the issues. My > suggestion is to add a configuration parameter allowing to consider or not > the -SNAPSHOT suffix as the version id/name when searching for issues. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MCHANGES-388) Add option to include issues using the -SNAPSHOT suffix for version/milestone
Marcelo Riss created MCHANGES-388: - Summary: Add option to include issues using the -SNAPSHOT suffix for version/milestone Key: MCHANGES-388 URL: https://issues.apache.org/jira/browse/MCHANGES-388 Project: Maven Changes Plugin Issue Type: Wish Reporter: Marcelo Riss -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] Commented: (CONTINUUM-820) Shell script execution rights under Linux
[ http://jira.codehaus.org/browse/CONTINUUM-820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109182 ] Marcelo Riss commented on CONTINUUM-820: I have the same problem with cvs under linux. I'm using ubuntu feisty distro. Shell script execution rights under Linux - Key: CONTINUUM-820 URL: http://jira.codehaus.org/browse/CONTINUUM-820 Project: Continuum Issue Type: Bug Components: Integration - Shell Affects Versions: 1.0.3 Environment: Linux Reporter: Nicolas Cazottes Fix For: Future When adding a new shell script project, in continuum, the build does not work because of missing execution rights on the checkouted resources. The cause of the problem is that by default, a checkout with svn does not set the execution rights. Continuum should change the execution flag of the script to be executed. -- 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
[jira] Created: (MSITE-140) Internal html references are not generated in the team-list.html
Internal html references are not generated in the team-list.html Key: MSITE-140 URL: http://jira.codehaus.org/browse/MSITE-140 Project: Maven 2.x Site Plugin Type: Bug Versions: 2.0-beta-5 Reporter: Marcelo Riss Priority: Minor Fix For: 2.0 When generating changes report based on xml file (not JIRA) maven creates a link in each developer responsible by the fix/add/update. When clicking in this link it is suppose to have shown the team-list page, but showing the data about the developer. The link has an internal html reference (#somedeveloperid). But, I checked the html generated for team-list and there is no internal html #references for any developer. -- 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
