[GRADLE-2556] Atributtes eclipse .classpath file generated from eclipse plugin are not ordered Created: 15/Nov/12 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | 1.2 |
Fix Version/s: | None |
Type: | Bug | ||
Reporter: | Zbigniew Sokolowski | Assignee: | Unassigned |
Resolution: | Won't Fix | Votes: | 0 |
Attachments: | screenshot-1.jpg |
Description |
As you can see in below generated file order of kind and path attributes is mixed. This is not a problem for eclipse. But it is problem for developers trying to troubleshoot. File becomes unreadable. Thanks, <classpathentry sourcepath="C:/Users/cwpl-zsokolow/.gradle/caches/artifacts-14/filestore/org.eclipse.jetty.orbit/org.apache.taglibs.standard.glassfish/1.2.0.v201112081803/source/f2702e293dd0cd8879c42a2c079bb0bc542d4b52/org.apache.taglibs.standard.glassfish-1.2.0.v201112081803-sources.jar" kind="lib" path="C:/Users/cwpl-zsokolow/.gradle/caches/artifacts-14/filestore/org.eclipse.jetty.orbit/org.apache.taglibs.standard.glassfish/1.2.0.v201112081803/orbit/2c4baa72af1d3aae3a1e029d4f8ca07498dabbe0/org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar" exported="true"/> |
Comments |
Comment by Zbigniew Sokolowski [ 15/Nov/12 ] |
one more look on the problem and I've found that if a jar has a version with sources then sourcepath attribute is first on the list |
Comment by Szczepan Faber [ 16/Nov/12 ] |
Thanks for reporting! Feel free to submit a pull request |
Comment by Zbigniew Sokolowski [ 16/Nov/12 ] |
Thank you very much Szczepan!, but what is a pull request? |
Comment by Zbigniew Sokolowski [ 20/Nov/12 ] |
what does it mean "pull request" ? |
Comment by Szczepan Faber [ 21/Nov/12 ] |
See https://github.com/gradle/gradle/blob/master/README.md Good luck! |
Comment by Zbigniew Sokolowski [ 21/Nov/12 ] |
I'm not familiar with github but I can't see pull back button, probably because I have only read-only access? |
Comment by Szczepan Faber [ 21/Nov/12 ] |
Hey Zbigniew Please read the available documentation on github and git and I bet that everything becomes clear Cheers! |
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 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. |