db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4857) Utilize the SOAP API to fetch JIRA issue list for release notes generation
Date Tue, 26 Oct 2010 09:06:23 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kristian Waagan updated DERBY-4857:

    Attachment: derby-4857-4b-jirasoap_ant_integration.diff

Thanks, Lily.

The error you are getting means that you have specified a version as 'true', which doesn't
exist (in JIRA). Versions are supposed to be formatted as major.minor.fixpack.point, for instance
Rick's script won't work any more because the Java application now expects a different set
of arguments - this is the reason you're getting the error message above.

Now, it turns out  the current script is unable to execute Maven on Windows, even under Cygwin.
The solution is to invoke "mvn.bat" instead of "mvn".
I have added logic to determine the correct Maven executable, and I am now able to execute
'ant genrelnotes' on Windows (haven't tested if my changes broke this on *nix now...)
I'm still hoping it will be enough for people to invoke 'ant genrelnotes' from tools/release.

Attaching patch 4b. Ready for review / testing (hint: use the filter id that Rick used, and
release version

PS! Lily, you don't have to care about what's inside the 'maven2' directory. That's another,
independent Maven project.

> Utilize the SOAP API to fetch JIRA issue list for release notes generation
> --------------------------------------------------------------------------
>                 Key: DERBY-4857
>                 URL: https://issues.apache.org/jira/browse/DERBY-4857
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions:
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>         Attachments: derby-4857-1a-jirasoap_relnotes.diff, derby-4857-1a-jirasoap_relnotes.stat,
derby-4857-2a-jirasoap_maven_client.diff, derby-4857-2a-jirasoap_maven_client.stat, derby-4857-3a-jirasoap_relnotesgen_changes.diff,
derby-4857-3a-jirasoap_relnotesgen_changes.stat, derby-4857-4a-jirasoap_ant_integration.diff,
derby-4857-4a-jirasoap_ant_integration.stat, derby-4857-4b-jirasoap_ant_integration.diff,
> Somewhat simplified, the release manager (RM) must currently perform the following manual
steps to feed the release note generate the data it needs:
>  a) Create manual JIRA filter to select issues addressed by the release.
>  b) Save the filter result to disk as XML.
>  c) Write/modify the XML parser to be able to parse the report.
>  d) Determine and record all JIRA release note attachment ids for the issues requiring
a release note.
> By using the current version of the SOAP API (3.13.5), steps (b) to (d) can be removed.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message