Grails
  1. Grails
  2. GRAILS-6359

Grails attempts to download "source" and "javadoc" dependencies

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 1.3.2
    • Fix Version/s: 2.3-M1
    • Component/s: None
    • Labels:
      None

      Description

      When I add a dependency via the dependency DSL, Grails tries to get hold of the "source" and "javadoc" JARs too for some reason. Here's part of the output:

      :: problems summary ::
      :::: WARNINGS
      		[FAILED     ] net.sf.dozer#dozer;5.1!dozer.jar(source):  (0ms)
      
      	==== grailsPlugins: tried
      
      	  /home/pal20/dev/projects/scratch/test-1.7.3/lib/dozer-5.1.jar
      	  /home/pal20/.grails/1.3.2.BUILD-SNAPSHOT/projects/test-1.7.3/plugins/tomcat-1.3.1/lib/dozer-5.1.jar
      	  /home/pal20/.grails/1.3.2.BUILD-SNAPSHOT/projects/test-1.7.3/plugins/hibernate-1.3.1/lib/dozer-5.1.jar
      
      	==== grailsHome: tried
      
      	  /home/pal20/dev/tools/git/grails-core/lib/dozer-5.1-sources.jar
      
      	==== grailsHome: tried
      
      	  /home/pal20/dev/tools/git/grails-core/dist/dozer-5.1-sources.jar
      
      	==== grailsHome: tried
      
      	  /home/pal20/dev/tools/git/grails-core/plugins/grails-dozer-5.1.jar
      
      	==== grailsCentral: tried
      
      	  http://svn.codehaus.org/grails-plugins/grails-dozer/tags/RELEASE_5_1/grails-dozer-5.1.jar
      
      	==== grailsCore: tried
      
      	  http://svn.codehaus.org/grails/trunk/grails-plugins/grails-dozer/tags/RELEASE_5_1/grails-dozer-5.1.jar
      
      		[FAILED     ] net.sf.dozer#dozer;5.1!dozer.jar(javadoc):  (0ms)
      
      	==== grailsPlugins: tried
      
      	  /home/pal20/dev/projects/scratch/test-1.7.3/lib/dozer-5.1.jar
      	  /home/pal20/.grails/1.3.2.BUILD-SNAPSHOT/projects/test-1.7.3/plugins/tomcat-1.3.1/lib/dozer-5.1.jar
      	  /home/pal20/.grails/1.3.2.BUILD-SNAPSHOT/projects/test-1.7.3/plugins/hibernate-1.3.1/lib/dozer-5.1.jar
      
      	==== grailsHome: tried
      
      	  /home/pal20/dev/tools/git/grails-core/lib/dozer-5.1-javadoc.jar
      
      	==== grailsHome: tried
      
      	  /home/pal20/dev/tools/git/grails-core/dist/dozer-5.1-javadoc.jar
      
      	==== grailsHome: tried
      
      	  /home/pal20/dev/tools/git/grails-core/plugins/grails-dozer-5.1.jar
      
      	==== grailsCentral: tried
      
      	  http://svn.codehaus.org/grails-plugins/grails-dozer/tags/RELEASE_5_1/grails-dozer-5.1.jar
      
      	==== grailsCore: tried
      
      	  http://svn.codehaus.org/grails/trunk/grails-plugins/grails-dozer/tags/RELEASE_5_1/grails-dozer-5.1.jar
      
      		::::::::::::::::::::::::::::::::::::::::::::::
      
      		::              FAILED DOWNLOADS            ::
      
      		:: ^ see resolution messages for details  ^ ::
      
      		::::::::::::::::::::::::::::::::::::::::::::::
      
      		:: net.sf.dozer#dozer;5.1!dozer.jar(source)
      
      		:: net.sf.dozer#dozer;5.1!dozer.jar(javadoc)
      
      		::::::::::::::::::::::::::::::::::::::::::::::
      

      This is critical, because it seems to block the automatic installation of the Hibernate and Tomcat plugins. I have attached a project that exhibits the problem.

        Activity

        Hide
        Peter Ledbrook added a comment -

        Perhaps disabling transitive resolution for the problematic dependency may help? For example,

        runtime "org.springframework:spring-amqp:1.0.0.M2", {
            transitive = false
        }
        
        Show
        Peter Ledbrook added a comment - Perhaps disabling transitive resolution for the problematic dependency may help? For example, runtime "org.springframework:spring-amqp:1.0.0.M2" , { transitive = false }
        Hide
        Peter Ledbrook added a comment -

        Another workaround would be to have an internal Maven repo that has those dependencies stored in it. You could then put that at the top of the repository list.

        Show
        Peter Ledbrook added a comment - Another workaround would be to have an internal Maven repo that has those dependencies stored in it. You could then put that at the top of the repository list.
        Hide
        Ronny Løvtangen added a comment -

        Many artifact doesn't have sources and javadoc jars available, so this behavior is really bad for build performance.
        See also GRAILS-9021 which is essentially the same issue.

        Show
        Ronny Løvtangen added a comment - Many artifact doesn't have sources and javadoc jars available, so this behavior is really bad for build performance. See also GRAILS-9021 which is essentially the same issue.
        Hide
        Alex Anderson added a comment -

        I found this especially unhelpful when deploying to Heroku. Not sure that Peter's suggestion would be viable in this case.

        Show
        Alex Anderson added a comment - I found this especially unhelpful when deploying to Heroku. Not sure that Peter's suggestion would be viable in this case.
        Hide
        Graeme Rocher added a comment -

        fixed if you use Aether dependency management in 2.3

        Show
        Graeme Rocher added a comment - fixed if you use Aether dependency management in 2.3

          People

          • Assignee:
            Graeme Rocher
            Reporter:
            Peter Ledbrook
          • Votes:
            19 Vote for this issue
            Watchers:
            13 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Last Reviewed:

              Development