Eclipse Community Forums: Eclipse Platform » Dependency between java project and plugin project

Home » Eclipse Projects » Eclipse Platform » Dependency between java project and plugin project

Dependency between java project and plugin project [message #171268]

Tue, 16 December 2003 15:25

Eclipse User

I am having some trouble specifying project dependency between a regular
java project and a plugin project. Classes generated in regular java
project are referenced in plugin project. References are compile time.

For example, if there are two projects in workspace, project a and b.
Project a is a regular java project. Project b is a plugin project
dependent on project a. Project a contains one class A. Project b is a
simple view plugin created by PDE wizard.

I want to use class A from project a in plugin project b without packaging
class A in a jar and specifying it runtime dependency of plugin b. I have
specified the dependency in project b preferences. Both project a and b
compile correctly after the dependency has been specified. However, when
launching plugin b using runtime workbench, plugin b can not find class A.
How do you run dev/test/debug cycle of plugin b using runtime workbench
while specifying that plugin b is dependent on project a?

Regards,
Vladimir

Re: Dependency between java project and plugin project [message #171296 is a reply to message #171268]

Tue, 16 December 2003 15:42

Eclipse User

Just to add that I am having no trouble specifying dependency between
multiple java projects and launching various runtime configurations. Using
3.0 M5.

Re: Dependency between java project and plugin project [message #171311 is a reply to message #171268]

Tue, 16 December 2003 16:17

Eclipse User

Originally posted by: jdf.pobox.com

Vladimir wrote:

> I am having some trouble specifying project dependency between a regular
> java project and a plugin project.

There's no harm in converting the regular java project to a plugin; it
will not undo the Java nature of the existing project, and will make it
possible for other plugins to use it without any extra build steps, etc.

Select the project, and go to the menu "File->New->Other...->Plug-in
development->Convert projects to plug-in projects".

We have found that it is good practice to treat all Java projects as
plug-ins, and to exploit the ability of the PDE to automatically
generate classpaths from the plugin.xml file, thereby removing many
version dependencies.

--
Jonathan Feinberg jdf@us.ibm.com
http://domino.research.ibm.com/cambridge/research.nsf/pages/ cue.html

Re: Dependency between java project and plugin project [message #171654 is a reply to message #171311]

Wed, 17 December 2003 10:44

Eclipse User

Originally posted by: richkulp.NO.SPAM.us.ibm.com

Beside it must be in plugin. Plugins can't find code that is not in the
same plugin or required plugins. That's the way it works.

See:

http://www.eclipse.org/articles/Article-PDE-does-plugins/PDE -intro.html

and

http://www.eclipse.org/articles/Article-Plug-in-architecture /plugin_architecture.html

--
Thanks, Rich Kulp

Re: Dependency between java project and plugin project [message #171731 is a reply to message #171654]

Wed, 17 December 2003 13:53

Eclipse User

Rich and Jonathan,

Thanks for your responses. I am also discovering the power of project
scoped external tool builders using ant targets thus enabling seamless and
continuous build integration between projects. Ultimately I think that you
are right in your sugestion to use all plugin projects.

Cheers,
Vladimir

Previous Topic:	Font Control in Linux
Next Topic:	Associating a project with a snapshot view of clearcase

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Oct 31 01:12:18 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter