db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6769) sane.derbyTesting.jar.lastcontents can be "out of date" but no build error results
Date Thu, 13 Nov 2014 04:10:33 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14209234#comment-14209234
] 

ASF subversion and git services commented on DERBY-6769:
--------------------------------------------------------

Commit 1639245 from [~myrna] in branch 'code/trunk'
[ https://svn.apache.org/r1639245 ]

DERBY-6769; sane.derbyTesting.jar.lastcontents can be "out of date" but no build error results
   updating the contents with results from a clean environment

> sane.derbyTesting.jar.lastcontents can be "out of date" but no build error results
> ----------------------------------------------------------------------------------
>
>                 Key: DERBY-6769
>                 URL: https://issues.apache.org/jira/browse/DERBY-6769
>             Project: Derby
>          Issue Type: Bug
>          Components: Build tools
>    Affects Versions: 10.11.1.1
>            Reporter: Mike Matrigali
>            Assignee: Myrna van Lunteren
>            Priority: Minor
>
> I did a SANE build against a newly created client on trunk and go no errors.
> I then did an ant refreshjardriftcheck, and it generated a change to 
> sane.derbyTesting.jar.lastcontents to be checked in, it is included at end of description.
> There seems to be 2 problems here:
> 1) sane.derbyTesting.jar.lastcontents checked in version is likely out of date and needs
to be updated.
> 2) The build should notice it is out of date and fail.
> I was led to this as I am working on a change that did add files to derby.jar
> but was confused that it was generating changes for derbyTesting.jar in my own development
client.  This is why I tried it on a clean client and ran refresh even though build was clean.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message