[GRADLE-2009] Eclipse .classpath generated incorrectly when using dependencies with a classifier Created: 21/Dec/11 Updated: 04/Jan/13 Resolved: 02/Jan/12 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 1.0-milestone-6 |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Klaus Lehner | Assignee: | Unassigned |
| Resolution: | Not A Bug | Votes: | 0 |
| Description |
|
I have dependencies in my build.gradle like those: compile group: 'cc.catalysts.cp', name: 'cp-api', version: cpVersion, configuration: 'runtime', classifier:'' (background: the module also has other artifacty, I only want to have those with no classifier) When I run gradle eclipse, then the .classpath file also contains all other artifacts in the build path, e.g. txt files pom files and other artifacts. This worked correctly with milestone-5, where all those artifacts where not put into the .classpath file. |
| Comments |
| Comment by Klaus Lehner [ 27/Dec/11 ] |
|
Just found that this is not an eclipse plugin issue, this is a general issue with classifiers. When I have a dependency to component x with classifier=jar and this component x has a dependency to y, then all artifacts (resp. all classifiers) of y are put into my classpath, not only the 'jar' classifier. This was working correctly in milestone-5 but since milestone-6 (and also in the current snapshot) this is working incorrectly |
| Comment by Klaus Lehner [ 27/Dec/11 ] |
|
found that problem was on our side in another ivy repository, you can delete that issue. |