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)
  • jMock
  • JMOCK-121

jmock-junit* artifacts should list JUnit as normal dependency instead of as "provided" scope

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 2.1.0
  • Component/s: Maven Packaging
  • Labels:
    None

Description

One of the features of Maven is its ability to to provide transitive dependencies for a project that uses a particular library. The current jmock-junit* artifacts in the public Maven repository have a dependency on particular versions of JUnit, but list those dependencies with a scope of "provided", which means that any project that wants to use jmock-junit* will have to explicitly list JUnit as an additional dependency. A project shouldn't have to do this--if I say my project uses jmock-junit, Maven should be including JUnit automatically for me. If I want to override the particular version of JUnit that gets used, I can still do that.

Activity

  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Mauro Talevi added a comment - 22/May/07 2:43 AM

Done

Show
Mauro Talevi added a comment - 22/May/07 2:43 AM Done

People

  • Assignee:
    Mauro Talevi
    Reporter:
    David Jackman
Vote (0)
Watch (0)

Dates

  • Created:
    09/May/07 9:00 AM
    Updated:
    12/Jun/07 2:26 AM
    Resolved:
    22/May/07 2:43 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.