You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Nicolas De Loof <ni...@capgemini.com> on 2006/09/07 09:12:08 UTC
override dependency used by a plugin
Hello,
I'd like to use the jibx plugin (jibx.sourceforge.net)
This maven2 plugin declares dependencies to jibx 1.0-RC1. I'd like to
override this to use jibx 1.1 on plugin execution.
I've added a <dependencies> element in my plugin configuration, to
override jibx-run and jibx-bind to 1.1, but I always get this dependency
resolution :
[DEBUG] Using defaults for missing POM org.jibx:jibx-bind:pom:1.1:runtime
[DEBUG] org.jibx:jibx-bind:jar:1.1:runtime (selected for runtime)
[DEBUG] xpp3:xpp3:jar:1.1.3.3:runtime (selected for runtime)
[DEBUG] org.jibx:jibx-run:jar:1.0-RC1:runtime (selected for runtime)
[DEBUG] org.apache.maven:maven-project:jar:2.0:runtime (selected for
runtime)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (selected
for runtime)
[DEBUG]
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8:runtime
(selected for runtime)
[DEBUG] classworlds:classworlds:jar:1.1-alpha-2:runtime (selected
for runtime)
[DEBUG] junit:junit:jar:3.8.1:runtime (selected for runtime)
[DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected
for runtime)
[DEBUG] org.apache.maven:maven-model:jar:2.0:runtime (selected for
runtime)
[DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0:runtime
(selected for runtime)
[DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0:runtime
(selected for runtime)
[DEBUG]
org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5:runtime
(selected for runtime)
[DEBUG] org.apache.maven:maven-profile:jar:2.0:runtime (selected for
runtime)
[DEBUG] org.jibx:jibx-bind:jar:1.0-RC1:runtime (removed - nearer
found: 1.1)
[DEBUG] bcel:bcel:jar:5.1:runtime (selected for runtime)
[DEBUG] org.jibx:jibx-run:jar:1.1:runtime (removed - nearer found:
1.0-RC1)
[DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected
for runtime)
[DEBUG] commons-io:commons-io:jar:1.1:runtime (selected for runtime)
[DEBUG] Configuring mojo 'org.jibx:maven-jibx-plugin:1.1:bind' -->
Those trace shows that jibx-bind:1.1 is used as expected, but not
jibx-run, as "removed - nearer found: 1.0-RC1".
What exactly means "nearer" ? How to configure a hard dependency to 1.1
that will not be removed ?
Nico.
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: override dependency used by a plugin
Posted by Max Bowsher <ma...@mxtelecom.com>.
Nicolas De Loof wrote:
>
> Hello,
>
> I'd like to use the jibx plugin (jibx.sourceforge.net)
> This maven2 plugin declares dependencies to jibx 1.0-RC1. I'd like to
> override this to use jibx 1.1 on plugin execution.
>
> I've added a <dependencies> element in my plugin configuration, to
> override jibx-run and jibx-bind to 1.1, but I always get this dependency
> resolution :
>
> [DEBUG] Using defaults for missing POM org.jibx:jibx-bind:pom:1.1:runtime
> [DEBUG] org.jibx:jibx-bind:jar:1.1:runtime (selected for runtime)
> [DEBUG] xpp3:xpp3:jar:1.1.3.3:runtime (selected for runtime)
> [DEBUG] org.jibx:jibx-run:jar:1.0-RC1:runtime (selected for runtime)
> [DEBUG] org.apache.maven:maven-project:jar:2.0:runtime (selected for
> runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (selected
> for runtime)
> [DEBUG]
> org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8:runtime
> (selected for runtime)
> [DEBUG] classworlds:classworlds:jar:1.1-alpha-2:runtime (selected
> for runtime)
> [DEBUG] junit:junit:jar:3.8.1:runtime (selected for runtime)
> [DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected
> for runtime)
> [DEBUG] org.apache.maven:maven-model:jar:2.0:runtime (selected for
> runtime)
> [DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0:runtime
> (selected for runtime)
> [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0:runtime
> (selected for runtime)
> [DEBUG]
> org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5:runtime
> (selected for runtime)
> [DEBUG] org.apache.maven:maven-profile:jar:2.0:runtime (selected for
> runtime)
> [DEBUG] org.jibx:jibx-bind:jar:1.0-RC1:runtime (removed - nearer
> found: 1.1)
> [DEBUG] bcel:bcel:jar:5.1:runtime (selected for runtime)
> [DEBUG] org.jibx:jibx-run:jar:1.1:runtime (removed - nearer found:
> 1.0-RC1)
> [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected
> for runtime)
> [DEBUG] commons-io:commons-io:jar:1.1:runtime (selected for runtime)
> [DEBUG] Configuring mojo 'org.jibx:maven-jibx-plugin:1.1:bind' -->
>
>
> Those trace shows that jibx-bind:1.1 is used as expected, but not
> jibx-run, as "removed - nearer found: 1.0-RC1".
> What exactly means "nearer" ? How to configure a hard dependency to 1.1
> that will not be removed ?
I have exactly the same problem, except with maven-jar-plugin and
maven-archiver.
The following sentence from section 3.6, page 58 of "Better Builds with
Maven" makes me worry that this is impossible:
"If multiple versions are selected at the same depth, then the result is
undefined."
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org