JBehave
  1. JBehave
  2. JBEHAVE-960

Support for provided-scope dependencies

    Details

    • Type: New Feature New Feature
    • Status: Resolved Resolved
    • Priority: Major Major
    • Resolution: Duplicate
    • Affects Version/s: 3.7.4
    • Fix Version/s: 3.8
    • Component/s: Maven Plugin
    • Labels:
      None
    • Number of attachments :
      0

      Description

      As per discussion http://comments.gmane.org/gmane.comp.java.jbehave.user/1342, JBehave maven plugin never uses provided-scope dependencies. This is a pain for us as we package all libraries in separate modules, so they're always in provided scope. Having all of them explicitly changed to compile scope is way too much work.

      According to the conversation in the thread, the plugin uses requiresDependencyResolution which has scope runtime by default, excluding provided scope. According to MojoApiSpecification (http://maven.apache.org/developers/mojo-api-specification.html) it's just a matter of changing it to for example compile+runtime to have dependencies from other scopes as well.

        Activity

        Hide
        Jarkko Rantavuori added a comment -

        Ok, it seems version 3.8 of the plugin already has this covered and provided-scope dependencies work. Sorry for the trouble.

        Show
        Jarkko Rantavuori added a comment - Ok, it seems version 3.8 of the plugin already has this covered and provided-scope dependencies work. Sorry for the trouble.
        Jarkko Rantavuori made changes -
        Field Original Value New Value
        Status Open [ 1 ] Resolved [ 5 ]
        Fix Version/s 3.8 [ 19104 ]
        Resolution Duplicate [ 3 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            Jarkko Rantavuori
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: