4 ms·
There are at least two: 1) The Maven Ant tasks: http://maven.apache.org/ant-tasks/index.html http://maven.apache.org/ant-tasks/index.html 2) Ivy (now part of t
by jsankey 17y ago
There are at least two:
1) The Maven Ant tasks: http://maven.apache.org/ant-tasks/index.html http://maven.apache.org/ant-tasks/index.html
2) Ivy (now part of the Ant project): http://ant.apache.org/ivy/ http://ant.apache.org/ivy/
We use Ant+Ivy, and although it has some quirks Ivy works well enough for dependencies.
- nicpottier 17y agoDo either one of those actually pull down the appropriate sources and javadocs, and update my Eclipse classpath to include them with one command? I'm actually asking, not being snarky, as it doesn't look built in with Ivy and the few little projects claiming to do it don't look very active, what has been your experience? As I said, that is the one big carrot still keeping me in mvn camp.
- zupatol 17y agoI've worked with ivy on a project a few years ago and the integration with eclipse worked fine for the classpath and sources. I didn't check about the javadocs. Ivy is mainly a tool to work with ant, so it makes some sense that IDE integration is not in the same project, but as far as I could see, ivy and the eclipse plugin are written by the same people. The eclipse plugin was actually one of the reasons for choosing ivy over maven, because at the time maven was moving to 2.0 and its eclipse plugin was not yet available or stable. The other reason was the documentation. At the time there seemed to be more documentation about ivy than about all functionalities of maven together.