db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Storta Jr. (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4341) Building with ant all with a different CLASSPATH defined causes the build to fail
Date Wed, 17 Feb 2010 18:24:28 GMT

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

John Storta Jr. commented on DERBY-4341:
----------------------------------------

Sorry about the -v.  That was how it was specified in the original posting so that is what
I was using in all of my testing.  It does work without the -v, and the output is naturally
much cleaner.

Here is what the output shows if it finds a failure.
$ ant runmessagecheck
Buildfile: build.xml

runmessagecheck:
     [java] WARNING: Message id 99999 in messages_en.properties is not referenced in either
SQLState.java or MessageId.java
     [java] Exception in thread "main" java.lang.Exception: Message check failed. 
     [java] See error in build output or call ant runmessagecheck.
     [java] 	at org.apache.derbyBuild.MessageBundleTest.main(MessageBundleTest.java:68)

BUILD FAILED
/public/dev/svnwork/derby/build.xml:513: Java returned: 1

Total time: 0 seconds
$


If no issues, you get the following.
$ ant runmessagecheck
Buildfile: build.xml

runmessagecheck:

BUILD SUCCESSFUL
Total time: 0 seconds
$


Outputs are the same regardless of whether or not the CLASSPATH is set.




> Building with ant all with a different CLASSPATH defined causes the build to fail
> ---------------------------------------------------------------------------------
>
>                 Key: DERBY-4341
>                 URL: https://issues.apache.org/jira/browse/DERBY-4341
>             Project: Derby
>          Issue Type: Bug
>          Components: Build tools
>    Affects Versions: 10.6.0.0
>            Reporter: Tiago R. Espinha
>            Assignee: John Storta Jr.
>         Attachments: derby-4341.patch
>
>
> The problem happens when we are trying to compile the source code in a folder and have
the CLASSPATH variable set to a different code tree folder. This results in compile failures
like the following:
> runmessagecheck:
> [runMessageBundleTest] WARNING: Message id 22011.S.1 in messages_en.properties is not
referenced in either SQLState.java or MessageId.java
> [runMessageBundleTest] WARNING: Message id 42Y03.S.0 in messages_en.properties is not
referenced in either SQLState.java or MessageId.java
> [runMessageBundleTest] WARNING: Message id 42Y03.S.1 in messages_en.properties is not
referenced in either SQLState.java or MessageId.java
> [runMessageBundleTest] WARNING: Message id 42Y03.S.2 in messages_en.properties is not
referenced in either SQLState.java or MessageId.java
> BUILD FAILED
> /home/tiago/Desktop/DerbyStuff/CodeTenFiveTwo/build.xml:514: Message check failed. 
> See error in build output or call ant runmessagecheck.
> Total time: 1 minute 11 seconds
> This should be an easy fix and it is marked as a bug, since it doesn't seem very logical
for the compiling process to be CLASSPATH-dependent. Note that unsetting the CLASSPATH altogether
allows the compile to run without errors, so clearly this variable isn't needed and shouldn't
be used when it is set.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message