Open joewiz opened 5 years ago
indeed the order of the parameters is not OK ; args 33/34 are redundant and should be removed
actually params 35-68 should not be there. these are double
@dizzzz Strange indeed. Do you think the duplicate parameters could be the cause of the ClassNotFoundException
?
yes, I am sure about that
The doubled params are caused by the changes in the "Remove unnecessary global static state" commit, dd16fd6 on Bitbucket.
After replacing an old build of appbundler used by eXist-db with a new build of appbundler from this repository's master branch, eXist now fails to start via its appbundler-based app. The console reports a ClassNotFoundException. The full console output is below.
Steps to reproduce:
git clone https://github.com/eXist-db/exist.git
cd exist
git checkout develop-4.x.x
./build.sh app
dist/eXist-db.app/Contents/MacOS/eXist-JavaAppLauncher
Both appbundler and eXist were built with Oracle JDK 8.
This error did not affect builds of appbundler using my PR 55 from the previous bitbucket repository, and in fact, if you reset HEAD to f5603fb3a65d39b02342ff551a358813e6178734, run
ant clean package
and copy the resulting jar into eXist and rebuild eXist's app, eXist starts up completely normally without this ClassNotFoundException error. This suggests that some change in https://github.com/TheInfiniteKind/appbundler/compare/f5603fb3a65d39b02342ff551a358813e6178734...master has introduced a regression.Please let me know if I can provide any other information or further explanation.