Gradle
  1. Gradle
  2. GRADLE-1706

Gradle eclipse/idea plugin breaks when dependency sources jar is not found occasionally

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Resolution: Fixed
    • Affects Version/s: 1.0-milestone-4
    • Fix Version/s: 1.0-milestone-5

      Description

      In my multi-module project, the eclipse plugin has been applied to all the module, and eclipse.classpath.downloadSources = true, when run gradle eclipse command, there are several artifacts that missing source jars in the Maven repo, then gradle keep downloading something from the repo for every module. Should add some flag to make it ignore if the source jar is missing from the repo.

        Activity

        Hide
        Joern Huxhorn added a comment -

        Same for eclipse plugin.

        Show
        Joern Huxhorn added a comment - Same for eclipse plugin.
        Hide
        Szczepan Faber added a comment -

        This bug is fixed in master, but not in milestone-4 (see the fix version/s information).

        Please let me know if you are still facing this error using latest master (or one of younger milestone-5 snapshot releases).

        Hope that helps!

        Show
        Szczepan Faber added a comment - This bug is fixed in master, but not in milestone-4 (see the fix version/s information). Please let me know if you are still facing this error using latest master (or one of younger milestone-5 snapshot releases). Hope that helps!
        Hide
        Szczepan Faber added a comment -

        It is related GRADLE-1736. With the latest master/next gradle version the build will not break when idea cannot find sources. There might be an ivy warning printed instead but the idea metadata will be created and one can start developing using IDEA.

        I'm closing this issue to avoid confusion about: is it fixed or not. If the ivy warning bothers someone please submit a separate ticket Unfortunately, the ivy warning is hard to surpress.

        Show
        Szczepan Faber added a comment - It is related GRADLE-1736 . With the latest master/next gradle version the build will not break when idea cannot find sources. There might be an ivy warning printed instead but the idea metadata will be created and one can start developing using IDEA. I'm closing this issue to avoid confusion about: is it fixed or not. If the ivy warning bothers someone please submit a separate ticket Unfortunately, the ivy warning is hard to surpress.
        Hide
        Szczepan Faber added a comment -

        Workaround for versions < milestone-5

        ideaModule.downloadSources = false
        
        //or for all projects:
        allprojects {
          ideaModule.downloadSources = false
        }
        
        Show
        Szczepan Faber added a comment - Workaround for versions < milestone-5 ideaModule.downloadSources = false //or for all projects: allprojects { ideaModule.downloadSources = false }
        Hide
        Joern Huxhorn added a comment -

        I can confirm that this is working with 1.0-milestone-5-20111008000006+0200.

        Thanks for the infos!

        Show
        Joern Huxhorn added a comment - I can confirm that this is working with 1.0-milestone-5-20111008000006+0200. Thanks for the infos!

          People

          • Assignee:
            Szczepan Faber
            Reporter:
            Wang Liyu
          • Votes:
            3 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development