Hi, I have hands-on experience with Maven (1.x) and I used it for many internal projects. Dependencies declaration is really cool and very helpful. Executable XML as well. Tons of ready-to-use goals too and hacking Maven is a fun ... however; I think Ant can do this as well except the dependencies (I haven't tried Ivy). Saying that it means I really love Maven but for this project I think that Ant should be the sufficient (and more appropriate?).
1) How many dependencies can we think of (about 5 libraries right now) - does not seem to be a high number. 2) It can be a pain to code complex compilation and build process in Ant - but isn't this a good sign that you have to change something? This can force us to make compilation and build process more transparent. 3) With Ant we can still provide targets (goals in Maven terminology) for building a specific algorithm only. I think Maven would make sense if we want to make a specific project for each algorithm because each of algorithms can have different jar dependencies and/or jar versions. This sounds like quite complex scenario but it should be achievable with Maven. If we don't need this then I would vote for Ant (despite the fact I am Maven fan!). Lukas On Jan 30, 2008 9:06 AM, Ian Holsman <[EMAIL PROTECTED]> wrote: > Ken Montanez wrote: > > Ian, it looks like you have some experience with Maven. I have heard a > lot > > of good things about it from many people on many different projects, but > no > > personal experience to speak of - can you vouch for it? What do you like > > about it? Is there anything that you don't like/want to get away from? > > > > Ken > > > my experience is more as a 'user' of maven, I haven't ever written a pom > file or gone deeper than that. > > What I like about it is you specify what jars the projects needs (and > versions) and it goes and gets them and your code builds nicely, and it > can do things like deploy your code onto a tomcat server. > > regards > Ian > > > -- http://blog.lukas-vlcek.com/
