Eclipse Community Forums: Java Development Tools (JDT) » Importing resources from other projects

Help

Home

Home » Language IDEs » Java Development Tools (JDT) » Importing resources from other projects

Show: Today's Messages :: Show Polls :: Message Navigator

Importing resources from other projects [message #242908]

Mon, 16 April 2007 09:40

Oliver Plohmann

Messages: 9
Registered: July 2009

Junior Member

Hello,

we want to split our application into several eclipse projects to achieve
better partitioning, e.g. mimic config maps from OTI/Envy. I found the
project set plugin made by some people at CSC. It does exactly what we
need (intension is exactly the same but there is no version for eclipse
3.2 and I would prefer a general solution from the vendor herself rather
than having our whole eclipse project mechanism being dependent from a
little plugin that may be discontinued one day or already is).

So the problem is that there is a project A that defines some jars.
Project B includes Project A, however project A's jars do not become
visible to project B. This is the way eclipse works. So there is no way
round adding the jars from projet A explicitly to project B's project
path. Once a new jar has been added to project A, it also has to be added
to project B (at least some link).
This is not very elegant and can become tedious. My question is whether
somebody knows a solution to this.

Thanks, Oliver Plohmann

Report message to a moderator

Re: Importing resources from other projects [message #242924 is a reply to message #242908]

Mon, 16 April 2007 14:40

Eclipse User

Originally posted by: wegener.cboenospam.com

You need to export the Project A jar files. Go to the Order and Export tab
on the Java Build Path properties dialog for Project A. Check the jar files
you want to have accessable to Project B. Go to Project B and remove the
explicit definition of the jar files from the build path.

"Oliver Plohmann" <oliver@plohmann.com> wrote in message
news:64b1b48a1436ef8d609ff5c860ea4fa0$1@www.eclipse.org...
> Hello,
>
> we want to split our application into several eclipse projects to achieve
> better partitioning, e.g. mimic config maps from OTI/Envy. I found the
> project set plugin made by some people at CSC. It does exactly what we
> need (intension is exactly the same but there is no version for eclipse
> 3.2 and I would prefer a general solution from the vendor herself rather
> than having our whole eclipse project mechanism being dependent from a
> little plugin that may be discontinued one day or already is).
>
> So the problem is that there is a project A that defines some jars.
> Project B includes Project A, however project A's jars do not become
> visible to project B. This is the way eclipse works. So there is no way
> round adding the jars from projet A explicitly to project B's project
> path. Once a new jar has been added to project A, it also has to be added
> to project B (at least some link).
> This is not very elegant and can become tedious. My question is whether
> somebody knows a solution to this.
>
> Thanks, Oliver Plohmann
>

Report message to a moderator