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-6043) Make JQL default query mode for 'ant genrelnotes'
Date Thu, 17 Jan 2013 09:26:13 GMT

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

Kristian Waagan updated DERBY-6043:
-----------------------------------

    Issue & fix info:   (was: Patch Available)
       Fix Version/s: 10.10.0.0

Thanks, Rick.

You can do this behind a firewall, but then you have to instruct ant to use a proxy. Maybe
-autoproxy works for you, but it didn't on my system. I had to specify -Dhttp[s].proxyHost
and -Dhttp[s].proxyPort. You can put these properties in ANT_OPTS and they will be picked
up automatically.
Note that the first part of the ant target uses HTTP, whereas the last part (fetching the
release notes) uses HTTPS. This means you have to specify a proxy for both protocols.

Committed to trunk with revision 1434599.
                
> Make JQL default query mode for 'ant genrelnotes'
> -------------------------------------------------
>
>                 Key: DERBY-6043
>                 URL: https://issues.apache.org/jira/browse/DERBY-6043
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions: 10.10.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>             Fix For: 10.10.0.0
>
>         Attachments: derby-6043-1a-make_jql_default.diff
>
>
> The ant target genrelnotes (from tools/release/build.xml) should use JQL querying mode
by default, such that you don't have to specify jira.filter.id when invoking it.
> It will still be possible to specify jira.filter.id to instruct the tool to use an existing
JIRA filter if that is required for some reason.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message