c3c651340b
Guava 10.0.
2011-09-28 22:32:02 +00:00
3c1e6f7538
Depot needs java 1.6
2011-07-01 18:11:14 +00:00
b6942ec74a
Remove and ignore Eclipse files in favor of letting people generate their own using m2eclipse
2011-06-27 20:51:07 +00:00
ee93f91e61
Preparing for depot-1.5-SNAPSHOT development.
2011-05-24 20:57:26 +00:00
6c47a9c4ac
Preparing for 1.4 release.
2011-05-24 20:50:06 +00:00
1f7263c6fa
Preparing for 1.4-SNAPSHOT development.
2011-03-23 22:19:01 +00:00
19d9821f66
Preparing for 1.3 release.
2011-03-23 22:16:54 +00:00
8d56a93538
Meh, I was wrong in r841. Because the target version is 1.6, anything that tries to build against
...
depot with a 1.5 compiler is going to blow up with a mismatched version. Go back to 1.5 in build.xml
and pom.xml, but leave Eclipse using a 1.6 JVM. This means if anyone regenerates the m2eclipse
configuration, this will break in Eclipse again. Lame.
2011-03-23 22:09:29 +00:00
1a2967b31f
yohoho no longer cares if depot is built with 1.6, so build with that since we're using 1.6's Connection.createArrayOf in PostgreSQL4Builder. Sneak a ooo-buildification in with the compiler version bump.
2011-03-23 20:42:00 +00:00
a0999fb8a4
[maven-release-plugin] prepare for next development iteration
2011-01-07 22:31:59 +00:00
e0a55fc3a8
[maven-release-plugin] prepare release depot-1.2
2011-01-07 22:31:45 +00:00
16919c056b
Use the latest stable samskivert: 1.2.
2011-01-07 22:27:35 +00:00
7d99928d7c
Maven makes using version ranges too annoying by constantly checking for new
...
versions with the repository.
Why, Maven, do you not offer an option to not go searching numerous sources on
the Internet every time I run a build? (And then timing out when some of those
sources are behind firewalls and I'm not running vpn at the moment.) Indeed,
why would that not be the default?
2010-12-18 17:30:57 +00:00
63ac28fcef
Do so in a syntactically correct manner as well.
2010-12-09 17:19:40 +00:00
eeb8f5eeb7
Allow newer versions of our samskivert and guava dependencies.
2010-12-09 17:19:12 +00:00
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
Ray Greenwell