On Sat, 2002-04-13 at 08:50, Christian Willy Asmussen wrote:
> Dear mavens,
> I just started a new project using maven. For this project I needed torque
> (decoupled). So I added torque to my POM dependencies in project.xml. All
> worked fine, maven:update-jars fetched torque.jar just like I expected.
> Then I wrote a little testing task, like this:
>
> <available
> classpathref="classpath"
> property="torque.present"
> classname="org.apache.torque.Torque"
> />
>
> For my surprise, ${torque.present} was never set. I changed it to
> org.apache.torque.util.SqlEnum and then it worked. So I figured torque's
> jar was on my classpath. After running and with -debug option several
> times, I found out that Torque class could not be loaded because some of
> it's dependencies weren't present. So I copied most of the dependencies
> from torque's project.xml and then it worked.
>
> Question/Suggestion is:
> - Shouldn't Maven take care of this? The information needed is there and
> the process is always the same.
Maven will do this not in b4 but in b5. We're using the graph package in
the commons sandbox so that a project only has to state its direct
dependencies.
>
> tks,
> krico
> --
> There is no limit to what you can do
> if you don't care who gets the credit.
> - Keynote
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org
