Stephen Connolly <[email protected]> wrote on 12/01/2014 12:14:23 PM:
> It all depends how you use them. > > There are some use cases where they make sense. > > Usually these use cases include aggressive shading of the dependencies you > are bundling. > > Some cases where it can be useful: > > * If you are interfacing with a non-maven aware build tool chain - here the > uberjar makes life easier for that toolchain as they only have one > dependency to specify... the gotcha is if you make this the only way for > people to consume then the POM aware build toolchains will end up with > duplicate class hell > > * If you are creating an "App" or CLI utility jar file where people just > run the file directly then it can be easier to give them a single jar > file... but anyone else embedding your "app" will curse you if you only > provide the uberjar Thanks to all who replied; this was the information I was looking for.
