FWIW, I've now fixed a couple more things and revamped the build in the above fork to use gradle and published to maven central. Simon, you're totally invited to join my repo a maintainer, and we can move back to the one-jar name if you are willing to release it under a pure MIT or Apache 2.0 license rather than your customized license. The fact you trademarked One-JAR and included that trademark in the license notice that must be reproduced is awkward. Since you hold the copyright for the original,...
No support for Multi-Release Jars
This of course is in no way official, but I had to fix another problem I ran into,...
Bad link for maven usage
Oh there absolutely is value in maintaining this in my opinion. (and possibly this...
Oh there absolutely is value in maintaining this in my opinion. (and possibly this...
Ok, patches don't get much simpler than this :) Hope you can get it in there soon....
Ok, patches don't get much simpler than this :) Hope you can get it in there soon....
I guess that's only fair :) it is open source. Not sure if can commit myself to anything...
This one is really really irritating me. One of my most common use cases for one-jar...
This one is really really irritating me. One of my most common use cases for one-jar...
Seems this is likely to be related to my recently reported issue: https://sourceforge.net/p/one-jar/bugs/75/...
oops forgot to mention the version of onejar in use... buildscript { repositories...
oops forgot to mention the version of onejar in use... buildscript { repositories...
oops forgot to mention the version of onejar in use... buildscript { repositories...
oops forgot to mention the version of onejar in use... buildscript { repositories...
More classloading issues