You can submit a patch and if possible a test case.
I'll commit them as soon as possible.
Arnaud
> -Message d'origine-
> De : Eric Pugh [mailto:[EMAIL PROTECTED]
> Envoyé : jeudi 11 novembre 2004 12:20
> À : Maven Developers List
> Objet : RE: Ant plugin and
I think it would solve my issue. Do you mind if I take a stab at
implementing it?
> -Original Message-
> From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 11, 2004 10:30 AM
> To: 'Maven Developers List'
> Subject: RE: Ant plugin and m
; Envoyé : jeudi 11 novembre 2004 11:24
> À : Maven Developers List
> Objet : Re: Ant plugin and maven.jar.override
>
> I would think the correct behaviour is to simply honour the jar override
> whenever it is set, regardless of where it points (remember that they
> can be ve
I would think the correct behaviour is to simply honour the jar override
whenever it is set, regardless of where it points (remember that they
can be versions though, not necessarily a file!)
so add ${maven.jar.foo} to the classpath instead of getting it for
dependency foo if jar.override is on
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
