Fix onejar problem with AWS SDK

[paulhoule]

I am having this problem

https://github.com/aws/aws-sdk-java/issues/185

it looks like I may need to create a custom version of the one-jar plugin to use the AWS SDK. I kinda have to use onejar instead of the maven-assembly-plugin because with the latter Spring can't always find the XSD files it needs to boot. (It looks for them via http which works sporadically)

[paulhoule]

Found out from reading the thread above that this problem was introduced in aws sdk version 1.6.7 so it can be avoided by rollback to 1.6.6.

Tomorrow I need to get on the case of the onejar people and either get them to get a new release out and into the central repository or I fork the onejar plugin and put it in the central repository myself.

[paulhoule]

I have better things to do but can't quite do them today so I took a look at the backlog.

I wanted to cause some trouble with the maven plugin people but then on the thread above somebody told me the problem was not with the maven plugin

https://github.com/jolira/onejar-maven-plugin/blob/master/src/main/java/org/dstovall/OneJarMojo.java

but really with

http://one-jar.sourceforge.net/

so "what is to be done" (sorry Lenin) is to fix one-jar and then hack the plugin to use the new onejar so we have to start with the original one-jar and then patch or configure the maven plugin to use the new one.