That's what I thought you may have done. If the dependency isn't listed in project.xml, then Maven stops there. The maven.jar.override property and its corresponding maven.jar.* properties only apply to dependencies listed in project.xml. The override is telling Maven to find the jar in a location different from the default (which would be the local repository).
-----Original Message----- From: Mayorgaadame, Alex [IT] [mailto:[EMAIL PROTECTED] Sent: Friday, August 26, 2005 3:59 PM To: Maven Users List Subject: RE: [m1] How to use Ant script instead of java:compile while creating the site Bear in mind that I'm totally new to Maven, in an effort to make the thing compile I removed all dependencies in project.xml and put everything in project.properties like this: maven.jar.override = on # Jars set explicitly by path. maven.jar.tools = $JAVA_HOME/lib/tools.jar maven.jar.activation-1.0.1 = ${basedir}/builder/lib/activation-1.0.1.jar ... Lots of jars here... Thanks David your help is extremely appreciated Alex -----Original Message----- From: David Jackman [mailto:[EMAIL PROTECTED] Sent: Friday, August 26, 2005 3:10 PM To: Maven Users List Subject: RE: [m1] How to use Ant script instead of java:compile while creating the site What does your project.xml and project.properties look like in regard to these dependencies? -----Original Message----- From: Mayorgaadame, Alex [IT] [mailto:[EMAIL PROTECTED] Sent: Friday, August 26, 2005 10:22 AM To: Maven Users List Subject: RE: [m1] How to use Ant script instead of java:compile while creating the site Thanks David By creating a custom goal named java:compile that run the Ant build it kind of works. I would like to move on to Mavenize this project even more. First thing I would like to be able to compile using the real java:compile goal, but every time I try to do that I get errors like this on every import on the code: container/src/java/com/.../.../.../ESFAxisConnector.java:4: package org.mule.umo does not exist import org.mule.umo.UMOComponent; I've already overridden all the jars in project.properties but it just don't catch the overrides. The thing is the current ant builder basically put every jar on the file tree in the classpath. Alex -----Original Message----- From: David Jackman [mailto:[EMAIL PROTECTED] Sent: Friday, August 26, 2005 11:50 AM To: Maven Users List Subject: RE: [m1] How to use Ant script instead of java:compile while creating the site This exact question (or very similar) was brought up about a month ago. You might find what you need by reading through that thread (there was a lot of discussion). You can find the initial message here: http://www.mail-archive.com/[email protected]/msg21037.html If this doesn't address your problem, ask again and we'll resume the discussion. ..David.. -----Original Message----- From: Mayorgaadame, Alex [IT] [mailto:[EMAIL PROTECTED] Sent: Friday, August 26, 2005 8:18 AM To: Maven Users List Subject: [m1] How to use Ant script instead of java:compile while creating the site I'm in the early stages of presenting Maven to a huge project that uses Ant. The first goal is to create the site for it. The site goal will always fail because the java compilation files given that the dependencies aren't set in project.xml I've created a custom goal to run the ant build.xml and it compiles perfectly. How can I make the site:site maven goal to use that custom goal instead of java:compile while creating the site and the documentation. Hope you can help me on this so the won't scrap the MAven thing altogether. Thank you Alex --------------------------------------------------------------------- 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] --------------------------------------------------------------------- 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] --------------------------------------------------------------------- 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]
