Gradle
  1. Gradle
  2. GRADLE-784

Provide a 'provided' configuration

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None

      Description

      The intent of 'provided' configuration is to define dependencies which are needed for compilation, but which should not be "exported" (aka should not show up in runtime configuration)

        Activity

        Hide
        Jayson Minard added a comment -

        @Yaneeve, probably because it doesn't have the support for IDE's to pick up provided/optional. propdeps has intellij and eclipse support which is critical for me.

        Show
        Jayson Minard added a comment - @Yaneeve, probably because it doesn't have the support for IDE's to pick up provided/optional. propdeps has intellij and eclipse support which is critical for me.
        Hide
        Ben Fortuna added a comment -

        To play devil's advocate for a moment, is it possibly better to limit the native scopes (I.e. not support provided, optional natively) due to the ambiguity in how people expect/want the scope to behave? I know with maven there has been much confusion over how it works.

        Show
        Ben Fortuna added a comment - To play devil's advocate for a moment, is it possibly better to limit the native scopes (I.e. not support provided, optional natively) due to the ambiguity in how people expect/want the scope to behave? I know with maven there has been much confusion over how it works.
        Hide
        Paul Michael Reilly added a comment -

        No. If there is a "provided" feature, then at least one has a fighting chance to solve problems that the lack of it creates. And, worse, there is a normal compilation provided scope but not a test compilation provided scope. I am simply after consistency so that Dex does for test builds what it does for product builds — not clutter the apk with class files that should not be there.

        Show
        Paul Michael Reilly added a comment - No. If there is a "provided" feature, then at least one has a fighting chance to solve problems that the lack of it creates. And, worse, there is a normal compilation provided scope but not a test compilation provided scope. I am simply after consistency so that Dex does for test builds what it does for product builds — not clutter the apk with class files that should not be there.
        Hide
        Rick-Rainer Ludwig added a comment -

        I am evaluating Gradle for usage as build system for JavaEE development with OSGi frontend. Unfortunately, the dependency scope provided is crucial for such projects, because a lot of dependencies are provided by the containers and are only needed during compile time. All the arguments for a provided scope are mentioned above and the vote counter is up to 207 (with me). What will happen to this issue? If it is not going to be implemented, is there a reasonable explanation?

        I agree also on the the comments above, that an 'optional' scope is not needed and is in Maven builds a 'bad smell'.

        Show
        Rick-Rainer Ludwig added a comment - I am evaluating Gradle for usage as build system for JavaEE development with OSGi frontend. Unfortunately, the dependency scope provided is crucial for such projects, because a lot of dependencies are provided by the containers and are only needed during compile time. All the arguments for a provided scope are mentioned above and the vote counter is up to 207 (with me). What will happen to this issue? If it is not going to be implemented, is there a reasonable explanation? I agree also on the the comments above, that an 'optional' scope is not needed and is in Maven builds a 'bad smell'.
        Hide
        Yaneeve Shekel added a comment -

        I would like to back up @Rick-Rainer Ludwig by saying that not only is it an issue with JEE + OSGI, we encounter likewise issues in the bigdata domain especially within the hadoop ecosystem. We use the nebula plugin, but it would have been better had it been supported out-of-the-box

        Show
        Yaneeve Shekel added a comment - I would like to back up @Rick-Rainer Ludwig by saying that not only is it an issue with JEE + OSGI, we encounter likewise issues in the bigdata domain especially within the hadoop ecosystem. We use the nebula plugin, but it would have been better had it been supported out-of-the-box

          People

          • Assignee:
            Unassigned
            Reporter:
            Steve Ebersole
          • Votes:
            212 Vote for this issue
            Watchers:
            156 Start watching this issue

            Dates

            • Created:
              Updated:

              Development