Enabling features
-
I see. In the case of this MR, the executable (the
.jar
file) is rebuilt on every app startup. Thus, this would not be overwritten by an update. The relevant commandline parameters are persistent inenv.sh
when updating.I think there are two failure modes after an update: 1) obsolete commandline parameters in
env.sh
or 2).jar
files inproviders/
, which were compatible with the previous version but incompatible with the new version. If you want to allow users to select custom features and install custom providers. I think both these options are essentially unavoidable.Let me know if there is something I can improve. I am looking forward to getting this merged.