use maven for dependency management

[GoogleCodeExporter]

in order to not having all the libraries in version control, i would suggest 
using maven in order to declare dependency libs.
http://maven.apache.org/

Original issue reported on code.google.com by dasjogibtsnet@gmail.com on 10 Jun 2010 at 10:02

[GoogleCodeExporter]

Original comment by iainsproat on 10 Jun 2010 at 10:32

• Added labels: Component-Scripts, Priority-Low, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

-1 on his. I wouldn't want the build system to depend on the availability of 
other services running, it makes it more fragile.

Original comment by stefano.mazzocchi@gmail.com on 10 Jun 2010 at 9:53

[GoogleCodeExporter]

Wow, I thought this would be a easy sell. I've used Maven for some of my 
projects and I found it very flexible and easy to use. However, if those who 
have actually committed code prefer the current build system then who am I to 
disagree.

Original comment by narphor...@gmail.com on 11 Jun 2010 at 5:14

[GoogleCodeExporter]

Maven is a locally installed tool, not an online service, so I don't understand 
Stefano's comment.  If you're building offline (or online and a repository 
isn't available for some reason), you can use the offline flag to build using 
cached dependency information.

Having said that, I'm neutral on the proposal.  In a lot of cases I actually 
prefer manual dependency management over the automagical updating of hidden 
dependencies one or two levels down.

Original comment by tfmorris on 11 Jun 2010 at 2:29

[GoogleCodeExporter]

While at Simile, we were very excited about Maven and used it quite pervasively 
for several projects. It worked mostly for our needs, but occasionally 
hiccupped when the maven repository site was down.

However, in Gridworks' case, we probably don't want to use maven because we 
want fine-grained control on where the jars go (into the WEB-INF/lib and 
MOD-INF/lib dirs).

Original comment by dfhu...@gmail.com on 13 Jun 2010 at 5:11

[GoogleCodeExporter]

To be more concrete concerning offline builds, use the flag:

  mvn -o

Original comment by tfmorris on 13 Jun 2010 at 6:47

[GoogleCodeExporter]

@tmorris: maven is a locally installed tool, but the jar dependencies are 
loaded from a repository over the web. If the repository is down, or slow, 
you're impacted. Most importantly, not all jars that we depend on are available 
in the main maven repo, which means that we would have to have our own maven 
repos, further increasing fragility.

Offline builds can only be done if the repository is local, which is no 
different than having the jars in svn like we do today.

Original comment by stefano.mazzocchi@gmail.com on 19 Jun 2010 at 7:07

• Changed state: WontFix