Duplicate entry for plugin [message #332756] |
Fri, 07 November 2008 15:38 ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: swt.magellium.fr
Hello all !
I have a simple dependency problem :
I have 4 java projects : MAIN1, MAIN2, COMMON1, COMMON2.
MAIN1 is a simple java project (not a plugin).
It uses COMMON1 (added as referenced project in the build path).
MAIN2 is a plugin project.
It uses COMMON1 (added as referenced plugin in the manifest).
So COMMON1 is used by MAIN1 as a java project, and by MAIN2 as a plugin
project.
Now, COMMON1 wants to use COMMON2.
In order to work with MAIN1, COMMON1 must refer to COMMON2 in it's build
path (referenced project).
In order to work with MAIN2, COMMON1 must refer to COMMON2 in it's
plugin dependencies (referenced plugin).
If I use such a configuration, an error appears on COMMON1 : it's build
path contains a duplicate entry : COMMON2.
COMMON2 is referred both as referenced java project and as referenced
plugin project...
How can I remove this "duplicate entry" error and still have the two
MAIN1 and MAIN2 projects working ??
Thanks a lot in advance !
Stephane
|
|
|
Re: Duplicate entry for plugin [message #332762 is a reply to message #332756] |
Fri, 07 November 2008 15:55 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) |
Ed Merks![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=ed.merks%40gmail.com) Messages: 33196 Registered: July 2009 |
Senior Member |
|
|
Stephane,
I would suggest sticking to plugin projects and editing only the
MANIFEST.MF dependencies rather than messing directly with
build/classpath. A plugin project can always be used to build a stand
alone jar and it's much easier to manage the classpath for plugins...
SWT wrote:
> Hello all !
>
> I have a simple dependency problem :
> I have 4 java projects : MAIN1, MAIN2, COMMON1, COMMON2.
>
> MAIN1 is a simple java project (not a plugin).
> It uses COMMON1 (added as referenced project in the build path).
> MAIN2 is a plugin project.
> It uses COMMON1 (added as referenced plugin in the manifest).
>
> So COMMON1 is used by MAIN1 as a java project, and by MAIN2 as a
> plugin project.
> Now, COMMON1 wants to use COMMON2.
> In order to work with MAIN1, COMMON1 must refer to COMMON2 in it's
> build path (referenced project).
> In order to work with MAIN2, COMMON1 must refer to COMMON2 in it's
> plugin dependencies (referenced plugin).
>
> If I use such a configuration, an error appears on COMMON1 : it's
> build path contains a duplicate entry : COMMON2.
> COMMON2 is referred both as referenced java project and as referenced
> plugin project...
>
> How can I remove this "duplicate entry" error and still have the two
> MAIN1 and MAIN2 projects working ??
> Thanks a lot in advance !
>
> Stephane
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.03093 seconds