db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1458) Add MessageBundleTest to build script to verify that there are no orphaned message ids
Date Fri, 17 Oct 2008 17:30:46 GMT

    [ https://issues.apache.org/jira/browse/DERBY-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640591#action_12640591

Myrna van Lunteren commented on DERBY-1458:

forgot to mention - 
1. this was in response to a thread following the build failure after I checked in my second
2. The error message above shows "failure in message check" - that's when I had the BuildException
in the execute method do this: throw new BuildException("failure in message check");
With the current .java per the patch, the error shows: C:\derbyt\svn\trunk\build.xml:480:

> Add MessageBundleTest to build script to verify that there are no orphaned message ids
> --------------------------------------------------------------------------------------
>                 Key: DERBY-1458
>                 URL: https://issues.apache.org/jira/browse/DERBY-1458
>             Project: Derby
>          Issue Type: Test
>          Components: Build tools
>    Affects Versions:
>            Reporter: David Van Couvering
>            Assignee: Myrna van Lunteren
>             Fix For:
>         Attachments: DERBY-1458.diff, DERBY-1458.diff2, DERBY-1458_3.diff, DERBY-1458_3.stat,
DERBY-1458_4_tmp.diff, MessageBundleTest.java, MessageBundleTest.java
> MessageBundleTest can't be run with the regular tests because it relies on SQLState.java
and MessageId.java, which are not in the jar files.  But it actually makes more sense to run
it as part of the build, as we are verifying the consistency of code references.  

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

View raw message