Am 2016-04-01 um 16:35 schrieb Karl Heinz Marbaise:
Hi Michael,
On 4/1/16 3:24 PM, Michael Osipov wrote:
Gesendet: Freitag, 01. April 2016 um 13:37 Uhr
Von: "Karl Heinz Marbaise" <[email protected]>
An: "Maven Developers List" <[email protected]>
Betreff: Re: [VOTE] Release Maven Changes Plugin version 2.12
Hi,
I've tested with Maven 3.0.5, 3.1.1, 3.2.5, 3.3.9, 3.4.0-SNAPSHOT
(3533599e42a4a563abca33a69ed0f34c19815479)..without any issue.
So +1 from me...
Only one question is why the live jira report does not show all 12
issues which have been fixed ?
You have probably the query with "resolution = Unresolved", don't you?
Not me...the staged site ...has that...
http://maven.apache.org/plugins-archives/maven-changes-plugin-LATEST/
Well, that's right. I ran the mvn site locally again with -X saw that
only this is executed:
$ curl https://issues.apache.org/jira/rest/api/2/search -H
"Content-Type: application/json" --data '{"jql":"project = MCHANGES AND
status in (6) AND resolution in (1) ORDER BY type ASC, key
ASC","maxResults":200,"fields":["*all"]}' -s | jq -C '.issues | length'
100
Interestingly, from this list of 100 issues a few have been selected. I
checked the source code and the fix version is only added when useJql is
set. I did and the result is:
$ curl https://issues.apache.org/jira/rest/api/2/search -H
"Content-Type: application/json" --data '{"jql":"project = MCHANGES AND
fixVersion = \"2.12\" AND status in (6) AND resolution in (1) ORDER BY
type ASC, key ASC","maxResults":200,"fields":["*all"]}' -s | jq -C
'.issues[].key'
"MCHANGES-346"
"MCHANGES-354"
"MCHANGES-358"
"MCHANGES-361"
"MCHANGES-364"
"MCHANGES-368"
"MCHANGES-305"
"MCHANGES-345"
"MCHANGES-347"
"MCHANGES-355"
"MCHANGES-356"
"MCHANGES-363"
Good catch. I will fix the config and commit it.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
