StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Use <a href="http://maven.apache.org/" rel="noreferrer">Maven</a> or <a href="http://ant.apache.org/ivy/" rel="noreferrer">Ivy</a> to handle these shared jars. If you're wary of changing your projects too much, you can simply use <a href="http://ant.apache.org/ivy/" rel="noreferrer">Ivy</a> to manage the extra classpath for you.</p> <hr> <p>Both have good Eclipse plugins:</p> <h2><a href="http://m2eclipse.codehaus.org/" rel="noreferrer">m2eclipse</a></h2> <p><a href="http://img229.imageshack.us/img229/4848/mavendependencies.png" rel="noreferrer">Maven classpath container http://img229.imageshack.us/img229/4848/mavendependencies.png</a></p> <h2><a href="http://ant.apache.org/ivy/ivyde/" rel="noreferrer">IvyDE</a></h2> <p><a href="http://img76.imageshack.us/img76/3180/cpnode.jpg" rel="noreferrer">IvyDE classpath container http://img76.imageshack.us/img76/3180/cpnode.jpg</a></p> <p>which I've used with good results.</p> <p>You'll note that both of them reference jars <em>outside</em> the workspace, so the duplication is removed.</p> <hr> <p><strong>Update</strong> ( prompted by comments ):</p> <p>My reason for recommending this approach is that I strongly believe that it's simpler and clearer to <em>declare</em> dependencies rather then manually include them. There is a small one-time cost associated with this - smaller for Ivy than for Maven - but in the long run it does pay off.</p> <p>Another, smaller, benefit is the handling of transitive and conflicting dependencies. It's easy to forget <em>why</em> you need that commons-logging-1.1.jar in the classpath and whether you need to upgrade to 1.1.1. And also it's no fun to pull in all the depencies required for <em>e.g.</em> a Hibernate + Annotation + Spring combo. Focus on programming, not building.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload