[GRADLE-810] Internal Gradle error with simple Grails build Created: 06/Feb/10  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Peter Ledbrook Assignee: Unassigned
Resolution: Won't Fix Votes: 1

Attachments: Zip Archive gradle-grails-plugin-bug.zip    
Issue Links:
Related
Related to GRADLE-240 Maven Snapshots are not properly reso... Resolved

 Description   

I have attached an example Grails project with a Gradle build that uses the Grails plugin. For some reason, the first time it builds I get an internal Gradle error. I think it's related to having the java.net repository on my search path (for GParallelizer).

I have put the output of gradle -d compile into a file called debug-output.txt that's in the root of the project.

 Comments   
Comment by Russel Winder [ 06/Feb/10 ]

Peter,

GParallelizer is no more, GPars is what should be being used. It is in the Codehaus Repository, groupId: org.codehaus.gpars, artifactId: gpars, version: 0.9.

Comment by Russel Winder [ 06/Feb/10 ]

GPars did get synced by Codehaus so it is in the main Maven repository as well.

Comment by Peter Ledbrook [ 06/Feb/10 ]

OK, I can't edit the issue, but you may want to drop the priority. I misunderstood the syntax for mavenRepo. I now have separate mavenRepo lines for the Codehaus Snapshots repository and the java.net one. However, there really needs to be a better error message!

The problem is that when Gradle asks Ivy to download the plugin JAR in DefaultResolvedArtifact.getFile(), it doesn't download the JAR. I guess in this particular case because the java.net repository doesn't contain the JAR file.

Comment by Peter Ledbrook [ 06/Feb/10 ]

Thanks Russel. I thought the name had changed, but didn't see a GPars entry in the repository. I hadn't realised the project's artifacts had moved. I'll look into updating the Grails dependencies.

Comment by Russel Winder [ 06/Feb/10 ]

Lowering priority as requested.

Comment by Hans Dockter [ 19/Apr/10 ]

This will be improved once we switch to a native Maven resolver.

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 11:39:29 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.