[ 
https://issues.apache.org/jira/browse/MCHANGES-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)

Reply via email to