Torque Maven Plugin got broken when transferring to maven

["Henning P. Schmiedehausen" <hp...@intermeta.de>]

Sigh.

Building the jakarta-turbine-2 HEAD scheduler sources:

% maven scheduler-om
[...]

Old result:

% ls target/src/org/apache/turbine/services/schedule/
BaseJobEntry.java  BaseJobEntryPeer.java  JobEntry.java  JobEntryPeer.java  map

And with the MAVEN HEAD from today:

% maven scheduler-om
[...]

% ls target/src/org/apache/turbine/services/schedule/
${basePrefix}JobEntry.java  $basePrefixJobEntryPeer.java  JobEntry.java  JobEntryPeer.java  map


Folks, it might annoy you, but _testing_ your stuff before checking in
would really be great.

This is the bug fix. Quinton, when we met at an ApacheCon or somewhere, 
you owe me a beer (because tracking this down took most of my morning) :-)

--- jakarta-turbine-maven/src/plugins-build/torque/plugin.jelly~        Thu Feb 27 11:59:13 2003
+++ jakarta-turbine-maven/src/plugins-build/torque/plugin.jelly Thu Feb 27 11:58:30 2003
@@ -40,7 +40,7 @@
 
          Note: I have no idea why this file is not already processed by the plugin..
       -->
-    <property file="${maven.home}/plugins/maven-torque-plugin-3.1-dev/plugin.properties"/>
+    <property file="${maven.home}/plugins/maven-torque-plugin-3.1/plugin.properties"/>
 
     <!-- Define all of the tasks -->
     <taskdef

	Regards
		Henning




-- 
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen          INTERMETA GmbH
hps@intermeta.de        +49 9131 50 654 0   http://www.intermeta.de/

Java, perl, Solaris, Linux, xSP Consulting, Web Services 
freelance consultant -- Jakarta Turbine Development  -- hero for hire