Eclipse Community Forums: Eclipse Platform » Plugin references to non-plugin projects

Home » Eclipse Projects » Eclipse Platform » Plugin references to non-plugin projects

Plugin references to non-plugin projects [message #203482]

Sat, 28 February 2004 14:44

Eclipse User

I am writing a plugin that depends on code (client libraries etc.)
developed as separate non-plugin projects. These projects also export
a bunch of third-party JARs that they depend on.

I can add my non-plugin projects to the plugin project's build path,
but it doesn't take effect at runtime. Also, the build path is reset
every time you edit plugin.xml or build.properties.

Instead, I'm forced to add my projects' output JARs as
jars.extra.classpath ("Extra Classpath Entries" in the GUI) in
build.properties.

Obviously that's an inconvenient hack. First of all it breaks
Eclipse's code completion. Secondly, it means I have to manually copy
JARs whenever I change the other projects.

Is there a way for a plugin project to depend on non-plugin projects?

Alexander.

Re: Plugin references to non-plugin projects [message #203552 is a reply to message #203482]

Sat, 28 February 2004 17:08

Eclipse User

Originally posted by: ed.burnette.REMOVE.THIS.sas.com

No, the recommended way to handle this is to copy all the jars your plug-in
needs into the plug-in itself or another plug-in created for that purpose.

--
Ed Burnette, co-author, Eclipse in Action
www.eclipsepowered.org

"Alexander Staubo" <zaphod@byzantine.no> wrote in message
news:c1qqt1$pd8$1@eclipse.org...
> Is there a way for a plugin project to depend on non-plugin projects?

Previous Topic:	support objectcontribution for IType static constraint by project nature?
Next Topic:	Re: Is the COBOL project dead?

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Apr 26 00:35:03 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter