> - When maven-shade-plugin went out, I thought it was designed to be a > first-choice replacement for the maven-assembly-plugin/jar-with-dependencies > scenario/use case. > - Maven-assembly-plugin can do a lot more than just packaging an > uber-jar, that's why he remains useful. But when just wanting to package an > uber-jar, the recommended/maven way is using maven-shade-plugin.
That's not my take. Speaking for myself, shade is good when you want to not only create a jar-with-dependencies but you also want to "shade" some or all of the 3rd party classes/artifacts (move them under your own class heirarchy eg com.sun => net.wfay.com.sun). Assembly is good when you simply want jar-with-deps bundles or need to construct other random packages types with specific layouts for installation or deployment into particular environments. If you don't need/want to shade any of the artifacts, there is no need to use m-shade-p, and you should be using m-assembly-p (IMO). I'm not a Maven Developer so feel free to ignore this if/when one of them comes along and says otherwise... Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
