You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2014/05/30 17:01:15 UTC

[jira] [Resolved] (DERBY-5463) ant release should not modify drdamaint version

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

Rick Hillegas resolved DERBY-5463.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 10.10.2.0
                   10.11.0.0
                   10.9.2.2
                   10.8.3.3
                   10.7.1.4

No further activity has occurred on this issue for a long time. Resolving.

> 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
>             Fix For: 10.7.1.4, 10.8.3.3, 10.9.2.2, 10.11.0.0, 10.10.2.0
>
>         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.2#6252)