First of all: thanks for the immediate response...
The problems with the classpath configuration I ran into where caused by
torque-b3. I integrated it as a maven plugin. Everything worked fine
until it came to compiling the OM classes.
No clue why - is this a torque bug? Hard to believe because the other
torque targets function perfectly. For my purposes the OM compilation
problem is a minor one, only need it for database creation ("create-db",
"sql", "insert-sql"). "maven:jar" doesn't complain with other
jars/packages - didn't see it in my late-night-red-eyes-paranoia, sorry
for the inconvenience.
Oh, in fact there is one thing that I changed: I enabled
"inheritall=true" for the maven delegators in my build.xml file... does
that matter?
Is there a need for a torque plugin? I saw some messages about it in the
mail archive, but it was not clear to me if anybody is working on
that... if not I would like to contribute my stuff...
Jason van Zyl wrote:
> On Mon, 2002-07-29 at 19:14, Aleksandar Vidakovic wrote:
>
>>Hi all,
>>
>>I am trying to compile my mavenized projects, but maven seems to ignore
>>my project dependent jars. How do I tell maven to include my jars in the
>> classpath??? Thanks in advance for ending my frustration!!
>
>
> Anything you list as a dependency will be included in the classpath. You
> don't have to tell maven, it will just include them. What do your
> <dependencies/> look like in your project.xml file?
>
>
>
>>Aleks
>>
>>
>>--
>>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]>
