Author: jvanzyl
Date: Tue Oct 4 11:32:00 2005
New Revision: 294893
URL: http://svn.apache.org/viewcvs?rev=294893&view=rev
Log:
o contrast a typical ant build
Added:
maven/components/trunk/maven-site/src/site/apt/guides/getting-started/introduction-to-dependency-management.apt
(with props)
maven/components/trunk/maven-site/src/site/apt/guides/getting-started/introduction-to-repositories.apt
(with props)
Modified:
maven/components/trunk/maven-site/src/site/apt/guides/getting-started/index.apt
maven/components/trunk/maven-site/src/site/resources/ant/build-a4.xml
Modified:
maven/components/trunk/maven-site/src/site/apt/guides/getting-started/index.apt
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-site/src/site/apt/guides/getting-started/index.apt?rev=294893&r1=294892&r2=294893&view=diff
==============================================================================
---
maven/components/trunk/maven-site/src/site/apt/guides/getting-started/index.apt
(original)
+++
maven/components/trunk/maven-site/src/site/apt/guides/getting-started/index.apt
Tue Oct 4 11:32:00 2005
@@ -299,7 +299,9 @@
You can now take a look in the the <<<${basedir}/target>>> directory and you
will see the generated JAR file.
Now you'll want to install the artifact you've generated, the JAR file, in
your local repository
- (<<<~/.m2/repository>>> is the default value). To do so execute the following
command:
+ (<<<~/.m2/repository>>> is the default value). For more information on
repositories you can refer to our
+ {{{introduction-to-archetypes.html}Introduction to Repositories}} but now on
to installing our artifact!
+ To do so execute the following command:
+----+
@@ -346,6 +348,14 @@
[INFO]
----------------------------------------------------------------------------
+----+
+
+ Now you have walked through setting up setting up a typical Maven project,
building, testing, packaging and installing.
+ This is likely the vast majority of what you will be doing with Maven and if
you'ved noticed everything you've been
+ able to do up to this point has been driven by an 18 line file, namely the
project's model or POM. If you look at
+ a typical Ant {{{../../ant/build-a1.xml}build file}} that provides the same
functionality that we've achieved thus
+ far you'll notice it's already twice the size of the POM and we're just
getting started! There is far more
+ functionality available to you as a user of Maven without requiring any
additions to our POM as it is currently. To
+ get any more functionality out of our example Ant build file you must keep
making error prone additions.
~~* How do I package resources inside my JAR?
~~ o EIDSL
Added:
maven/components/trunk/maven-site/src/site/apt/guides/getting-started/introduction-to-dependency-management.apt
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-site/src/site/apt/guides/getting-started/introduction-to-dependency-management.apt?rev=294893&view=auto
==============================================================================
---
maven/components/trunk/maven-site/src/site/apt/guides/getting-started/introduction-to-dependency-management.apt
(added)
+++
maven/components/trunk/maven-site/src/site/apt/guides/getting-started/introduction-to-dependency-management.apt
Tue Oct 4 11:32:00 2005
@@ -0,0 +1,36 @@
+ ------
+ Introduction to Dependency Management
+ ------
+ Jason van Zyl
+ ------
+ 12 October 2005
+ ------
+
+Introduction to Dependency Management
+
+* How to Maintain Versions of Dependencies
+
+ In a multi-project
+
+ so using something as geronimo/continuum/cargo as an example i can document
that placing all deps used by the overall project in a TLP depMan section is
the way to go?
+
+ o use TLP for all deps used in a project
+ o in each project declare the dep and using groupId/artifactId and scope
+
+ if you provide exclusions in your dependency, and exclusions in your
depMgmt, the exclusions are NOT merged...local always wins
+<jdcasey> it's only an issue for exclusions, because it's a complex element
+
+ so exclusions in the depMan element at the parent level and child level
are not merged? is that correct?
+<jason> and the child level will win for a given dependency?
+<jdcasey> um, not sure how that works...haven't looked at it, but I believe
that's correct...
+<jdcasey> I'd have to look at the code
+
+ and injection only happens if there isn't something in the way
+<jdcasey> :)
+
+injection in depMan
+
+-----
+
+-----
+
Propchange:
maven/components/trunk/maven-site/src/site/apt/guides/getting-started/introduction-to-dependency-management.apt
------------------------------------------------------------------------------
svn:eol-style = native
Propchange:
maven/components/trunk/maven-site/src/site/apt/guides/getting-started/introduction-to-dependency-management.apt
------------------------------------------------------------------------------
svn:keywords = "Author Date Id Revision"
Added:
maven/components/trunk/maven-site/src/site/apt/guides/getting-started/introduction-to-repositories.apt
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-site/src/site/apt/guides/getting-started/introduction-to-repositories.apt?rev=294893&view=auto
==============================================================================
---
maven/components/trunk/maven-site/src/site/apt/guides/getting-started/introduction-to-repositories.apt
(added)
+++
maven/components/trunk/maven-site/src/site/apt/guides/getting-started/introduction-to-repositories.apt
Tue Oct 4 11:32:00 2005
@@ -0,0 +1,9 @@
+ ------
+ Introduction to Repositories
+ ------
+ Jason van Zyl
+ ------
+ 12 October 2005
+ ------
+
+Introduction to Repositories
Propchange:
maven/components/trunk/maven-site/src/site/apt/guides/getting-started/introduction-to-repositories.apt
------------------------------------------------------------------------------
svn:eol-style = native
Propchange:
maven/components/trunk/maven-site/src/site/apt/guides/getting-started/introduction-to-repositories.apt
------------------------------------------------------------------------------
svn:keywords = "Author Date Id Revision"
Modified: maven/components/trunk/maven-site/src/site/resources/ant/build-a4.xml
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-site/src/site/resources/ant/build-a4.xml?rev=294893&r1=294892&r2=294893&view=diff
==============================================================================
--- maven/components/trunk/maven-site/src/site/resources/ant/build-a4.xml
(original)
+++ maven/components/trunk/maven-site/src/site/resources/ant/build-a4.xml Tue
Oct 4 11:32:00 2005
@@ -28,4 +28,25 @@
<target name="jar" description="o Create the jar" depends="compile">
<jar jarfile="target/${final.name.api}.jar"/>
</target>
+ <target name="test" depends="test:compile" description="Run all acceptance
tests and unit tests">
+ <mkdir dir="${test.reports.dir}"/>
+ <junit printsummary="no" fork="yes" forkmode="once"
haltonfailure="${junit.haltonfailure}" includeantruntime="true">
+ <sysproperty key="java.awt.headless" value="true"/>
+ <classpath refid="classpath"/>
+ <formatter type="brief" usefile="no"/>
+ <formatter type="xml"/>
+ <batchtest todir="${test.reports.dir}">
+ <fileset dir="src/test/java">
+ <include name="${test.src.includes}"/>
+ </fileset>
+ </batchtest>
+ </junit>
+ <junitreport todir="${test.reports.dir}">
+ <fileset dir="${test.reports.dir}">
+ <include name="TEST-*.xml"/>
+ </fileset>
+ <report format="frames" todir="${test.reports.dir}/html"/>
+ </junitreport>
+ <echo message="Detailed results written to report :
${test.reports.dir}/html/index.html"/>
+ </target>
</project>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
