Lily Wei wrote:
Thank you, Knut.
I was able to build all the source after changin my jdk to jdk1.6.0. I am seeing the following error when I try to build my test:
runmessagecheck:
[runMessageBundleTest] WARNING: Message id XRE04.U.2 in messages_en.properties i
s not referenced in either SQLState.java or MessageId.java
[runMessageBundleTest] WARNING: Message id XRE04.U.1 in messages_en.properties i
s not referenced in either SQLState.java or MessageId.java
[runMessageBundleTest] WARNING: Message id XRE11 in messages_en.properties is no
t referenced in either SQLState.java or MessageId.java
[runMessageBundleTest] WARNING: Message id XRE09 in messages_en.properties is no
t referenced in either SQLState.java or MessageId.java
[runMessageBundleTest] WARNING: Message id XRE05 in messages_en.properties is no
t referenced in either SQLState.java or MessageId.java
[runMessageBundleTest] WARNING: Message id XRE41 in messages_en.properties is no
t referenced in either SQLState.java or MessageId.java
[runMessageBundleTest] WARNING: Message id XRE42 in messages_en.properties is no
t referenced in either SQLState.java or MessageId.java
[runMessageBundleTest] WARNING: Message id XRE21 in messages_en.properties is no
t referenced in either SQLState.java or MessageId.java
[runMessageBundleTest] WARNING: Message id XRE22 in messages_en.properties is no
t referenced in either SQLState.java or MessageId.java
[runMessageBundleTest] WARNING: Message id 42Y03 in messages_en.properties is no
t referenced in either SQLState.java or MessageId.java
BUILD FAILED
c:\derby\trunk\build.xml:514: Message check failed.
See error in build output or call ant runmessagecheck.
at org.apache.derbyBuild.MessageBundleTest.execute(MessageBundleTest.jav
a:69)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
        at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.jav
a:106)
        at org.apache.tools.ant.Task.perform(Task.java:348)
        at org.apache.tools.ant.Target.execute(Target.java:357)
        at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
        at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExe
cutor.java:41)
        at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
        at org.apache.tools.ant.Main.runBuild(Main.java:758)
        at org.apache.tools.ant.Main.startAnt(Main.java:217)
        at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
        at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
Total time: 10 seconds
I have seen this before after recent message changes. I am guessing that perhaps the tool checks the values in the jars in your classpath instead of the build tree, but haven't verified this, because usually when I rebuild the issue goes away. Try the following from your source root:

svn update
rm -rf jars/*
ant all


Kathey

Reply via email to