[GRADLE-2268] Jar manifest generation should be a separate task, particularly for osgi jars Created: 01/May/12 Updated: 10/Feb/17 Resolved: 10/Feb/17
At the moment, we create the manifest file as part of the jar task everytime.
This is particularly problematic for large OSGi jars as this means invoking the bnd tool, which can take a long time. What's worse is that given the current arrangement, we are running it even when the jar task is up-to-date.
If we moved the manifest generation into its own task, we could manage the inputs properly and avoid running the bnd tool unnecessarily.
|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.