Occasional Thoughts

For quite a while the Ubuntu subversion package suffer from bad user certificates that do not follow the standards strictly. In case you have to authenticate with such a certificate subversion will return such an error message:

The root of this problem is that the Ubuntu packages link against libneon-gnutls, which handles certificates in a stricter way than libneon. A easy workaround in the past was to simply replace a replace the library link of libneon-gnutls to point to libneon:

sudo mv /usr/lib/libneon-gnutls.so.27 /usr/lib/libneon-gnutls.so.27.old
sudo ln -s /usr/lib/libneon.so.27 /usr/lib/libneon-gnutls.so.27

However once you do this in Ubuntu 12.04 Precise Pangolin you will get a another error message instead:

OPTIONS of <url>': SSL handshake failed: SSL disabled due to library version mismatch (<url>)

When reading through ActionScript code I frequently see two ActionScript mistakes that are likely to cause runtime misbehavior and confusions. Sometimes thing do not appear at first glance what you might think at the beginning. However both ActionScript bumps can easily be driven around. 

I'm glad to be able to depricate my own post Groovy++-with-Maven a couple of weeks ago. The Groovy++ team has already taken action and provides the groovvypp libraries in a commonly accessible repository. They also provide a preliminary version of the gmaven plugin that supports statically linked Groovy.

For details see Using-groovypp-with-maven  and also the related update Using-groovypp-with-maven (update).

Please see my update Official-Maven-support-for-Groovypp.

If you are already a fan of Groovy you probably will also be a fan of the rising star Groovy++. Even people that dislike the dynamic magic of Groovy must agree, that this is cool stuff, mixing the power of Groovy with the safety and performance of classical Java. Since Groovy++ is still brand new it lacks of any Maven support today. In the following I will show how you can tweak the GMaven plugin for using the Groovy++ extensions.

Please be aware that this is just a very quick work to get it running and might not be stable. For example I did not verify all the necessary dependencies. So further work has to be done.

Spring Actionscript is a great library - no question. It makes it much easier to mock Cairngorm service delegates and rewire them for testing with FlexUnit. Testing the full event/command/delegate workflow is pretty easy.

However today I had quite some "fun" with the Maven artifact and it's transitive dependencies in combination with Maven 2.2.1. Spring Actionscript has some dependencies to these artifacts:

• as3commons-lang
• as3commons-logging
• as3commons-reflect