"Charles Tassoni" <[EMAIL PROTECTED]> wrote on 24/12/2003
08:04:24 AM:
> Thanks to Charles-Alexandre Sabourdin and dion for their advice.
> The suggestions didn't work for me. When I set
> <version>${pom.currentVersion}</version> on the jar I'm trying to build
on
> the fly, I got exactly the same result: maven simply resolved
> ${pom.currentVersion} to "1.0" and put the outdated 1.0 jar into the
> classpath while trying to build the new version of that jar.
> Same when I tried the other suggesion, using
<version>SNAPSHOTversion>,
> except that this time I had to change my jar in myProject/jars from
> theJar-1.0.jar to theJar-SNAPSHOT.jar. But "SNAPSHOT" did not act as a
> signal for maven to avoid putting the jar in the classpath.
> I understand that this problem does not occur every time someone
builds.
> Most times, if you put an old version of theJar.jar while trying to
> compile classes for an new version of theJar.jar, you won't get a
compile
> error. But try moving one of your classes into a different package and
> you'll see that having the old version of the jar causes compile errors
when
> you try to rebuild the jar.
> So, anyone know how to tell maven "Don't use this jar in the
classpath"
> when compiling?
Why do you not want the jar in the dependencies?
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
