jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Maven 2 & 3
  • MNG-2448

Can not exclude a dependency from a plugin

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: 2.0.4
  • Fix Version/s: None
  • Component/s: Artifacts and Repositories
  • Labels:
    None
  • Complexity:
    Intermediate
  • Testcase included:
    yes

Description

I need to be able to exclude a dependency that a plugin included so I can replace it with a different dependency. In this exact case I'm attempting to use the com.sun.tools.xjc.maven2:maven-jaxb-plugin:1.0 plugin and it depends on the non-public jsr173 jar. I would like to exclude that jar so I can include public stax one. I know this will be fixed by implementing the spec resolution feature, but excluding bad dependencies from a plugin is a general problem.

The following snippit will demonstrate the download problem assuming you don't have the jsr173 jar available:

<plugin>
<groupId>com.sun.tools.xjc.maven2</groupId>
<artifactId>maven-jaxb-plugin</artifactId>
<version>1.0</version>
<executions>
<execution>
<goals>
<goal>generate</goal>
</goals>
</execution>
</executions>
<configuration>
<generatePackage>org.apache.xbean.jaxb.schema</generatePackage>
</configuration>
</configuration>
</plugin>

Issue Links

duplicates

New Feature - A new feature of the product, which has yet to be developed. MNG-2163 Allow plugin dependencies to be excluded

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Kenney Westerhof added a comment - 16/Jun/07 8:03 AM

Just redeclare the dependency as you normally do inside <plugin><dependencies>.
Since maven 2.0.5, (or possibly 2.0.6) that declaration will override the one from the plugin itself.

Show
Kenney Westerhof added a comment - 16/Jun/07 8:03 AM Just redeclare the dependency as you normally do inside <plugin><dependencies>. Since maven 2.0.5, (or possibly 2.0.6) that declaration will override the one from the plugin itself.
Hide
Permalink
Mark Hobson added a comment - 18/Jun/07 8:29 AM

Not sure this will work due to MNG-2972.

Show
Mark Hobson added a comment - 18/Jun/07 8:29 AM Not sure this will work due to MNG-2972.

People

  • Assignee:
    Unassigned
    Reporter:
    Dain Sundstrom
Vote (1)
Watch (3)

Dates

  • Created:
    14/Jul/06 11:50 AM
    Updated:
    17/Dec/08 10:06 PM
    Resolved:
    16/Jun/07 8:03 AM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.