well at work I've been working on making our chopped up monolithic application more manageable.
the problem is that we use to have 1 project, now we have around 11 or so. each has their on library folder. At this point in time its an easy thing to deal with, in a years time when we start getting jars updated, its going to be a big pain in the a#se.
so I've been learning alot about maven and have started to implement it into our small applications and now I'm up to the corner stone of the project.
pull all the artifacts together and make an install script.
as its a custom piece of code that users ant and bash with uuencode and many other bits and pieces, i was not going to even try making a maven plugin to make my install.sh file.
i looked into ivy and found that it does not use the same local repository structure as maven but can use nexus.. so not good.
but then i found http://ptrthomas.wordpress.com/2009/03/08/why-you-should-use-the-maven-ant-tasks-instead-of-maven-or-ivy/
it seems you can pull in maven dependency's into ant and use them there.
my current thinking is to use the maven ant task to extract all the war's and config files in the maven local or remote repository and let ant/bash do its magic to make my custom install.sh file :)
