db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5463) ant release should not modify drdamaint version
Date Mon, 13 Jan 2014 20:06:56 GMT

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

Rick Hillegas updated DERBY-5463:
---------------------------------

    Attachment: derby-5463-02-aa-setDRDAMaintIDBackTo_1.diff

Attaching derby-5463-02-aa-setDRDAMaintIDBackTo_1.diff. This sets drdamaint back to 1.

Touches the following file:

M       tools/ant/properties/release.properties


> ant release should not modify drdamaint version 
> ------------------------------------------------
>
>                 Key: DERBY-5463
>                 URL: https://issues.apache.org/jira/browse/DERBY-5463
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions: 10.8.2.2, 10.9.1.0
>            Reporter: Myrna van Lunteren
>            Assignee: Rick Hillegas
>            Priority: Minor
>         Attachments: derby-5463-01-aa-leaveDRDAmaintIDAlone.diff, derby-5463-02-aa-setDRDAMaintIDBackTo_1.diff
>
>
> ant release automatically sets drdamaint version to 0 in release.properties.
> However, on the 10.8 branch, drdamaint version had been increased to trigger a difference
in behavior with vs. without a particular check in; ant release caused this to get reset thus
breaking the fix.
> ant release should somehow assess the value of drdamaint.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message