It would be great if the Grouper Installer's automated install config/properties file could be used to limit the release number of patches applied to a given installation. I could see this being multiple properties, one for each grouper component.

There is a potential mis-match of the properties limiting the API not coinciding with the limiting placed on the UI component.

I would argue that the installer should just do its normal thing and stop when the appropriate patch limit is hit. If the UI needed a higher API patch number then it should just gracefully skip the UI patch just like it does today if a dependency is not applied.