|
|
|
Re: Use of plain old Eclipse Plugins with Virgo Tooling [message #875483 is a reply to message #874622] |
Tue, 22 May 2012 20:31 |
Thorsten Schlathölter Messages: 312 Registered: February 2012 Location: Düsseldorf |
Senior Member |
|
|
Finally I "solved" this issue by declaring an xml builder that copies the META-INF\MANIFEST.MF into the bin folder.
This is not very practical because the builder is for sure only executed when the project is build. (I have got to admit that I never used an external builders before, so maybe I am missing something). But at least it works. If somebody tries this, make sure that you tell the builder to refresh the bin folder after completion. For plugins that make use of the Virgo BundleClasspathContainer (org.eclipse.virgo.ide.jdt.core.MANIFEST_CLASSPATH_CONTAINER) it is important to note that this container only works if the META-INF folder is located in a source folder. So in this case the META-INF folder might have to be copied from the source folder to the root of the plugin (I have not yet tried that).
I assume that this is only a temporary work around until the bug gets fixed.
Regards,
Thorsten
[Updated on: Tue, 22 May 2012 20:33] Report message to a moderator
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03145 seconds