Community
Participate
Working Groups
Using Eclipse 3.2 RC1 NOTE: This report is an ENHACEMENT, not a bug, so it should probably be left until after Eclipse 3.2 is released. Neglecting to include META-INF in build.properties causes the following fatal error for the plugin: !ENTRY org.eclipse.update.configurator 2006-04-24 16:02:55.584 !MESSAGE Plugin does not have a valid identifier: plugins/<id>_<version>/ Since all plugins are really OSGi bundles, and since OSGi requires every bundle to have a META-INF, it seems sensible for the PDE to verify that build.properties includes META-INF. For Java projects the PDE already ensures that '.' is included in build.properties. Ideally, if the project has no errors or warnings the resulting plugin/bundle should "just work". A problem such as this should really be detected by the tooling.
Also see bug 147621 that is closely related to this problem in that it asks for build.properties validation.
Created attachment 46452 [details] org.eclipse.pde.ui.patch Appeasing Wassim... I was working in this area already so sorry if I over-stepped ;)
Upon inspection of the patch, it seems to be lacking two things: 1. META-INF/MANIFEST.MF is also acceptable in bin.includes 2. old-style plug-ins don't have a manifest.mf. So we need to check the project first for the existing of this file before flagging it. use WorkspaceModelManager.hasBundleManifest(...)
Created attachment 46457 [details] org.eclipse.pde.ui.patch #1 should be taken care of here added support for #2 good deal
Patch released. Thanks Chris.