so add ${maven.jar.foo} to the classpath instead of getting it for dependency foo if jar.override is on and jar.foo is not numerical.
Cheers, Brett
Eric Pugh wrote:
Hi all, I am working on generating an Ant file for a project that is using the maven.jar.override option. We have a /lib/ directory where we have placed some javamail.jar and activation.jar so that users dont' have to manually install them.
However, when I run 'maven ant', the generated build.xml still tries to download these dependencies from the remote repo. I am thinking about modifying the Ant plugin so that if a dependency is located within the project (relative to basedir) then we don't try and download it, but just add it to the classpath from wherever it is.
However, if a dependency was specified as being in the local repo under a different version or a completely different location, then the ant script would work the same.
Is this a good idea? I think that the "contained somewhere below the ${basedir}" check on a jar implies that whoever is using the Ant build would have checked out the project and have the jar on their local filesystem, correct?
Eric Pugh
--------------------------------------------------------------------- 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]
