-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ClassNotFoundException when starting appbundler-based apps #45
Comments
This was referenced Jun 1, 2019
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 |
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 f5603fb, 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 f5603fb...master has introduced a regression.Please let me know if I can provide any other information or further explanation.
The text was updated successfully, but these errors were encountered: