Grouper Users - Open Discussion List

[Chris Hyzer <>]

There are pros and cons to both approaches…  Im not saying there is no value in your approach, but with the current strategy you can patch a UI without having to do another build.  Therefore only a very small change will be made to the system which reduces risk in my opinion.  You don’t have to worry about doing a build and overwriting a prior patch or doing something else unintended.  I don’t think one is best, if the current way fits in your deployment model, I think you will have less risk.  If not, then you have to do it the other way J   This isn’t a trivial change, will need to look into it.

 

https://bugs.internet2.edu/jira/browse/GRP-1113

 

Thanks,

Chris

 

From: John Gasper [mailto:]
Sent: Friday, February 20, 2015 2:25 PM
To: Chris Hyzer;
Subject: Re: [grouper-users] patching the UI with grouperInstaller

 

I'd argue that it would be best to do the ui base/home directory. I think most people don't consider the expanded war to be the canonical truth. It also kills the process if a context fragment and unexpanded war is used.

Have you already created a Jira issue to track this? I'll volunteer to do if you haven't.


On 2/20/15 10:37 AM, Chris Hyzer wrote:

Yes, it only currently works against an expanded war directory… people keep asking about this so I guess we should think about adding it at some point…

 

Thanks,

Chris

 

From: [] On Behalf Of John Gasper
Sent: Friday, February 20, 2015 12:41 PM
To:
Subject: [grouper-users] patching the UI with grouperInstaller

 

Hi Chris,

I tried to patch a Grouper UI install with the grouperInstaller today and found that it appears to want to work against the expanded war directory and not the base grouper.ui-2.2.1 directory.

Can you confirm this? Am I missing the option to patch the base directory (and then re-apply `ant war`)?

Thanks,
John

---
John Gasper
IAM Consultant
Unicon, Inc.
PGP/GPG Key: 0xbafee3ef