You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Derek Alexander (JIRA)" <ji...@codehaus.org> on 2007/05/02 00:57:26 UTC

[jira] Created: (MNG-2972) Ignores version of plugin dependency specified in my pom

Ignores version of plugin dependency specified in my pom
--------------------------------------------------------

                 Key: MNG-2972
                 URL: http://jira.codehaus.org/browse/MNG-2972
             Project: Maven 2
          Issue Type: Bug
          Components: Dependencies
    Affects Versions: 2.0.6
         Environment: maven 2.0.6, java version "1.5.0_07"
            Reporter: Derek Alexander
            Priority: Critical


xmlbeans-maven-plugin declares a dependency on xmlbeans-2.0.0

I want to use xmlbeans-2.2.0

So in my pom I put:

      <plugin>
        <groupId>org.codehaus.mojo</groupId>
        <artifactId>xmlbeans-maven-plugin</artifactId>
        <executions>
           <execution>
              <goals>
                 <goal>xmlbeans</goal>
              </goals>
           </execution>
        </executions>
        <configuration>
		...
        </configuration>
	  <dependencies>
	    <dependency>
	      <groupId>xmlbeans</groupId>
	      <artifactId>xbean</artifactId>
	      <version>2.2.0</version>
	    </dependency>
	  </dependencies>
      </plugin

But it still downloads 2.0.0. (as well as 2.2.0). Haven't got a clue which it is using as it doesn't seem to output stuff like that. Couldn't see a verbose or debug switch mentioned in the docs. Anyway I think it is still using 2.0.0.

Seems like I'm not the first to experience this:
http://www.nabble.com/Override-plugin-dependency-version-tf2357806s177.html#a6568092

Apparently this should be possible: http://maven.apache.org/pom.html#plugins

"dependencies: Dependencies are seen a lot within the POM, and are an element under all plugins element blocks. The dependencies have the same structure and function as under that base build. The major difference in this case is that instead of applying as dependencies of the project, they now apply as dependencies of the plugin that they are under. The power of this is to alter the dependency list of a plugin, perhaps by removing an unused runtime dependency via exclusions, or by altering the version of a required dpendency. See above under Dependencies for more information."

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Work started: (MNG-2972) Ignores version of plugin dependency specified in my pom

Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on MNG-2972 started by Brian Fox.

> Ignores version of plugin dependency specified in my pom
> --------------------------------------------------------
>
>                 Key: MNG-2972
>                 URL: http://jira.codehaus.org/browse/MNG-2972
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 2.0.6
>         Environment: maven 2.0.6, java version "1.5.0_07"
>            Reporter: Derek Alexander
>            Assignee: Brian Fox
>            Priority: Critical
>             Fix For: 2.0.9
>
>
> xmlbeans-maven-plugin declares a dependency on xmlbeans-2.0.0
> I want to use xmlbeans-2.2.0
> So in my pom I put:
>       <plugin>
>         <groupId>org.codehaus.mojo</groupId>
>         <artifactId>xmlbeans-maven-plugin</artifactId>
>         <executions>
>            <execution>
>               <goals>
>                  <goal>xmlbeans</goal>
>               </goals>
>            </execution>
>         </executions>
>         <configuration>
> 		...
>         </configuration>
> 	  <dependencies>
> 	    <dependency>
> 	      <groupId>xmlbeans</groupId>
> 	      <artifactId>xbean</artifactId>
> 	      <version>2.2.0</version>
> 	    </dependency>
> 	  </dependencies>
>       </plugin
> But it still downloads 2.0.0. (as well as 2.2.0). Haven't got a clue which it is using as it doesn't seem to output stuff like that. Couldn't see a verbose or debug switch mentioned in the docs. Anyway I think it is still using 2.0.0.
> Seems like I'm not the first to experience this:
> http://www.nabble.com/Override-plugin-dependency-version-tf2357806s177.html#a6568092
> Apparently this should be possible: http://maven.apache.org/pom.html#plugins
> "dependencies: Dependencies are seen a lot within the POM, and are an element under all plugins element blocks. The dependencies have the same structure and function as under that base build. The major difference in this case is that instead of applying as dependencies of the project, they now apply as dependencies of the plugin that they are under. The power of this is to alter the dependency list of a plugin, perhaps by removing an unused runtime dependency via exclusions, or by altering the version of a required dpendency. See above under Dependencies for more information."

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Closed: (MNG-2972) Ignores version of plugin dependency specified in my pom

Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Fox closed MNG-2972.
--------------------------

    Resolution: Fixed

This is confirmed fixed in 2.0.9, an additional IT was created to be sure.

> Ignores version of plugin dependency specified in my pom
> --------------------------------------------------------
>
>                 Key: MNG-2972
>                 URL: http://jira.codehaus.org/browse/MNG-2972
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 2.0.6
>         Environment: maven 2.0.6, java version "1.5.0_07"
>            Reporter: Derek Alexander
>            Assignee: Brian Fox
>            Priority: Critical
>             Fix For: 2.0.9
>
>
> xmlbeans-maven-plugin declares a dependency on xmlbeans-2.0.0
> I want to use xmlbeans-2.2.0
> So in my pom I put:
>       <plugin>
>         <groupId>org.codehaus.mojo</groupId>
>         <artifactId>xmlbeans-maven-plugin</artifactId>
>         <executions>
>            <execution>
>               <goals>
>                  <goal>xmlbeans</goal>
>               </goals>
>            </execution>
>         </executions>
>         <configuration>
> 		...
>         </configuration>
> 	  <dependencies>
> 	    <dependency>
> 	      <groupId>xmlbeans</groupId>
> 	      <artifactId>xbean</artifactId>
> 	      <version>2.2.0</version>
> 	    </dependency>
> 	  </dependencies>
>       </plugin
> But it still downloads 2.0.0. (as well as 2.2.0). Haven't got a clue which it is using as it doesn't seem to output stuff like that. Couldn't see a verbose or debug switch mentioned in the docs. Anyway I think it is still using 2.0.0.
> Seems like I'm not the first to experience this:
> http://www.nabble.com/Override-plugin-dependency-version-tf2357806s177.html#a6568092
> Apparently this should be possible: http://maven.apache.org/pom.html#plugins
> "dependencies: Dependencies are seen a lot within the POM, and are an element under all plugins element blocks. The dependencies have the same structure and function as under that base build. The major difference in this case is that instead of applying as dependencies of the project, they now apply as dependencies of the plugin that they are under. The power of this is to alter the dependency list of a plugin, perhaps by removing an unused runtime dependency via exclusions, or by altering the version of a required dpendency. See above under Dependencies for more information."

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Reopened: (MNG-2972) Ignores version of plugin dependency specified in my pom

Posted by "Derek Alexander (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Derek Alexander reopened MNG-2972:
----------------------------------


> You actually specify the dependencies inside the plugin element.

Yes, that's what I was doing.

OK to just reopen this issue I hope.

> Ignores version of plugin dependency specified in my pom
> --------------------------------------------------------
>
>                 Key: MNG-2972
>                 URL: http://jira.codehaus.org/browse/MNG-2972
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 2.0.6
>         Environment: maven 2.0.6, java version "1.5.0_07"
>            Reporter: Derek Alexander
>            Priority: Critical
>             Fix For: Reviewed Pending Version Assignment
>
>
> xmlbeans-maven-plugin declares a dependency on xmlbeans-2.0.0
> I want to use xmlbeans-2.2.0
> So in my pom I put:
>       <plugin>
>         <groupId>org.codehaus.mojo</groupId>
>         <artifactId>xmlbeans-maven-plugin</artifactId>
>         <executions>
>            <execution>
>               <goals>
>                  <goal>xmlbeans</goal>
>               </goals>
>            </execution>
>         </executions>
>         <configuration>
> 		...
>         </configuration>
> 	  <dependencies>
> 	    <dependency>
> 	      <groupId>xmlbeans</groupId>
> 	      <artifactId>xbean</artifactId>
> 	      <version>2.2.0</version>
> 	    </dependency>
> 	  </dependencies>
>       </plugin
> But it still downloads 2.0.0. (as well as 2.2.0). Haven't got a clue which it is using as it doesn't seem to output stuff like that. Couldn't see a verbose or debug switch mentioned in the docs. Anyway I think it is still using 2.0.0.
> Seems like I'm not the first to experience this:
> http://www.nabble.com/Override-plugin-dependency-version-tf2357806s177.html#a6568092
> Apparently this should be possible: http://maven.apache.org/pom.html#plugins
> "dependencies: Dependencies are seen a lot within the POM, and are an element under all plugins element blocks. The dependencies have the same structure and function as under that base build. The major difference in this case is that instead of applying as dependencies of the project, they now apply as dependencies of the plugin that they are under. The power of this is to alter the dependency list of a plugin, perhaps by removing an unused runtime dependency via exclusions, or by altering the version of a required dpendency. See above under Dependencies for more information."

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Closed: (MNG-2972) Ignores version of plugin dependency specified in my pom

Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason van Zyl closed MNG-2972.
------------------------------

    Resolution: Won't Fix

This is not how plugin dependencies work. You actually specify the dependencies inside the plugin element. Try this and if that doesn't work then it's a bug and open a new issue.

> Ignores version of plugin dependency specified in my pom
> --------------------------------------------------------
>
>                 Key: MNG-2972
>                 URL: http://jira.codehaus.org/browse/MNG-2972
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 2.0.6
>         Environment: maven 2.0.6, java version "1.5.0_07"
>            Reporter: Derek Alexander
>            Priority: Critical
>             Fix For: Reviewed Pending Version Assignment
>
>
> xmlbeans-maven-plugin declares a dependency on xmlbeans-2.0.0
> I want to use xmlbeans-2.2.0
> So in my pom I put:
>       <plugin>
>         <groupId>org.codehaus.mojo</groupId>
>         <artifactId>xmlbeans-maven-plugin</artifactId>
>         <executions>
>            <execution>
>               <goals>
>                  <goal>xmlbeans</goal>
>               </goals>
>            </execution>
>         </executions>
>         <configuration>
> 		...
>         </configuration>
> 	  <dependencies>
> 	    <dependency>
> 	      <groupId>xmlbeans</groupId>
> 	      <artifactId>xbean</artifactId>
> 	      <version>2.2.0</version>
> 	    </dependency>
> 	  </dependencies>
>       </plugin
> But it still downloads 2.0.0. (as well as 2.2.0). Haven't got a clue which it is using as it doesn't seem to output stuff like that. Couldn't see a verbose or debug switch mentioned in the docs. Anyway I think it is still using 2.0.0.
> Seems like I'm not the first to experience this:
> http://www.nabble.com/Override-plugin-dependency-version-tf2357806s177.html#a6568092
> Apparently this should be possible: http://maven.apache.org/pom.html#plugins
> "dependencies: Dependencies are seen a lot within the POM, and are an element under all plugins element blocks. The dependencies have the same structure and function as under that base build. The major difference in this case is that instead of applying as dependencies of the project, they now apply as dependencies of the plugin that they are under. The power of this is to alter the dependency list of a plugin, perhaps by removing an unused runtime dependency via exclusions, or by altering the version of a required dpendency. See above under Dependencies for more information."

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (MNG-2972) Ignores version of plugin dependency specified in my pom

Posted by "Mark Hobson (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99846 ] 

Mark Hobson commented on MNG-2972:
----------------------------------

The POM snippet above does specify the dependencies block within the plugin element.  I've encountered this problem before myself, so would have thought this should be reopened.

> Ignores version of plugin dependency specified in my pom
> --------------------------------------------------------
>
>                 Key: MNG-2972
>                 URL: http://jira.codehaus.org/browse/MNG-2972
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 2.0.6
>         Environment: maven 2.0.6, java version "1.5.0_07"
>            Reporter: Derek Alexander
>            Priority: Critical
>             Fix For: Reviewed Pending Version Assignment
>
>
> xmlbeans-maven-plugin declares a dependency on xmlbeans-2.0.0
> I want to use xmlbeans-2.2.0
> So in my pom I put:
>       <plugin>
>         <groupId>org.codehaus.mojo</groupId>
>         <artifactId>xmlbeans-maven-plugin</artifactId>
>         <executions>
>            <execution>
>               <goals>
>                  <goal>xmlbeans</goal>
>               </goals>
>            </execution>
>         </executions>
>         <configuration>
> 		...
>         </configuration>
> 	  <dependencies>
> 	    <dependency>
> 	      <groupId>xmlbeans</groupId>
> 	      <artifactId>xbean</artifactId>
> 	      <version>2.2.0</version>
> 	    </dependency>
> 	  </dependencies>
>       </plugin
> But it still downloads 2.0.0. (as well as 2.2.0). Haven't got a clue which it is using as it doesn't seem to output stuff like that. Couldn't see a verbose or debug switch mentioned in the docs. Anyway I think it is still using 2.0.0.
> Seems like I'm not the first to experience this:
> http://www.nabble.com/Override-plugin-dependency-version-tf2357806s177.html#a6568092
> Apparently this should be possible: http://maven.apache.org/pom.html#plugins
> "dependencies: Dependencies are seen a lot within the POM, and are an element under all plugins element blocks. The dependencies have the same structure and function as under that base build. The major difference in this case is that instead of applying as dependencies of the project, they now apply as dependencies of the plugin that they are under. The power of this is to alter the dependency list of a plugin, perhaps by removing an unused runtime dependency via exclusions, or by altering the version of a required dpendency. See above under Dependencies for more information."

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (MNG-2972) Ignores version of plugin dependency specified in my pom

Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Fox updated MNG-2972:
---------------------------

    Fix Version/s:     (was: Reviewed Pending Version Assignment)
                   2.0.9

I think this was fixed already. Check in 2.0.9

> Ignores version of plugin dependency specified in my pom
> --------------------------------------------------------
>
>                 Key: MNG-2972
>                 URL: http://jira.codehaus.org/browse/MNG-2972
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 2.0.6
>         Environment: maven 2.0.6, java version "1.5.0_07"
>            Reporter: Derek Alexander
>            Priority: Critical
>             Fix For: 2.0.9
>
>
> xmlbeans-maven-plugin declares a dependency on xmlbeans-2.0.0
> I want to use xmlbeans-2.2.0
> So in my pom I put:
>       <plugin>
>         <groupId>org.codehaus.mojo</groupId>
>         <artifactId>xmlbeans-maven-plugin</artifactId>
>         <executions>
>            <execution>
>               <goals>
>                  <goal>xmlbeans</goal>
>               </goals>
>            </execution>
>         </executions>
>         <configuration>
> 		...
>         </configuration>
> 	  <dependencies>
> 	    <dependency>
> 	      <groupId>xmlbeans</groupId>
> 	      <artifactId>xbean</artifactId>
> 	      <version>2.2.0</version>
> 	    </dependency>
> 	  </dependencies>
>       </plugin
> But it still downloads 2.0.0. (as well as 2.2.0). Haven't got a clue which it is using as it doesn't seem to output stuff like that. Couldn't see a verbose or debug switch mentioned in the docs. Anyway I think it is still using 2.0.0.
> Seems like I'm not the first to experience this:
> http://www.nabble.com/Override-plugin-dependency-version-tf2357806s177.html#a6568092
> Apparently this should be possible: http://maven.apache.org/pom.html#plugins
> "dependencies: Dependencies are seen a lot within the POM, and are an element under all plugins element blocks. The dependencies have the same structure and function as under that base build. The major difference in this case is that instead of applying as dependencies of the project, they now apply as dependencies of the plugin that they are under. The power of this is to alter the dependency list of a plugin, perhaps by removing an unused runtime dependency via exclusions, or by altering the version of a required dpendency. See above under Dependencies for more information."

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (MNG-2972) Ignores version of plugin dependency specified in my pom

Posted by "Brad Szabo (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97137 ] 

Brad Szabo commented on MNG-2972:
---------------------------------

I also ran into this issue a couple months back. See my post on the Users list http://www.nabble.com/-Maven2--xmlbeans-maven-plugin-Issue----StAX-transitive-dependencies-t3359711s177.html

One issue that I discovered which is related to the overriding behavior in question is that if I added a few more dependencies to the POM, all of a sudden the dependency version that I specified in my plugin declaration DID successfully override the plugin version. 
I could consistently get the plugin override to work after adding 5 or 6 more seemingly random jars to my dependency list. 


> Ignores version of plugin dependency specified in my pom
> --------------------------------------------------------
>
>                 Key: MNG-2972
>                 URL: http://jira.codehaus.org/browse/MNG-2972
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 2.0.6
>         Environment: maven 2.0.6, java version "1.5.0_07"
>            Reporter: Derek Alexander
>            Priority: Critical
>
> xmlbeans-maven-plugin declares a dependency on xmlbeans-2.0.0
> I want to use xmlbeans-2.2.0
> So in my pom I put:
>       <plugin>
>         <groupId>org.codehaus.mojo</groupId>
>         <artifactId>xmlbeans-maven-plugin</artifactId>
>         <executions>
>            <execution>
>               <goals>
>                  <goal>xmlbeans</goal>
>               </goals>
>            </execution>
>         </executions>
>         <configuration>
> 		...
>         </configuration>
> 	  <dependencies>
> 	    <dependency>
> 	      <groupId>xmlbeans</groupId>
> 	      <artifactId>xbean</artifactId>
> 	      <version>2.2.0</version>
> 	    </dependency>
> 	  </dependencies>
>       </plugin
> But it still downloads 2.0.0. (as well as 2.2.0). Haven't got a clue which it is using as it doesn't seem to output stuff like that. Couldn't see a verbose or debug switch mentioned in the docs. Anyway I think it is still using 2.0.0.
> Seems like I'm not the first to experience this:
> http://www.nabble.com/Override-plugin-dependency-version-tf2357806s177.html#a6568092
> Apparently this should be possible: http://maven.apache.org/pom.html#plugins
> "dependencies: Dependencies are seen a lot within the POM, and are an element under all plugins element blocks. The dependencies have the same structure and function as under that base build. The major difference in this case is that instead of applying as dependencies of the project, they now apply as dependencies of the plugin that they are under. The power of this is to alter the dependency list of a plugin, perhaps by removing an unused runtime dependency via exclusions, or by altering the version of a required dpendency. See above under Dependencies for more information."

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira