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] Updated: (DERBY-1458) Add MessageBundleTest to build script to verify that there are no orphaned message ids
Date Fri, 17 Oct 2008 17:24:44 GMT

     [ https://issues.apache.org/jira/browse/DERBY-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Myrna van Lunteren updated DERBY-1458:

    Attachment: DERBY-1458_4_tmp.diff

I'm attaching an attempt to implement a taskdef, similar to what was done for PropertySetter,
but I'm stumped - I get a failure out of the call to the taskdef (regardless of whether or
not I make the check hit some failures).

The output I get is this (with verbose):

C:\derbyt\svn\trunk\build.xml:480: failure in message check
	at org.apache.derbyBuild.MessageBundleTest.execute(Unknown Source)
	at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
	at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
	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:1329)
	at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
	at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
	at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
	at org.apache.tools.ant.Main.runBuild(Main.java:698)
	at org.apache.tools.ant.Main.startAnt(Main.java:199)
	at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
	at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)

Is there anyone familiar with this technique that can spot where I went wrong?

> 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