Does anyone have some insight as to why the uberjar functionality of the Classworlds project hasn't gotten much support with Maven 2?
http://classworlds.codehaus.org/uberjar.html It seems like a really useful setup as it preserves some of the information that the assembly plugin strips, such as signed jars, the individual manifests as well as the original organization of class files and resources. Was there something inherently wrong with the classworlds implementation that a Maven 2 plugin was never created? I was considering going down the path of creating a Maven 2 plugin to create classworld uberjars but I wanted to throw the question out there in case someone already knew the 'gotchas' surrounding it. -- View this message in context: http://www.nabble.com/%22Classworlds-uberjar%22-vs.-%22assembly-jar-with-dependencies%22-tp18786168p18786168.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
