-
Notifications
You must be signed in to change notification settings - Fork 2
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
Windows: Metafix-Runner sometimes complains that file path of runner is too long #371
Comments
Installed version of Metafacture Core works:
Release distribution seems to work too:
|
From Fix repo:
but:
and
Have some kind of error, at first the seem to work and output the flux commands. But the build results in an error:
|
So do the batch scripts. Flux exits with an error code when no file is given. |
The difference between Metafix and Core is that the latter provides a bespoke batch script, while the former generates a generic one via Gradle's Application plugin. This error may theoretically hit both in the same way, but the Metafix script already contains a pretty long In addition to that, the Metafix runner doesn't support the same configuration options as the Core runner (namely, Both differences may hopefully become moot once Metafix gets integrated into Core. |
Tested with the metafix-runner.bat in Windows: set the classpath with wildcard |
The generated start script for Windows consists of a huge classpath. This classpath was too long, resulting in an error when executing the start script. Using wildcard to include libraries shortens the classpath so that now error occurs when executing the start script.
@maipet right, if you manipulate |
Also here - a big thx to all who have contributed here to fix this issue! |
We have not found a solution yet.
Same for:
The following works:
Workaround is to extract the metafix-runner without version in the download folder, the desktop or in the homefolder (maybe then with version would work too)
The text was updated successfully, but these errors were encountered: