No, actually I have been trying to figure it out, here's the problem:

torque.zip contains everything I need (.vm files and a whole bunch of jars),
now I haven't downloaded the torque.jar to see what's in it, so I'm not sure
if it actually has the .vm files embedded.

If I want to use torque, then I need to include all of it's dependencies
plus check-in the lovely build file that you can now use with torque and
it's .vm files. Or I can check-in just the zip and extract it - which is
probably what I will have to do.

I think that a torque plug-in is the way of the future for this, so once you
have an architecture I will gladly create this one for turbine.

-warner

----- Original Message -----
From: <[EMAIL PROTECTED]>
To: "Turbine Maven Developers List" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Sunday, May 12, 2002 6:56 PM
Subject: Re: torque dependency question


>
> Warner,
>
> did I answer this before?
>
> If not, just list the jar as a dependency in the project.xml, and it will
> get auto-included into the war.
>
> --
> dIon Gillard, Multitask Consulting
> Work:      http://www.multitask.com.au
> Developers: http://adslgateway.multitask.com.au/developers
>
>
>
>                     "Warner Onstine"
>                     <sw-list@warneron       To:
<[EMAIL PROTECTED]>
>                     stine.com>              cc:
>                                             Subject:     torque dependency
question
>                     05/12/02 07:27 AM
>                     Please respond to
>                     "Turbine Maven
>                     Developers List"
>
>
>
>
>
>
> Hi all,
> I am creating a new Web app using Maven as the project management tool and
> have a question, what is the best way to list a torque dependency?
> Should I put in the zip dependency and then unzip the file into my
> directory?
> Or should I place the jar dependency and unzip everything and check it
into
> CVS as such?
> This strikes me as a perfect example of a maven plug-in (I love that
> idea!).
>
> -warner
>
> +warner onstine+
>
>
> --
> To unsubscribe, e-mail:   <
> mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <
> mailto:[EMAIL PROTECTED]>
>
>
>
>
>
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
>
>


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

Reply via email to