[
https://issues.apache.org/jira/browse/YETUS-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ajay Yadava updated YETUS-446:
------------------------------
Attachment: YETUS-446.00.patch
h5. Changes in -00.patch
1. Fixed the handling of non-existent versions in range
2. Fixed the issue where stacktrace gets printed if an invalid project name is
given along with a range of versions
3. Made changes to show response from server in case of error.
h5. Sample commands and their outputs after the change
{code}
releasedocmaker --project yahoo --outputdir FALCON --projecttitle 'Apache
Falcon' --version 0 --version 2 --range --index --license
Looking for 0 through 2
JIRA returns HTTP error 404: Not Found. Aborting.
Response from the server is:
{"errorMessages":["No project could be found with key 'YAHOO'."],"errors":{}}
{code}
{code}
releasedocmaker --project yahoo --outputdir FALCON --projecttitle 'Apache
Falcon' --version 56 --range --index --license
Looking for 56 through 56
JIRA returns HTTP error 404: Not Found. Aborting.
Response from the server is:
{"errorMessages":["No project could be found with key 'YAHOO'."],"errors":{}}
{code}
{code}
releasedocmaker --project yahoo --outputdir FALCON --projecttitle 'Apache
Falcon' --version 56 --index --license
JIRA returns HTTP error 400: Bad Request. Aborting.
Response from the server is:
{"errorMessages":["The value 'yahoo' does not exist for the field
'project'.","The value '56' does not exist for the field
'fixVersion'."],"errors":{}}
{code}
{code}
releasedocmaker --project falcon --outputdir FALCON --projecttitle 'Apache
Falcon' --version 0 --version 2 --index --license
JIRA returns HTTP error 400: Bad Request. Aborting.
Response from the server is:
{"errorMessages":["The value '0' does not exist for the field
'fixVersion'."],"errors":{}}
{code}
{code}
releasedocmaker --project falcon --outputdir FALCON --projecttitle 'Apache
Falcon' --version 0 --version 2 --range --index --license
Looking for 0 through 2
Adding 0.3 to the list
Adding 0.4 to the list
Adding 0.5 to the list
Adding 0.6 to the list
Adding 0.6.1 to the list
Adding 0.7 to the list
Adding 0.8 to the list
Adding 0.9 to the list
Adding 0.10 to the list
Adding 0.81 to the list
Adding 1.0 to the list
There is no issue which has the specified version: 0.81
{code}
> releasedocmaker not handling 0 version in a range correctly?
> ------------------------------------------------------------
>
> Key: YETUS-446
> URL: https://issues.apache.org/jira/browse/YETUS-446
> Project: Yetus
> Issue Type: Bug
> Components: Release Doc Maker
> Affects Versions: 0.4.0
> Reporter: Allen Wittenauer
> Assignee: Ajay Yadava
> Attachments: YETUS-446.00.patch
>
>
> Playing around this morning, I seem to have hit an interesting bug.
> {code}
> releasedocmaker --project FALCON --outputdir FALCON --projecttitle 'Apache
> Falcon' --version 0 --version 1 --range --index --license
> {code}
> results in this URL getting generated:
> {code}
> https://issues.apache.org/jira/rest/api/2/search?jql=project+in+%28%27FALCON%27%29+and++++++++++++++++fixVersion+in+%28%270.0%27%29+and++++++++++++++++resolution+%3D+Fixed&startAt=0&maxResults=100
> {code}
> A completely valid URL. However, RDM reports on the screen:
> {code}
> JIRA returns HTTP error 400: Bad Request. Aborting.
> Please make sure the specified projects are correct.
> {code}
> whereas JIRA spits back
> {code}
> {"errorMessages":["The value '0.0' does not exist for the field
> 'fixVersion'."],"errors":{}}
> {code}
> So somewhere we are generating an invalid version and not verifying it with
> JIRA. Additionally, our error message is wrong which isn't going to help the
> user at all. :(
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
