[GRADLE-2289] daemon and JAR entry META-INF/MANIFEST.MF not found Created: 10/May/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-rc-3
Fix Version/s: None

Type: Bug
Reporter: Szczepan Faber Assignee: Unassigned
Resolution: Won't Fix Votes: 1


 Description   
  1. I develop a plugin suite for the corporate environment.
  2. I install a fresh snapshot of the plugins jar into some local repository (ivy layout).
  3. I attempt to test that new snapshot with some local projects that use those plugins.
  4. When I use the daemon, multiple times a day the build of the consumer project fails with:
Caused by: java.io.FileNotFoundException: JAR entry META-INF/MANIFEST.MF not found in /Users/sfaber/local-repo/com/linkedin/rum/product-plugins/0.13.41-SNAPSHOT/product-plugins-0.13.41-SNAPSHOT.jar

Full stack trace: https://gist.github.com/8abf8e43f31fbec60d4e

The workaround is stopping the daemon: gradle --stop

I haven't had that problem with gradle M9.

 Comments   
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:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

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.

Generated at Wed Jun 30 12:17:54 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.