You can view the issue detail at the following URL:
<http://nagoya.apache.org/scarab/issues/id/TRQS66>
Type : Defect
Issue Id : TRQS66
Reported by: James Courtney
[EMAIL PROTECTED] - ([EMAIL PROTECTED])
Details:
Summary: Torque maven-plugin uses classpath generated by project.xml.
Description: The Torque maven plugin is packaged with a project.xml file which
includes a list of dependencies. For some reason when torque.useClasspath is set to
false the classpath searched for the templates is the one constructed from this list
of dependencies. Since this dependency list specifies the same version of Torque as
the plugin being used this binds the plugin to the same full version of torque. Thus
you can't use the RC2 plugin with the RC1 release since you won't have the RC2 release
in the classpath Velocity searches for the templates as part of the om target. This
may be by design but it seems an unnecessary constraint. I would think that having
velocity search the project classpath for the user's maven project rather than the
embedded classpath for the torque plugin would make more sense.
Status: New
Database: Oracle
Operating system: Windows
Priority: Medium
--
To unsubscribe, e-mail: <mailto:turbine-torque-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:turbine-torque-dev-help@;jakarta.apache.org>
