fd035fd463
[maven-release-plugin] prepare for next development iteration
2010-11-20 02:54:24 +00:00
35f9d8339e
[maven-release-plugin] prepare release depot-1.1
2010-11-20 02:54:12 +00:00
e39e7fea42
We don't actually use any Ant code in Depot. Amazing!
2010-11-15 18:03:38 +00:00
206781f529
Depend on samskivert as a project and inherit its dependencies, export our own dependencies, bump to guava r07
2010-10-28 20:09:15 +00:00
5c56ec1fe7
Only do our signing when we're deploying to the public repository.
2010-10-18 21:53:03 +00:00
1c28f34ac4
Use hardcoded plugin version numbers to appease the Maven 3 nazis.
2010-10-18 21:52:16 +00:00
f293412671
[maven-release-plugin] prepare for next development iteration
2010-09-23 18:55:03 +00:00
448c89289a
[maven-release-plugin] prepare release depot-1.0
2010-09-23 18:54:54 +00:00
c609db73de
Prepare for forthcoming release. Apparently the Maven "process" is to leave
...
your POM at nextversion-SNAPSHOT and then when you do all the release
machinations, it shaves the -SNAPSHOT off, tags, builds and ships your thing,
then commits a new POM with nextnextversion-SNAPSHOT as the version.
2010-09-10 16:35:53 +00:00
d2a6b4422f
Various updates to bring POM up to date with current "best practices."
2010-09-09 20:27:45 +00:00
685e7e8ef5
Nixed some bits inherited from copied-and-pasted samskivert POM.
2010-09-09 05:30:30 +00:00
2d3cfff9b4
Adding needed Javadoc links. Removing unneeded system properties. Configuring
...
plugins to use latest version.
2010-09-09 05:26:50 +00:00
d2d88aa25e
A pom file for Depot. I believe that once the samskivert Maven repo is
...
authorized by Sonatype, I'll be able to upload Depot into it as well, since
they both use the com.samskivert groupId. w00t!
2010-09-08 23:30:08 +00:00
Michael Bayne