Weird requirement by Eclipse [message #182114] |
Wed, 29 November 2006 11:36 |
Eclipse User |
|
|
|
Originally posted by: sri1025.gmail.com
Hi!
I have two projects in my workspace. Like this
workspace
+
+
+- Project1
+
+- Project2
Project1 has external references to 2 jar files in its build path, and
Project2 refers Project1 in its build path. But eclipse was warning me to
add the 2 jar files (which Project1 refers) to Project2's build path
because it indirectly refers the classes in those jar files.
I think it should ideally be enough to have reference to just Project1.
Your thoughts?
Thanks,
Srikanth
|
|
|
Re: Weird requirement by Eclipse [message #182144 is a reply to message #182114] |
Wed, 29 November 2006 16:17 |
Eclipse User |
|
|
|
Originally posted by: wegener.cboe.com
Srikanth wrote:
> Hi!
> I have two projects in my workspace. Like this
> workspace
> +
> +
> +- Project1
> +
> +- Project2
> Project1 has external references to 2 jar files in its build path, and
> Project2 refers Project1 in its build path. But eclipse was warning me to
> add the 2 jar files (which Project1 refers) to Project2's build path
> because it indirectly refers the classes in those jar files.
> I think it should ideally be enough to have reference to just Project1.
> Your thoughts?
> Thanks,
> Srikanth
Sounds like you need to export the jar files in Project1. Open up the
Project1 properties. On the Java Build Path, there is an Order and Export
tab. Go to this tab and check the jar files that Project 2 needs. This
will make the jars available to any project that depends on Project1
(Project 2 in your case.)
|
|
|
Powered by
FUDForum. Page generated in 0.08017 seconds