[GRADLE-2991] Application plugin's CreateStartScripts assumes all classpath files are present in lib dir Created: 20/Jan/14 Updated: 24/Jan/17 Resolved: 24/Jan/17 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Gradle Forums | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 12 |
| Description |
|
The `classpath` property is mapped to `sourceSets.main.runtimeClasspath + jar.outputs.files`. It is assumed that each file of this property is going to be present in the lib directory of the application distribution. This makes adding to the classpath awkward as it requires adding to the classpath property and ensuring that the file is present in the lib directory as two separate steps. |
| Comments |
| Comment by Yeison Rodriguez [ 02/Dec/14 ] |
|
So, how do fixes happen? Can I make the fix and do a pull request? |
| Comment by Marcin Erdmann [ 03/Dec/14 ] |
|
Yes, providing a pull request with appropriate test coverage is the fastest way to get something of particular interest to you 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 Benjamin Muschko [ 24/Jan/17 ] |
|
You can use a custom template to fulfill the use case. The Javadocs provide an example. |