[GRADLE-2391] osgi plugin fails to jar if there are no classes Created: 17/Jul/12 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Improvement | ||
Reporter: | Gradle Forums | Assignee: | Unassigned |
Resolution: | Won't Fix | Votes: | 5 |
Issue Links: |
|
Description |
See forum issue for steps to reproduce. |
Comments |
Comment by Denis Tunović [ 20/Nov/13 ] |
Any update on this issue? |
Comment by Adam Murdoch [ 25/Nov/13 ] |
Not yet. Would you be interested in helping to fix this issue? |
Comment by Denis Tunović [ 10/Jan/14 ] |
I am pretty new to Gradle. When I have more experience I will, if it is not fixed by then. |
Comment by Peter Keller [ 18/Aug/14 ] |
We want to add a blueprint.xml to an OSGI bundle with Apache Camel route definitions but without any additional Java classes. However this is not possible if this issue is not 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 [ 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. |