[GRADLE-855] Native JarJar archive task Created: 16/Mar/10 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | New Feature | ||
Reporter: | Hans Dockter | Assignee: | Unassigned |
Resolution: | Won't Fix | Votes: | 5 |
Comments |
Comment by Robert Fischer [ 16/May/12 ] |
FYI, I'm going to rework my OneJar plugin to be a JarJar Links plugin. Gradle is more than welcome to take the code—I release it under the CC0. |
Comment by René Gröschke (Inactive) [ 10/Jul/12 ] |
A native JarJar gradle task must drive the Main class. A more elegant implementation is currently not possible due to https://code.google.com/p/jarjar/issues/detail?id=54 |
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. |