Maven could also give us a more robust "eclipse-files" target based off of the dependencies as defined in pom.xml, and possibly "assemble-projects-eclipse" and "assemble-projects-dist" targets which could pull down into an eclipse workspace or a distribution directory that was all wired together and ready to go, i.e., no more "webapps not in classpath" and assorted other errors which are a product of the project split.
This is all doable with ant+ivy of course, or bash for that matter, but maven's inherently plugged into a maven repo and source repo and has conventions around defining your dependencies in one place and running different targets based off of them, so it would likely be more maintainable in the long run. +1 for exploring On Fri, Apr 2, 2010 at 11:04 AM, Drew Farris <drew.far...@gmail.com> wrote: > On Fri, Apr 2, 2010 at 8:23 AM, Enis Söztutar <enis....@gmail.com> wrote: > > .Do we have any build-specific reason that cannot be done with ivy. > > It can be done with ivy, but it's generally far more manageable to do > everything with maven because there is considerably less configuration > required. Less to configure, less to maintain. > > +1 for exploring, can't wait to give it a whirl. >
