grouper-users - [grouper-users] RE: Patching the UI
Subject: Grouper Users - Open Discussion List
- From: "Hyzer, Chris" <>
- To: Sean Mason <>, "" <>
- Subject: [grouper-users] RE: Patching the UI
- Date: Wed, 9 Nov 2016 19:14:43 +0000
- Accept-language: en-US
- Authentication-results: spf=none (sender IP is ) ;
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
Sorry, patches only work on the built UI. If you rebuild it you need to repatch it. The way patching works its not conducive to patching the pre-built UI.
On Behalf Of Sean Mason
I’ve been experimenting with patching, mostly to get up-to-date with the PSPNG progress, which has worked well.
I’m now attempting to patch the UI, and have run into some difficulties.
It appears the grouperInstaller wants the path of the built “UI”, rather than the pre-built “UI”. This may not be an issue for a service that is in production and stable, but I’m not sure how to work this while I am experimenting and developing pre-production, where I sometimes rebuild the UI.
If I patch the UI (which appears to also patch the embedded API files) will patch work not all be un-done when I re-build the UI experimenting with some other settings? Similarly, if I patch the API, then build the UI, the grouperInstaller seems to run into trouble where it sees changed files, but wants to overwrite them and chooses the safe path.
Is there a way I’ve overlooked to patch the UI source, so patched changes are incorporated with every UI build? Am I using the wrong approach? How have others worked through this?
- [grouper-users] Patching the UI, Sean Mason, 11/09/2016
- [grouper-users] RE: Patching the UI, Hyzer, Chris, 11/09/2016
Archive powered by MHonArc 2.6.19.