I have some experience using onejar archives for deployment. It mostly worked but we had some issues. it doesn't work well with AOP - in our case we had issues using it with AppDynamics and Kamon. Also, it makes it hard to access configuration files since they are wrapped twice in jars. I guess that it would be easier to put the library jars on the path. Moreover, most projects now migrate to docker base deployment which don't need uberjars.
On Thu, Dec 8, 2016 at 5:15 PM Evan Hughes <wisebald...@apache.org> wrote: > Hey all, > > Wanting to grab the oppions of the community on whether we stick to an > uberjar/shadowjar/box of magic or extend our script to put the dependencies > on the path and then run the wave jar. > > This shouldn't change any functionality but since we are cleaning up some > of the build logic I thought we should discuss it. An example of non uber > jarring can be seen with intellij's idea ide just fyi. > > Curious to see what the community thinks. > > ~ Evan >
