|
|
Optimize with a SATA RAID Storage Solution
Range of capacities as low as $1250 per TB. Ideal if you currently rely on servers/disks/JBODs
Page 4 of 5
<developers >
<developer >
<name >Eric Dobbs </name >
<id >dobbs </id >
<email >dobbs@apache.org </email >
<organization/ >
<roles >
<role >Java Developer </role >
</roles >
</developer >
<developer >
<name >Stephen Haberman </name >
<id >stephenh </id >
<email >stephenh@chase3000.com </email >
<organization/ >
<roles >
<role >Java Developer </role >
</roles >
</developer >
<developer >
<name >Fedor Karpelevitch </name >
<id >fedor </id >
<email >fedor@karpelevitch.net </email >
<organization/ >
<roles >
<role >Java Developer </role >
</roles >
</developer >
<developer >
<name >John McNally </name >
<id >jmcnally </id >
<email >jmcnally@collab.net </email >
<organization >CollabNet </organization >
<roles >
<role >Java Developer </role >
</roles >
</developer >
<developer >
<name >Martin Poeschl </name >
<id >mpoeschl </id >
<email >mpoeschl@marmot.at </email >
<organization >Tucana.at </organization >
<roles >
<role >Java Developer </role >
</roles >
</developer >
<developer >
<name >Daniel Rall </name >
<id >dlr </id >
<email >dlr@finemaltcoding.com </email >
<organization >CollabNet, Inc. </organization >
<roles >
<role >Java Developer </role >
</roles >
</developer >
<developer >
<name >Kurt Schrader </name >
<id >kschrader </id >
<email >kschrader@karmalab.org </email >
<organization/ >
<roles >
<role >Java Developer </role >
</roles >
</developer >
<developer >
<name >Jon Scott Stevens </name >
<id >jon </id >
<email >jon@latchkey.com </email >
<organization >CollabNet, Inc. </organization >
<roles >
<role >Java Developer </role >
</roles >
</developer >
<developer >
<name >James Taylor </name >
<id >jtaylor </id >
<email >james@jamestaylor.org </email >
<organization/ >
<roles >
<role >Java Developer </role >
</roles >
</developer >
<developer >
<name >Jason van Zyl </name >
<id >jvanzyl </id >
<email >jason@zenplex.com </email >
<organization >Zenplex </organization >
<roles >
<role >Java Developer </role >
</roles >
</developer >
</developers >
As mentioned earlier, Maven can manage all jar file dependencies for the build machines. Each dependency refers to a jar file
in a remote repository. In Maven's future versions, these dependencies might extend beyond jar files. Maven caches the jar
files on the local machine under the Maven directory. The <dependency> element has three child elements, <id>, <version>, and <url>. Maven looks in the remote repository for a directory with the same name as the <id>. Under that directory, it looks for a jars subdirectory. Inside the jars directory should be a jar file that has the filename id-version.jar. So for Torque's first dependency, the filename would be ant-1.4.1.jar. The external component's homepage should be specified in the <url> element, so Maven can generate site documentation for the dependencies with correct links.
Maven also uses this list to create the classpath for the builds:
<dependencies >
<dependency >
<id >ant </id >
<version >1.4.1 </version >
<url >http://jakarta.apache.org/ant/ </url >
</dependency >
<dependency >
<id >commons-beanutils </id >
<version >1.4 </version >
</dependency >
<dependency >
<id >commons-collections </id >
<version >2.0 </version >
<url >http://jakarta.apache.org/commons/collections.html </url >
</dependency >
<dependency >
<id >commons-configuration </id >
<version >1.0-dev </version >
<url >http://jakarta.apache.org/commons/ </url >
</dependency >
<dependency >
<id >commons-dbcp </id >
<version >1.0-dev-20020806 </version >
<url >http://jakarta.apache.org/commons/ </url >
</dependency >
<dependency >
<id >commons-lang </id >
<version >1.0-b1 </version >
<url >http://jakarta.apache.org/commons/ </url >
</dependency >
<dependency >
<id >commons-logging </id >
<version >1.0.1 </version >
<url >http://jakarta.apache.org/commons/ </url >
</dependency >
<dependency >
<id >commons-pool </id >
<version >1.0 </version >
<url >http://jakarta.apache.org/commons/pool/ </url >
</dependency >
<dependency >
<id >jcs </id >
<version >1.0-dev </version >
<url >http://jakarta.apache.org/turbine/jcs/ </url >
</dependency >
<dependency >
<id >jdbc </id >
<version >2.0 </version >
<url >http://java.sun.com/products/jdbc/download.html#spec </url >
</dependency >
<dependency >
<id >jndi </id >
<version >1.2.1 </version >
<url >http://java.sun.com/products/jndi/ </url >
</dependency >
<dependency >
<id >log4j </id >
<version >1.2.6 </version >
<url >http://jakarta.apache.org/log4j/ </url >
</dependency >
<dependency >
<id >stratum </id >
<version >1.0-b3 </version >
<url >http://jakarta.apache.org/turbine/stratum/ </url >
</dependency >
<dependency >
<id >tomcat </id >
<version >1.0 </version >
<jar >tomcat-naming-1.0.jar </jar >
<url >http://jakarta.apache.org/tomcat/ </url >
</dependency >
<dependency >
<id >velocity </id >
<version >1.3 </version >
<url >http://jakarta.apache.org/velocity/ </url >
</dependency >
<dependency >
<id >village </id >
<version >1.5.3 </version >
<url >http://share.whichever.com/index.php?SCREEN=village </url >
</dependency >
<dependency >
<id >xerces </id >
<version >2.0.2 </version >
<jar >xercesImpl-2.0.2.jar </jar >
<url >http://xml.apache.org/xerces2-j/ </url >
</dependency >
<!-- Packaged EntityResolver conflicts with the one in Xerces 1.4.4 -- >
<dependency >
<id >xml-apis </id >
<version >2.0.2 </version >
<url >http://xml.apache.org/xerces2-j/ </url >
</dependency >
<dependency >
<id >junit </id >
<version >3.7 </version >
<url >http://www.junit.org </url >
</dependency >
</dependencies >
The build element controls the project's build process: