Hi David,
You might want to wrap the test in a custom Ant Task. These are
described in the Ant manual: "Developing with Ant"->"Writing Your Own
Task". You can then check the return status of the task and fail the
build if appropriate.
Regards,
-Rick
David Van Couvering wrote:
Hm, a build-time check. I guess in a way it is a build-time issue.
Let me think about how I might do that, thanks for the idea.
David
Daniel John Debrunner wrote:
David Van Couvering wrote:
So, as Andrew very astutely pointed out, i18n/MessageBundleTest.java
will not succeed when running against the jar files because it tries to
load shared/common/reference/SQLState, which is not included in the jar
files. This problem also exists for MessageId.java, which this test
also refers to and which also is not included in the jar files.
Does this need to be a test, could it be converted into a build time
check? Then there are no requirements for these classes to be in
derbytesting.jar. Also there is probably no requirement to run this test
on different platforms.
I used to have something similar (pre-open source), that found messages
that existed but were never used.
Dan.
