Forum Controls
Spotlight Features

The Rich Engineering Heritage Behind Dependency Injection

Andrew McVeigh takes us on a tour of the rich heritage behind dependency injection, what it represents, and tells us why its here to stay.

Java, the OLPC, and community responsibility

The "One Laptop Per Child" project has a great device ready to ship, but there's no Java on there. Let's think about working together to put Java on OLPC!
Replies: 2 - Pages: 1  
Threads: [ Previous | Next ]
  Click to reply to this thread Reply

Build problem with plugins. (help needed)

At 7:58 PM on Jul 24, 2008, Sridhar Blooming Javalobby Member wrote:

Hello All,
I have problem with the following scenario. I need your help in resolving
this problem.

I have two plugins A and B as described below

Plug-in A
src (a folder containing some classes)
thirdParty.jar
Manifest (manifest folder)

Plug-in B (depends on A)
src (a folder containing some classes using classes from A.src and
A.thirtdParty.jar)
Manifest (manifest folder)

Plugin A exports classes from it's src folder from the third party library
it included in it.

Now, if Plug-in A and Plug-in B are built in the work space, both of them
build fine.

However, if I do the following,
1) build Plugin-A separately
2) copy A.jar (plug in jar file created by export) into plugins folder
in my eclipse installation
3) create a work space with Plug-in B in it using eclipse.

The problem now is that Plug-B is compilation errors for classes from B
saying that it could not resolve the classes from A.
Am I doing something wrong here? What is wrong with my scenario above?

thanks a lot in advance,
Sri


  Click to reply to this thread Reply
1. At 10:23 AM on Jul 25, 2008, Eric Rizzo wrote:

Re: Build problem with plugins. (help needed)

Sri_know wrote:
> Hello All,
> I have problem with the following scenario. I need your help in resolving
> this problem.
>
> I have two plugins A and B as described below
>
> Plug-in A
> src (a folder containing some classes)
> thirdParty.jar
> Manifest (manifest folder)
>
> Plug-in B (depends on A)
> src (a folder containing some classes using classes from A.src and
> A.thirtdParty.jar)
> Manifest (manifest folder)
>
> Plugin A exports classes from it's src folder from the third party library
> it included in it.
>
> Now, if Plug-in A and Plug-in B are built in the work space, both of them
> build fine.
>
> However, if I do the following,
> 1) build Plugin-A separately
> 2) copy A.jar (plug in jar file created by export) into plugins folder
> in my eclipse installation
> 3) create a work space with Plug-in B in it using eclipse.
>
> The problem now is that Plug-B is compilation errors for classes from B
> saying that it could not resolve the classes from A.
> Am I doing something wrong here? What is wrong with my scenario above?

Just having a plugin installed (as you've done in step 2 above) does NOT
automatically make it available to projects in the workspace. You'll
need to add A.jar to Project B's build path. The easiest way to do that
is to use the Add Variable... button on the build path edit tab, and
then select the ECLIPSE_HOME variable, Extend..., and select A.jar

Hope this helps,
Eric
  Click to reply to this thread Reply
1. At 5:08 PM on Jul 25, 2008, Alon wrote:

Re: Build problem with plugins. (help needed)

I think the problem here is that A.jar has a nested jar - thirdParty.jar.
Eclipse doesn't know how to handle nested JARs. Try to export plug-in A as
a folder.



thread.rss_message