On 19 February 2014 13:07, Ron Bets <ron.b...@oracle.com> wrote: > Thanks for the speedy response. > > I have run across these types of memory exceptions in the past, but given > that the build had been working correctly until I added the Maven > <artifact:dependencies/> bit, I naturally jumped to the conclusion that there > was something odd going on. This was exacerbated when the ant error log > actually identified the <artifact:dependencies/> as the offending line in the > build file. I'll play around with the memory parameters and see what happens. > > Cheers, > Ron > > Btw, is there a reference for all parameters supported by > <artifact:dependencies/>? I have
You mean this one? http://maven.apache.org/ant-tasks/examples/dependencies.html I'm afraid the two people who have answered your question really dont use Ant, so we dont know much about what you are doing. We use Maven natively rather than Ant with Maven dependency stuff. I'd recommend looking at the freely available books at http://maven.apache.org/articles.html and seeing whether you want to take the full plunge and migrate to Maven completely. Ant has its place, but for managing the Java software development lifecycle I'm obviously biased towards Maven :) --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
