Hi.
I'm working on a Maven Java Plugin & am running into an issue. I am directly
using the Dependency class in my code from the latest version of that jar,
3.0.1. However, the version in my Maven installation directory lib is 2.0.4
(same as the version of Maven I'm using) & the method available in
Dependency differ quite a bit between these versions. In pom.xml I have
3.0.1 as a dependency & it is in my local repository so the code compiles,
but once I execute my plugin, the mvn executable seems to look at the 2.0.4
jar in its lib directory instead of the configured 3.0.1 library, so I get a
runtime error that the method couldn't be found in the Dependency class. Any
suggestions on getting around this? As hacky as it sounds I even tried
copying the 3.0.1 jar to the Maven lib, renaming it to 2.0.4, but apparently
there are other differences that then causes Maven to choke completely. Any
help is much appreciated.
Thanks!

Actually, maven-model-3.0.1 has a different groupId I believe, and
belongs to Maven 1.x. You're probably looking for maven-model-2.0.4

15/09/2006, at 3:35 AM, fogwolf wrote:

Hi.

I'm working on a Maven Java Plugin & am running into an issue. I am
directly
using the Dependency class in my code from the latest version of
that jar,
3.0.1. However, the version in my Maven installation directory lib
is 2.0.4
(same as the version of Maven I'm using) & the method available in
Dependency differ quite a bit between these versions. In pom.xml I
have
3.0.1 as a dependency & it is in my local repository so the code
compiles,
but once I execute my plugin, the mvn executable seems to look at
the 2.0.4
jar in its lib directory instead of the configured 3.0.1 library,
so I get a
runtime error that the method couldn't be found in the Dependency
class. Any
suggestions on getting around this? As hacky as it sounds I even tried
copying the 3.0.1 jar to the Maven lib, renaming it to 2.0.4, but
apparently
there are other differences that then causes Maven to choke
completely. Any
help is much appreciated.

Thanks!

yep - you are right. thanks!

brettporter wrote:

Actually, maven-model-3.0.1 has a different groupId I believe, and
belongs to Maven 1.x. You're probably looking for maven-model-2.0.4

15/09/2006, at 3:35 AM, fogwolf wrote:

>>
>Hi.
>>
>I'm working on a Maven Java Plugin & am running into an issue. I am
>directly
>using the Dependency class in my code from the latest version of
>that jar,
>3.0.1. However, the version in my Maven installation directory lib
>is 2.0.4
>(same as the version of Maven I'm using) & the method available in
>Dependency differ quite a bit between these versions. In pom.xml I
>have
>3.0.1 as a dependency & it is in my local repository so the code
>compiles,
>but once I execute my plugin, the mvn executable seems to look at
>the 2.0.4
>jar in its lib directory instead of the configured 3.0.1 library,
>so I get a
>runtime error that the method couldn't be found in the Dependency
>class. Any
>suggestions on getting around this? As hacky as it sounds I even tried
>copying the 3.0.1 jar to the Maven lib, renaming it to 2.0.4, but
>apparently
>there are other differences that then causes Maven to choke
>completely. Any
>help is much appreciated.
>>
>Thanks!
>--
>View this message in context:
>#a6310953
>Sent from the Maven Developers forum at Nabble.com.
>>
>>
>
>To unsubscribe, e-mail: dev-unsubscribe (AT) maven (DOT) apache.org
>For additional commands, e-mail: dev-help (AT) maven (DOT) apache.org

To unsubscribe, e-mail: dev-unsubscribe (AT) maven (DOT) apache.org
For additional commands, e-mail: dev-help (AT) maven (DOT) apache.org