[
https://issues.apache.org/jira/browse/DERBY-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14209232#comment-14209232
]
Myrna van Lunteren commented on DERBY-6769:
-------------------------------------------
The differences are all class files floating around in the environment I used
to create the original lastgoodjarcontents files. I should have used a clean
environment (or have done a better job cleaning up).
It is not dependent on sane or insane.
I will update the contents.
The fact that the build does not error for these is because it does not warn
about classes going away (i.e. missing from the builds), only about classes
being added - so that part is by design.
> 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)
