> -----Original Message-----
> From: Stephen Haberman [mailto:[EMAIL PROTECTED]] 
> Sent: Thursday, January 30, 2003 12:30 PM
> To: Turbine Developers List
> Subject: Re: Build process reverted
> 
> 
> On Wed, Jan 29, 2003 at 11:55:35AM -0600, Quinton McCombs wrote:
> > I still have not been able to pass the package name for the 
> generated 
> > scheduler OM objects to the torque plugin.
> 
> If I understand your problem correctly, this is done in Fulcrum by:
> 
> - set torque.schema.om.includes=turbine-schema.xml,
>   torque.targetPackage=${securityPackage}, call torque:om
> - set torque.schema.om.includes=scheduler-schema.xml,
>   torque.targetPackage="${schedulerPackage}, call torque:om
> 
> securityPackage and schedulerPackage are set in 
> project.properties, though they could very well be hardcoded here.
> 

I will get the latest copy of the fulcrum code to see if exactly how it
is being done now.  I actually copied the logic from Fulcrum's build
process.  What I found was that it did not work in either place.  

Fulcrum was building it correctly at one time.  However, when the torque
plugin was introduced, it stopped working properly.

You have the right part of maven.xml listed for where the problem
occurs.  What happens is the "set" is completely ignored.  The OM
objects are built in the org.apache.torque package.

> > To make matters worse, the torque plugin breaks xdoc generation.
> 
> Interesting...right now xdoc fails for me, but it's due to a 
> ClassNotFoundException for o.a.m.util.CaseInsensitiveGlobPattern,
> which I hope is just a bug from my snapshot of maven's CVS. 
> I'll update later today and see what happens.
> 

I have been using beta 7.  I have heard that the xdoc problem had been
fixed in the CVS version.  I have been hesitant to go with the CVS
version as I would rather not make that a requirement to build
Turbine....  I was hoping for a better solution.


> - Stephen
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to