-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Count not read generated bundle manifest message with no description #5
Comments
Can you try enable debug level for root logger in .metadata/.plugins/org.eclipse.m2e.logback.configuration/logback.${m2e.version}.xml ? |
I've done that, see the log at https://gist.github.com/1662787 . It seems that the generated manifest is out of sync. |
I've opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=369380 to track maven console view debug toggle problems. Are you able to reproduce the problem with generated manifest out of sync with latest m2e 1.1 snapshot build (see http://www.eclipse.org/m2e/download/ installation instructions)? |
After upgrading I no longer get that specific error, however I do get many other errors: 2012-01-23 14:30:18,456 [Worker-5] ERROR o.e.m.e.x.i.MarkerLocationService - Error checking for warnings followed by groups of 2012-01-23 14:30:38,937 [Worker-5] ERROR o.e.m.e.x.i.MarkerLocationService - null |
please provide complete standalone sample project and steps to reproduce the problem. |
There still is some sort of error , even with the nightly m2eclipse. Steps to reproduce:
svn co http://svn.apache.org/repos/asf/sling/trunk/ sling
After the workspace is refreshed and rebuilt, several plugins are in error null ( org.apache.felix:maven-bundle-plugin:2.0.1:manifest:bundle-manifest:process-classes ) |
This project is way too big for me to troubleshoot. Please provide a small standalone project that demonstrates just the problem with maven-bundle-plugin and does not require any other configurators (scala, modello, etc). |
I have a some projects in the reactor which use the felix-bundle-plugin and for which I have logged warning in the error log and the maven console: 1/23/12 11:10:27 AM GMT+02:00: [WARN] Count not read generated bundle manifest of project bla-bla-bla . Even with debug logging enabled, neither the Error Log view nor the Maven Console ( in the Console view ) show the root cause, so I'm unable to find the root cause.
Please allow for the root cause to propagate so that I know if I need to fix my POMs or report a proper bug.
The text was updated successfully, but these errors were encountered: