One-Jar-Expandmight help here as well, but I think not requiring runtime expansion of the fat jar is nicer.
The purpose of this would be to support libraries that cannot handle nested JARs such as (embedded) Jetty. The problem with e.g. Jetty is that it's not able to find .jsp files from within nested JARs just always reporting a 404.
I think adding a setting to enable the "splatting" of the main jar directly into the final jar would not be a difficult task but would provide a clean solution for the aforementioned problem.
If, on the other hand, OneJar already supports this, it would be nice to be able to pass the respective setting through to it via sbt-onejar settings.
One-Jar-Expand
might help here as well, but I think not requiring runtime expansion of the fat jar is nicer.The purpose of this would be to support libraries that cannot handle nested JARs such as (embedded) Jetty. The problem with e.g. Jetty is that it's not able to find
.jsp
files from within nested JARs just always reporting a 404.I think adding a setting to enable the "splatting" of the main jar directly into the final jar would not be a difficult task but would provide a clean solution for the aforementioned problem.
If, on the other hand, OneJar already supports this, it would be nice to be able to pass the respective setting through to it via sbt-onejar settings.