5b4ed4e93a
Preparing for getdown-1.3.3 release.
2014-01-20 09:09:26 -08:00
6c7f13fa36
Preparing for 1.4-SNAPSHOT development.
2014-01-14 21:12:29 -08:00
db210a8ee7
Preparing for getdown-1.3.2 release.
2014-01-14 21:11:00 -08:00
da147c9b99
[maven-release-plugin] prepare for next development iteration
2013-04-09 07:04:06 -07:00
85095f05a9
[maven-release-plugin] prepare release getdown-1.3.1
2013-04-09 07:04:04 -07:00
b2ef1f57ec
[maven-release-plugin] prepare for next development iteration
2013-01-09 13:02:15 -08:00
40e9ab7a82
[maven-release-plugin] prepare release getdown-1.3
2013-01-09 13:02:12 -08:00
4a7d8d3b05
Update our SCM to Git since that's what we use now.
2013-01-09 13:01:25 -08:00
8f3c990d6e
We need to keep some classfile attributes.
...
Otherwise compiling against the resulting jar can be hosed.
2013-01-09 12:57:36 -08:00
f9d056ba8a
Preparing for 1.3-SNAPSHOT development.
2012-12-10 16:21:27 -08:00
bb6e44c927
Preparing for getdown-1.2.5 release.
2012-12-10 16:12:25 -08:00
bfb4b06b30
Bump Proguard to 4.8 to make things work with Java 7.
2012-12-04 16:23:03 -08:00
bb61a43a71
OpenJDK omits plugin.jar. Obtain it from icedtea-web if available.
2012-07-02 17:44:16 +00:00
bbb8e74bab
Preparing for 1.3-SNAPSHOT development.
2012-06-01 22:51:35 +00:00
f67f0a313d
Preparing for getdown-1.2.4 release.
2012-06-01 22:48:35 +00:00
8fec356846
Handle java.home pointing to the JDK the JDK's JRE.
2012-05-01 20:30:34 +00:00
c24abe2c7f
Preparing for 1.3-SNAPSHOT development.
2012-04-04 03:31:04 +00:00
4f5e7049f3
Preparing for getdown-1.2.3 release.
2012-04-04 03:17:05 +00:00
aecd4ea650
Preparing for 1.3-SNAPSHOT development.
2012-03-22 01:22:16 +00:00
12b49f5b53
Preparing for getdown-1.2.2 release.
2012-03-22 01:16:24 +00:00
8d2db15433
Preparing for 1.3-SNAPSHOT development.
2012-03-15 01:26:02 +00:00
8003919d1d
Preparing for getdown-1.2.1 release.
2012-03-15 01:24:10 +00:00
953769b143
Preparing for 1.3-SNAPSHOT development.
2012-02-22 06:24:48 +00:00
2e1ae1a74f
Preparing for getdown-1.2 release
2012-02-22 06:14:08 +00:00
71d3abddf1
Revamped the Maven build to use the Maven Proguard plugin (PITA!) instead of
...
calling out to Ant to do the Proguard build.
Running Ant from within Maven (which then runs Maven from within Ant) no longer
works as of Maven 3.
While I was in here, I changed the build to use the Proguard-ed artifact as the
primary artifact, and changed the POM to reflect that none of the dependencies
are transitive.
2011-09-17 17:39:23 +00:00
40de11fa15
Remove and ignore Eclipse files in favor of letting people generate their own using m2eclipse
2011-06-27 20:52:00 +00:00
b3e650f939
Use the shipped samskivert-1.2, fix proguard jar creation.
2011-02-11 18:07:58 +00:00
04398ed747
Update to the samskivert-1.2 SNAPSHOT to get SwingUtil.setWindowIcons()
2010-12-02 01:24:08 +00:00
a508c9e07a
Go back to the next snapshot revision.
2010-11-19 03:59:00 +00:00
88a950997c
Prepare a stable 1.1 release for the OOO repo.
2010-11-19 03:58:17 +00:00
6f5cc3a7dc
[maven-release-plugin] prepare for next development iteration
2010-11-19 01:11:49 +00:00
51fd4c08f5
[maven-release-plugin] prepare release getdown-1.1
2010-11-19 01:11:37 +00:00
5918b67fb1
Revamped primary build to use Maven Ant tasks. Eliminated Ivy-based build,
...
which was used by Maven, now Maven calls into the primary build to generate its
Proguarded jar file. Retired the Retroweaved jar file after a tremendous amount
of fucking around with Retroweaver. I think it's safe to say that the number of
people showing up with a 1.4 JDK operational in their browser is epsilon close
to zero.
2010-11-18 17:38:43 +00:00
6f1a6ce78d
Sorted out a way to get Maven to reference a local jar file without rendering
...
the pom file hosed for transitive dependencies.
2010-11-18 15:54:42 +00:00
d16fa8aebd
Only require signing when doing a real release.
2010-10-14 22:45:12 +00:00
44754f6d43
Let's call our auxiliary Ant file build-proguard since that is more indicative
...
of its purpose in life.
2010-09-21 06:41:18 +00:00
646dc2bdf0
More javadoc fixes.
2010-09-21 06:17:47 +00:00
31b77bcdbe
GetdownApp is the correct entry-point for the application.
2010-09-21 06:12:33 +00:00
90301057f6
[maven-release-plugin] prepare for next development iteration
2010-09-21 06:01:58 +00:00
bf0470b81a
[maven-release-plugin] prepare release getdown-1.0
2010-09-21 06:01:48 +00:00
95857ec608
Let's
2010-09-21 05:38:24 +00:00
724ee652f1
Praise be to Ivy, which lets me do what I need without tremendous amounts of
...
hair-pulling and ball-ache. We now have Maven call out to an Ivy-based Ant task
to do the Proguard build (with Ivy maintaining a parallel copy of the
dependencies, unfortunately). It's a twisty maze of passages, but it gets the
Proguard build done during the right Maven phase so that all of its magical
building, version number changing, SVN commits, etc. can happen as usual during
the publishing process.
2010-09-21 05:26:00 +00:00
f6a03dd99f
A bastard combination of Maven and Ivy that will hopefully eventually allow us
...
to build and publish Getdown. Everything builds with Maven, but getting
Proguard to work inside Maven is an exercise in gouge-my-eyes-out-now, so I'll
be doing the Proguard bits in a separate Ant script which will use Ivy to
obtain dependencies sanely. This too is rife with PITA, but less so than doing
everything in Maven. Ivy bits don't yet work.
2010-09-21 00:45:35 +00:00
Ray J. Greenwell