search

tesla / m2eclipse-tycho

25 stars 26 forks source link

Count not read generated bundle manifest message with no description #5

Open rombert opened 12 years ago

rombert commented 12 years ago

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.

ifedorenko commented 12 years ago

Can you try enable debug level for root logger in .metadata/.plugins/org.eclipse.m2e.logback.configuration/logback.${m2e.version}.xml ?

rombert commented 12 years ago

I've done that, see the log at https://gist.github.com/1662787 . It seems that the generated manifest is out of sync.

ifedorenko commented 12 years ago

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)?

rombert commented 12 years ago

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 java.lang.NullPointerException: null at org.eclipse.m2e.editor.xml.internal.MarkerLocationService.checkVarious(MarkerLocationService.java:529) [org.eclipse.m2e.editor.xml_1.1.0.20120111-2043.jar:na] at org.eclipse.m2e.editor.xml.internal.MarkerLocationService.addEditorHintMarkers(MarkerLocationService.java:221) [org.eclipse.m2e.editor.xml_1.1.0.20120111-2043.jar:na] at org.eclipse.m2e.core.internal.markers.MarkerUtils.addEditorHintMarkers(MarkerUtils.java:61) [org.eclipse.m2e.core_1.1.0.20120111-2043.jar:na] at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.readMavenProject(ProjectRegistryManager.java:640) [org.eclipse.m2e.core_1.1.0.20120111-2043.jar:na] at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:367) [org.eclipse.m2e.core_1.1.0.20120111-2043.jar:na] at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:327) [org.eclipse.m2e.core_1.1.0.20120111-2043.jar:na] at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryRefreshJob.run(ProjectRegistryRefreshJob.java:87) [org.eclipse.m2e.core_1.1.0.20120111-2043.jar:na] at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) [org.eclipse.core.jobs_3.5.100.v20110404.jar:na]

followed by groups of

2012-01-23 14:30:38,937 [Worker-5] ERROR o.e.m.e.x.i.MarkerLocationService - null org.eclipse.jface.text.BadLocationException: null at org.eclipse.jface.text.ListLineTracker.getLineOffset(ListLineTracker.java:201) ~[na:na] at org.eclipse.jface.text.AbstractLineTracker.getLineOffset(AbstractLineTracker.java:169) ~[na:na] at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.getLineOffset(BasicStructuredDocument.java:1495) ~[na:na] at org.eclipse.m2e.editor.xml.internal.MarkerLocationService.findLocationForMarker(MarkerLocationService.java:87) ~[na:na] at org.eclipse.m2e.core.internal.markers.MarkerUtils.decorateMarker(MarkerUtils.java:43) [org.eclipse.m2e.core_1.1.0.20120111-2043.jar:na] at org.eclipse.m2e.core.internal.markers.MavenMarkerManager.addErrorMarker(MavenMarkerManager.java:302) [org.eclipse.m2e.core_1.1.0.20120111-2043.jar:na] at org.eclipse.m2e.core.internal.markers.MavenMarkerManager.addErrorMarkers(MavenMarkerManager.java:290) [org.eclipse.m2e.core_1.1.0.20120111-2043.jar:na] at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.setupLifecycleMapping(ProjectRegistryManager.java:543) [org.eclipse.m2e.core_1.1.0.20120111-2043.jar:na] at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:445) [org.eclipse.m2e.core_1.1.0.20120111-2043.jar:na] at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:327) [org.eclipse.m2e.core_1.1.0.20120111-2043.jar:na] at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryRefreshJob.run(ProjectRegistryRefreshJob.java:87) [org.eclipse.m2e.core_1.1.0.20120111-2043.jar:na] at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) [org.eclipse.core.jobs_3.5.100.v20110404.jar:na]

ifedorenko commented 12 years ago

please provide complete standalone sample project and steps to reproduce the problem.

rombert commented 12 years ago

There still is some sort of error , even with the nightly m2eclipse.

Steps to reproduce:

  1. Check out Apache Sling from SVN using the CLI:

svn co http://svn.apache.org/repos/asf/sling/trunk/ sling

  1. Import the sling projects using "Import existing Maven projects" . I have chosen to 'Resolve later' the plugins in error.
  2. Restart Eclipse when prompted

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 )

ifedorenko commented 12 years ago

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).