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 "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2014/11/13 02:54:43 UTC
[jira] [Assigned] (DERBY-6769) sane.derbyTesting.jar.lastcontents
can be "out of date" but no build error results
[ https://issues.apache.org/jira/browse/DERBY-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren reassigned DERBY-6769:
-----------------------------------------
Assignee: Myrna van Lunteren
> 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)