[GRADLE-2492] pom generation broken for parallel execution Created: 21/Sep/12 Updated: 27/Jan/17 Resolved: 16/Jan/17 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 1.2 |
| Fix Version/s: | 2.5-rc-1 |
| Type: | Bug | ||
| Reporter: | Szczepan Faber | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Description |
|
The problem was detected by the CI builds: http://builds.gradle.org/viewLog.html?buildId=28132&tab=buildResultsDiv&buildTypeId=bt67 MavenConversionSpec used to validate converted-from-maven projects by running 'clean', 'build', 'install'. The last task was causing the trouble. |
| Comments |
| Comment by Adam Murdoch [ 20/Jul/13 ] |
|
This is fixed in the new `maven-publish` plugin, but not the old `maven` plugin. |
| Comment by Luke Daley [ 21/Jul/13 ] |
|
This has been fixed in Maven: http://jira.codehaus.org/browse/MNG-4542 |
| Comment by Ray [ 21/Mar/16 ] |
|
Since Gradle 2.5+ now uses Maven 3 for publishing, can this issue be marked as fixed? |
| 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:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle! |
| Comment by Ray [ 15/Nov/16 ] |
|
I do believe this is fixed. |