Grouper Users - Open Discussion List

["Hyzer, Chris" <>]

Yes, and auto patching should work if you set the force flag in grouper.installer.properties

 

# autorun, Problem installing patch since this patch file: <filename> is not the same as what the patch expects:

# Do you want to force install this patch (t|f)? [f]:

grouperInstaller.autorun.forceInstallPatch = t

 

From: [mailto:] On Behalf Of Redman, Chad
Sent: Wednesday, May 09, 2018 7:55 AM
To: O'Dowd, Josh <>;
Subject: [grouper-users] RE: Best practice for updating dist?

 

Hi Josh,

 

My understanding is that the UI patches are geared for applying to an unpacked war file, or to the dist folder after building the UI. At this point the UI patches don't patch the original source. That would explain what you're seeing, that rebuilding the dist directory simply recreates the app from the pristine source files.

 

-Chad

 

 

From: [] On Behalf Of O'Dowd, Josh
Sent: Tuesday, May 08, 2018 12:22 PM
To:
Subject: [grouper-users] Best practice for updating dist?

 

New to using/building grouper.

 

I have attempted to adhere to the “overlay” configuration strategy, by making property and xml changes outside the “dist” directory, and modifying the $.properties file vs. the $.base.properties files.

 

To build/dist I am running “ant dist” from the ${grouper.home}/grouper.ui-2.3.0 directory and then patching the ui from the ${grouper.home}/grouper.installer-2.3.0 directory.  When prompted for tarball dir, I am specifying ${grouper.home}/tarballs.

 

The problem I am having is that when I run “ant dist” and simply restart tomcat, the previously applied patches are no longer applied, and require patching again.  Is this the recommended way to do this?  Patching seems to be tedious, and ‘auto-patching’ isn’t really applying ALL the patches, so having to run it manually.

 

Thanks.

 

Josh O’Dowd

Software Systems Engineer / Identity Access Management

University of Montana