So I did what we, engineers always do in this situation: run your own. Good news, it took just over an hour and I ended with a single very small file. It can only variable substitution but that was enough for me. Here it is:
The best part: it has no dependencies so you can just copy file into your project and template away.
Of course you can Maven just as well:
Microframeworks are popular these days. This thing doesn’t even qualify to be called micro- or even nano- but I got a feeling I am going to use Bristle template in the future…
Finally found some time to publish BuildNumber — a Maven plugin and Ant task to embed SVN build number into your application during build. Great for tracking what version is deployed where.
ProGuard is a great tool for packaging your Java Applet or application. We use it mainly to package a program and bunch of dependencies into small .jar file. It works great on Linux and Windows but on my Mac it would end up with messages like:
[proguard] Reading library jar [/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/jsse.jar]
[proguard] Error: Can't read [proguard.ClassPathEntry@50502819] (No such file or directory)
With some help from the Eric Lafortune, the ProGuard author, the solution was to put a link to the missing file to its “regular” place in Java libraries:
sudo ln -s ../../Classes/classes.jar rt.jar
sudo ln -s ../../Classes/jsse.jar .
The downside is that you should do some manual stuff on each Mac you want to build on. If somebody has better solution I would love to know about it.
In military training long time ago, I and my fellow students were forced to do a lot of things that were illogical, redundant or outright stupid. Sometimes our only explanation was “so the life wouldn’t seem sweet like honey”. It kind of made sense to make life intentionally hard in the army — it was supposed to be training after all. It seems that the Apple in this case was following the same logic: let’s spread runtime libraries all over the system so that the engineer’s life wouldn’t seem too sweet like honey. Anybody got better explanation, please let me know.
http://www.cacert.org/ is a great way to easily create free SSL certificates for development work. In order to successfully connect from Java program using SSL to a server carrying a certificate issued by CACert you need to “bless” the certiticate, or make it trusted by your your local Java JRE installation.
Let’s first make sure we are in the lib/security subdirectory of the currently running JRE:
> cd $JDK_HOME\jre\lib\security
Then, download the certificate file to your local computer:
$JDK_HOME\jre\lib\security> wget http://www.cacert.org/certs/root.crt
--2010-03-16 09:24:40-- http://www.cacert.org/certs/root.crt
Resolving www.cacert.org... 126.96.36.199
Connecting to www.cacert.org|188.8.131.52|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2569 (2.5K) [application/x-x509-ca-cert]
Saving to: `root.crt'
100%[======================================>] 2,569 15.4K/s in 0.2s
2010-03-16 09:24:41 (15.4 KB/s) - `root.crt' saved [2569/2569]
Now let’s import the certificate into the JRE keystore (note the password of the default JRE keystore — it’s different on different platforms):
$JDK_HOME\jre\lib\security> keytool -import -keystore cacerts
-storepass changeit -alias cacert-root1 -trustcacerts -file root.crt
Owner: EMAILADDRESSfirstname.lastname@example.org, CN=CA Cert Signing Authority, OU=http://www.cacert.org, O=Root CA
Issuer: EMAILADDRESSemail@example.com, CN=CA Cert Signing Authority, OU=http:/
/www.cacert.org, O=Root CA
Serial number: 0
Valid from: Sun Mar 30 04:29:49 PST 2003 until: Tue Mar 29 05:29:49 PDT 2033
Trust this certificate? [no]: yes
Certificate was added to keystore
Now you are ready to start sending Java SSL requests to your server.