[GRADLE-2061] Using mavenLocal() is very slow in Milestone 7 Created: 23/Jan/12  Updated: 04/Jan/13  Resolved: 23/Jan/12

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-7
Fix Version/s: 1.0-milestone-8

Type: Bug
Reporter: Gradle Forums Assignee: Daz DeBoer
Resolution: Fixed Votes: 0


My company has a large body of code that we currently build with maven. I'm trying to introduce Gradle for some new components. However, as others have noticed using existing artifacts from the local Maven repository very slow. My (already slow) integration tests take >13 minutes to run with localMaven() and just over 3 minutes without it (3 minutes is bad enough!). For now my work around is to copy .jar files built by maven into src/main/libs and add these to the classpath in Gradle. This is fine for right now but

What is the recommended approach here? Is there an easy work around that I'm not thinking of? Migrating everything to Gradle all at once could be a considerable amount of work and very much out of scope for what I'm doing right now - on the other hand my alternative right now is to go back to Maven (which I also don't want to do). What are other people doing?

Comment by Gradle Forums [ 23/Jan/12 ]

I should have said:

  • I'm using milestone 7
  • The difference in timing (10mn) is reproducible based on whether mavenLocal() is included or not.


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