Eclipse Community Forums: Rich Client Platform (RCP)

Home » Eclipse Projects » Rich Client Platform (RCP) » Project dependencies

Tue, 13 February 2007 08:36

Eclipse User

Originally posted by: jorgen.ekstrom.bredband.net

Hi,

I have developed an application using SWT/JFace which consists of several
standard java subprojects, and now I'm
trying to convert the main application into an RCP application/plugin. How
can I specify that my RCP application is
dependant on the other subprojects in my workspace so it compiles and runs?

....or do all my subprojects have to be converted into plugins in order for
OSGi framework to load them properly?

/ Jorgen

java.lang.NoClassDefFoundError: com/finsys/core/env/FinSysEnv
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Unknown Source)
at java.lang.Class.getConstructor0(Unknown Source)
at java.lang.Class.newInstance0(Unknown Source)
at java.lang.Class.newInstance(Unknown Source)
at
org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI .createExecutableExtension(RegistryStrategyOSGI.java:157)
at
org.eclipse.core.internal.registry.ExtensionRegistry.createE xecutableExtension(ExtensionRegistry.java:759)
at
org.eclipse.core.internal.registry.ConfigurationElement.crea teExecutableExtension(ConfigurationElement.java:243)
at
org.eclipse.core.internal.registry.ConfigurationElementHandl e.createExecutableExtension(ConfigurationElementHandle.java: 51)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:74)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:92)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:68)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:400)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336 )
at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
at org.eclipse.core.launcher.Main.run(Main.java:977)
at org.eclipse.core.launcher.Main.main(Main.java:952)

Re: Project dependencies [message #463548 is a reply to message #463547]

Tue, 13 February 2007 08:52

Eclipse User

Originally posted by: cemdayanik.gmail.com

you have two options:

1)convert each project to plugin.
-manifest.mf->runtime->exported packages->Add packages that you want to be
available for other projects.
-for the projects that will be using these: manifest.mf->dependencies->add
library plugin.

( you need to remove any dependencies added via project->buildpath )

2-add library projects as a jar. (manifest.mf->runtime->classpath)

I prefer the first way if it is not a external jar I am using..

Re: Project dependencies [message #463550 is a reply to message #463548]

Tue, 13 February 2007 09:00

Eclipse User

Originally posted by: cemdayanik.gmail.com

and be aware of this bug if you use first method:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=146042

it is said that it is resolved but 3.3M4 still has the same issue.

the fix in that forum only works with 3.1.2, I wasnt able to make it work
with 3.3M4

Re: Project dependencies [message #463551 is a reply to message #463550]

Tue, 13 February 2007 09:08

Eclipse User

Originally posted by: cemdayanik.gmail.com

umm, the bug is fixed with 3.3M5

Re: Project dependencies [message #463552 is a reply to message #463548]

Tue, 13 February 2007 09:29

Eclipse User

Originally posted by: jorgen.ekstrom.bredband.net

Thanks for your quick answer. Can I convert the subproject into a plugin by
simply adding a manifest and a
build.properties fiel to it, or what is required for Eclipse to regognize it
as a plugin? Or do I have to create
a new plug-in project and move the files over from the old project to the
new project?

Can I manage wihtout an Activator? Adding one would make my otherwise clean
library dependent on
Eclipse/OSGi which I would like to avoid as far as possible.

BR
Jorgen

"Cem Dayanik" <cemdayanik@gmail.com> wrote in message
news:3033c8efd058a81fe2fc71bbb4314d87$1@www.eclipse.org...
> you have two options:
>
> 1)convert each project to plugin. -manifest.mf->runtime->exported
> packages->Add packages that you want to be available for other projects.
> -for the projects that will be using these: manifest.mf->dependencies->add
> library plugin.
>
>
> ( you need to remove any dependencies added via project->buildpath )
>
> 2-add library projects as a jar. (manifest.mf->runtime->classpath)
>
>
> I prefer the first way if it is not a external jar I am using..
>
>
>
>

Previous Topic:	[Contributions] New Menu API in 3.3M5
Next Topic:	Close editor area

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Mar 23 21:23:04 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter