[GRADLE-2339] Need a Deb creation task Created: 07/Jun/12 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | New Feature | ||
Reporter: | Russel Winder | Assignee: | Unassigned |
Resolution: | Won't Fix | Votes: | 5 |
Description |
Currently people are using the Ant task for creating Deb files in Gradle. This Ant task appears not to be supported any more. It would be good to take this opportunity to create a Gradle "native" task. |
Comments |
Comment by Shin [ 25/Nov/12 ] |
Picked up on this because I'm starting to look at using more Debian/Ubuntu systems soon so I haven't tried anything yet but jpkg (http://code.google.com/p/jpkg-library/) looks promising and it's written in Java. Otherwise I'd use something like the Effing Package Manager to read the source dirs and give me a .deb back. But you'd have to have it already on your system (ruby). |
Comment by Tobias Gesellchen [ 23/Oct/13 ] |
Without knowing the old Ant task and its features, you might want to search for Gradle plugins not being included in the official Gradle package. There are some links available on http://wiki.gradle.org/display/GRADLE/Plugins. Including some shameless self-promotion, here is another list with quite promising Debian/Ubuntu packaging plugins: As always, it depends on your needs which plugin fits best. |
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. |