Bye bye Ivy. Even though I like you better, building with Maven makes

publishing to the public Maven repositories much simpler. Being published to
the public Maven repositories makes life easier for everyone who wants to
depend on samskivert.


git-svn-id: https://samskivert.googlecode.com/svn/trunk@2864 6335cc39-0255-0410-8fd6-9bcaacd3b74c
This commit is contained in:
samskivert
2010-09-09 18:21:54 +00:00
parent db601ce31f
commit eb85d7d40b
3 changed files with 9 additions and 241 deletions
+9 -9
View File
@@ -36,12 +36,12 @@ following principles:
Building
--------
The library is built using ant. If you aren't already using ant for other
projects, it can be found here:
The library is built using Ant or Maven, pick your poison. If you use ant, you
will need to obtain the jar files enumerated in etc/libs-incl.xml and place
them in the lib/ directory. If you use Maven, the dependencies will be
automatically fetched.
http://ant.apache.org/
Invoke ant with any of the following targets:
Invoke Ant with any of the following targets:
all: builds the class files and javadoc documentation
compile: builds only the class files (dist/classes)
@@ -49,11 +49,11 @@ Invoke ant with any of the following targets:
tests: builds and runs the unit tests
dist: builds the distribution jar file (dist/samskivert.jar)
It is highly recommended to use the Ivy-based build file, which will
automatically download any dependencies. The build file will also download Ivy
if needed. For example, to build everything invoke:
Invoke Maven with the following targets:
% ant -f build-ivy.xml all
mvn test: builds the code and runs the tests
mvn package: builds the code and creates target/samskivert-X.X.jar
mvn install: builds and installs samskivert into your local Maven repository
Distribution
------------