|Re: Build path selection list [message #983810 is a reply to message #983545]
||Wed, 14 November 2012 06:53
| Russell Bateman
Registered: July 2009
Location: Provo, Utah, USA
On 11/13/2012 06:55 PM, John Conrad wrote:|
> The Build Path "option" gives a list of mostly jar files that one can
> add to a project. How do you designate where eclipse goes to "find" the
> list it presents?
Eclipse offers two "places" to get JARs although through more than two
interfaces (buttons) under the Libraries tab.
1. Add library takes you to a list grouping tools Eclipse knows about
because you configured it so: JDK, Tomcat, etc. plus stuff like JUnit,
User libraries you establish yourself in collections of third-party
libraries, Web App libraries you get from other projects in the
workspace when relevant.
2. Add JAR/Add JARs takes you nowhere: you must browse to find a
third-party JAR you want to use.
This is also where/how you associate Javadoc and/or source code with the
JARs you consume making Eclipse Content Assist work in your Java editor.
All of this is recorded in the .classpath file at the root of your project.
Is this what you meant?
You can mitigate all of this Build Path stuff by adopting Maven to a)
create the Eclipse project (via an appropriate archetype), b) keep the
needed JARs up-to-date from web sources, etc. It's very difficult to
grasp (about as mysterious as the old autotools on Unix/Linux for
building C/C++ and other resources0, but very effective. Many swear by
There are still other ways such as Apache Ivy which works a little like
Maven except that it's far easier because it uses XML in ant scripts.
I haven't used something called Gradle and don't know how it works, but
I've heard good things about it.
Hope this helps.
Powered by FUDForum
. Page generated in 0.03893 seconds