You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We now have a great list of installation options available.
Some of the options are also available to the mpm input files as well, such as destinationfolder=xxx and --destination.
It would be great to have the options to more flags such as --doc, --no-jre, --source and --no-gpu.
Currently, these cannot be set if using mpm-input files.
Maintaining installation in a configuration as code manner would bring more flexibility and readability.
The text was updated successfully, but these errors were encountered:
Expanding the supported list of options in the input file is on our long-term roadmap. In the meantime, if your workflow requires these options, please use the non-input file workflow.
Thanks for the insight on having this on the roadmap later. I am looking forward to it.
I believe workarounds can be used until this has been implemented. Workarouned could be a mix of the installer input file and a wrapper script (myMPM.sh) that could parse the input file and append the flags.
We now have a great list of installation options available.
Some of the options are also available to the mpm input files as well, such as
destinationfolder=xxx
and--destination
.It would be great to have the options to more flags such as
--doc
,--no-jre
,--source
and--no-gpu
.Currently, these cannot be set if using mpm-input files.
Maintaining installation in a configuration as code manner would bring more flexibility and readability.
The text was updated successfully, but these errors were encountered: