[GRADLE-1750] CLONE - Resolve performance is still slow for project dependencies when they are deeply nested. Created: 16/Aug/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 0.8
Fix Version/s: None

Type: Improvement
Reporter: Marius Kotsbak Assignee: Hans Dockter
Resolution: Won't Fix Votes: 4

Comment by Marius Kotsbak [ 16/Aug/11 ]


Total time: 23 mins 16.342 secs

Gradle file:

apply plugin: 'java'
apply plugin: 'maven'


{ mavenLocal() mavenRepo urls: ["https://repository.jboss.org/nexus/content/repositories/releases/"] mavenRepo urls: ["https://repository.jboss.org/nexus/content/repositories/thirdparty-releases/"] mavenRepo urls: ["https://repository.jboss.org/nexus/content/repositories/deprecated/"] mavenRepo urls: ["http://repo1.maven.org/maven2"] mavenRepo urls: ["http://download.java.net/maven/2/"] }

dependencies {
compile "org.codehaus.woodstox:wstx-asl:3.2.1"
compile ("org.jboss.jbossas:jboss-as-client:6.0.0.Final")

{ exclude group: 'org.hibernate', module: 'hibernate-annotations' exclude group: 'org.jboss.security', module: 'jbossxacml' exclude group: 'ws-commons', module: 'policy' exclude group: 'woodstox', module: 'wstx-asl' }


Comment by Russ Egan [ 30/Sep/11 ]

I think I'm seeing this too. ejbs with jboss dependencies create a big dependency graph. Slows down any operation that accesses it: gradle dependencies, compilation, building wars, checking up to date status of war, etc.

Comment by Bin Lin [ 16/Jun/14 ]

We have same performance problem as our dependency graph is quite big, deep and complex.
We are on gradle 1.12

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:03:24 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.