Allowing gump3 to run maven without changing the maven descriptor files
-> Parse Maven Descriptor file
-> run script for maven projects
-> match dependencies without loss of descriptor data
-> Create new project and module for gump
***Currently being built into gump3
Gump2 has an integration with Maven, albeit at the runtime interface (Gump2 can launch Maven) but not the metadata level, i.e. the Maven project descriptor. This means that Gump2 processes it's own (Gump) metadata format
 to understand how interact with Maven, and not Maven's native version
, which contain the same information. This duplication makes it harder for Maven projects to exist in Gump, even though a tool exists  that maps the formats. The truism "if data exists in two places one of them is wrong" holds, and often the Gump metadata is out of date/wrong.
We are looking for Gump3 to consume a Maven project descriptors  directly. Also, one thing we wish to resolve is . As such, the Gump3 code is in SVN, at , although we'll figure out a better way for you to access it.
Setting up a Maven project
In your module description you need to add type=”maven” to the end of that tag.
Java based build tool
<project href="project.xml" type="maven"/>
If any specific maven goals need to be added to the build a goal=”maven_goal” may also be added.
<project href="maven_test.xml" type="maven" goal=”jar”/>
Setting up Maven Gump id mismatches
Currently there is a mismatch between maven and gump ids. The fix right now is a mapping between these mismatches that can be found in gump/util/mavenToGump.conf. When new mismatches are discovered they should be added to this file(follow format already in file).