Agile BoardAttach filesAttach ScreenshotAdd voteVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • Trunk, Upcoming Branch
    • None
    • Gradle
    • None
    • Bug Crush Event - 21/2/2015

    Description

      I posted a related message in dev ML: https://markmail.org/message/55r5ycn2wrbotnbn:

      Hi,

      I just read a members thread about this article: https://medium.com/@alex.birsan/dependency-confusion-4a5d60fec610

      One member mentioned that the Groovy project is using the Gradle's dependency verification feature[1] in the Apache Groovy build.

      I suggest we do the same, even after the move from JCenter to MavenCentral where things should be safer.

      What do you think?

      [1] https://docs.gradle.org/current/userguide/dependency_verification.html

      Jacques

      Note that dependency verification is an incubating feature. So we will wait before backporting from trunk...

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            jleroux Jacques Le Roux

            Dates

              Created:
              Updated:

              Agile

                Completed Sprint:
                Bug Crush Event - 21/2/2015 ended 26/Feb/15
                View on Board

                Slack

                  Issue deployment