|
|
| Re: ClassNotFound Exception{FIXED] [message #287762 is a reply to message #287759] |
Wed, 06 July 2005 20:48   |
Eclipse User |
|
|
|
Originally posted by: chaves-do-not-spam.inf.ufsc.br
Kevin wrote:
> The moment I added a second
> plugin, which the first plugin required, to that RCP I could no longer
> export the plugin or run it. I could still execute it with in the Eclipse
> Framework using Run.
Where was the dependency between the first and second plug-in specified?
If it was done in the plugin.xml, that would explain it. Once you have a
MANIFEST.MF, the plugin.xml is used only for declaring extensions and
extension points. Any runtime-relate information is completely ignored.
Otherwise, if you have steps to recreate the original problematic
scenario, by all means report it on bugzilla.
Rafael
|
|
|
| Re: ClassNotFound Exception{FIXED] [message #287809 is a reply to message #287762] |
Thu, 07 July 2005 08:17 |
 Daniel Krügler
Messages: 853
Registered: July 2009 |
Senior Member |
|
|
Rafael Chaves wrote:
> Kevin wrote:
>
>> The moment I added a second plugin, which the first plugin required,
>> to that RCP I could no longer export the plugin or run it. I could
>> still execute it with in the Eclipse Framework using Run.
>
>
> Where was the dependency between the first and second plug-in specified?
> If it was done in the plugin.xml, that would explain it. Once you have a
> MANIFEST.MF, the plugin.xml is used only for declaring extensions and
> extension points. Any runtime-relate information is completely ignored.
>
> Otherwise, if you have steps to recreate the original problematic
> scenario, by all means report it on bugzilla.
I can at least report the same experiences (problems) with the new OSGI
plugin manifest. We are working in a team, which since two days used the
old pure plugin.xml manifest and our product export worked fine all the
time.
Now a collegue started the first time to add a new plugin using the new
(recommended) OSGI plugin manifest and we were not able to realize an
exported RCP which successfully runs - ClassNotFound or resolution
problems all the time!
It might be worth adding that we did not touch the plugin.xml directly
to express dependencies, but used the dependencies page for that.
Although it is a good idea to provide a conversion utility **to** the
new osgi manifest, at least a reverse conversion to the pure 3.0
plugin.xml would be great. I fear, we have to do the same thing as the
OP to convert the new osgi manifests to the pure plugin.xml format....
Greetings from Bremen,
Daniel Krügler
|
|
|
| Re: ClassNotFound Exception{FIXED] [message #287842 is a reply to message #287809] |
Thu, 07 July 2005 14:10 |
| Eclipse User |
|
|
|
Originally posted by: chaves-do-not-spam.inf.ufsc.br
Note that all plug-ins end up having OSGi manifests (this was true even in
3.0). If you don't provide one, one will be automatically generated for
you during startup. There is no loss of functionality in doing that.
What may be occurring is that users are not familiar with the manifest
format (which is more complicated, because it is more powerful), so
mistakes tend to happen more often due to manual tweaking (not saying this
is your case).
Of course, it is not impossible that the tooling for composing or
generating manifests (which includes components from the OSGi runtime)
have issues. If you found any, please let the team know by reporting it on
Bugzilla.
Rafael
Daniel Krügler wrote:
> I can at least report the same experiences (problems) with the new OSGI
> plugin manifest. We are working in a team, which since two days used the
> old pure plugin.xml manifest and our product export worked fine all the
> time.
> Now a collegue started the first time to add a new plugin using the new
> (recommended) OSGI plugin manifest and we were not able to realize an
> exported RCP which successfully runs - ClassNotFound or resolution
> problems all the time!
> It might be worth adding that we did not touch the plugin.xml directly
> to express dependencies, but used the dependencies page for that.
>
> Although it is a good idea to provide a conversion utility **to** the
> new osgi manifest, at least a reverse conversion to the pure 3.0
> plugin.xml would be great. I fear, we have to do the same thing as the
> OP to convert the new osgi manifests to the pure plugin.xml format....
> Greetings from Bremen,
> Daniel Krügler
|
|
|
|
| Re: ClassNotFound Exception{FIXED] [message #287860 is a reply to message #287846] |
Thu, 07 July 2005 15:24 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
It is not documented because the auto-generated ones are just placed in
an internal storage area not meant for general access. However, you can
look at them just so you see what is produced.
You should do this from a running binary Eclipse configuration, probably
one with your exported old style plugins. Look in the
eclipse\configuration\org.eclipse.osgi\manifests
directory. That is where they store the manifests for old style plugins.
Note: I would make sure that your old-style plugin is at least the 3.0
style (i.e. you use YourPlugin() constructor and start(BundleContext)
kind of plugins) and not have the older runtime.compatibility
requirement and YourPlugin(IPluginDescriptor) kind of plugin constructor.
--
Thanks,
Rich Kulp
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03402 seconds
] 
Search
Help
Register
Login
Home
