-
Notifications
You must be signed in to change notification settings - Fork 350
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
Error when using an external kit #2090
Comments
maybe related to the fast-jar thing we have introduced ? it looks like the classpath is messed up |
Oh, right! I didn't notice that this got merged yesterday and we switched to runtime 1.7.0-SNAPSHOT. In case of external kit, the individual entries of the classpath are not expected to be be present on the kit. cc: @jamesnetherton |
I can try to take a look tomorrow or Friday. |
Strange that it did not happen before merging the global builder. I think it's not related to the global builder per se, it's more likely a problem with using external kits.
The test is pretty easy:
--kit=external --name=different-one
It fails (today):
Any idea @lburgazzoli ?
The text was updated successfully, but these errors were encountered: