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 "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2014/01/13 17:58:53 UTC
[jira] [Commented] (DERBY-5463) ant release should not modify
drdamaint version
[ https://issues.apache.org/jira/browse/DERBY-5463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13869687#comment-13869687 ]
Knut Anders Hatlen commented on DERBY-5463:
-------------------------------------------
This bug seems to have bitten us again. The DRDA maintenance version was reset to 0 on the 10.8 branch in revision 1557213, which makes derbynet.PrepareStatementTest.testLongColumn fail: http://download.java.net/javadesktop/derby/request_5586103/
> 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
> Priority: Minor
>
> 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)