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
{{ message }}
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.
I'd like to propose making server-version a required parameter to 'ml new' and 'ml init'. The way that Roxy does bootstrapping didn't change from ML5 to ML6 so users didn't have to set server-version to 6 even if they were using ML6.
However, with ML7 being released soon and a substantial percentage of the user base likely still at ML6 (or even ML5) for a while, it might be a nice usability enhancement to require people to provide a --server-version command line parameter when running 'ml new' or 'ml init', since there is no way for us to query for the ML server version and provide a helpful error if the server-version in the properties file is incorrect.
The text was updated successfully, but these errors were encountered:
I'd like to propose making server-version a required parameter to 'ml new' and 'ml init'. The way that Roxy does bootstrapping didn't change from ML5 to ML6 so users didn't have to set server-version to 6 even if they were using ML6.
However, with ML7 being released soon and a substantial percentage of the user base likely still at ML6 (or even ML5) for a while, it might be a nice usability enhancement to require people to provide a --server-version command line parameter when running 'ml new' or 'ml init', since there is no way for us to query for the ML server version and provide a helpful error if the server-version in the properties file is incorrect.
The text was updated successfully, but these errors were encountered: