Grouper Users - Open Discussion List

["Hyzer, Chris" <>]

I updated this wiki:

 

https://spaces.internet2.edu/display/Grouper/Grouper+Installer

 

Does it help?  Also, if you are rebuilding the ui, do a clean build, and then it should patch from scratch and not have conflicts.  But if you want to force install that’s fine too.

 

Using a config file

You can put a grouper.installer.properties in the same directory as the grouperInstaller.jar to control various aspects.  See the grouper.installer.example.properties for whats possible to put in there

At a minimum you need this in the config file (version and url)

# this should be before the version number

download.server.url = "http://software.internet2.edu/grouper

 

# default version to install

grouper.version = 2.3.0

To run the installer, use this command

[appadmin@i2midev6 patchesAuto]$ ls

grouperInstaller.jar

grouper.installer.properties

[appadmin@i2midev6 patchesAuto]$ java -cp .:grouperInstaller.jar edu.internet2.middleware.grouperInstaller.GrouperInstaller

 

You can also set this property which as you run the installer will let you know the property to set for each prompt

# this should be before the version number

download.server.url = "http://software.internet2.edu/grouper

 

# default version to install

grouper.version = 2.3.0

 

# print out autorun keys in prompts so you can easily see how to configure the autorun

grouperInstaller.print.autorunKeys = false

Then once you see which properties to set, put them all in the grouper.installer.properties and run, and you can use defaults to make it not interactive

 

# this should be before the version number

download.server.url = "http://software.internet2.edu/grouper

 

# default version to install

grouper.version = 2.3.0

 

#### set this to true to try to use defaults for everything.  Only things without default values will need to be set

grouperInstaller.autorun.useDefaultsAsMuchAsAvailable = true

 

 

 

-----Original Message-----
From: [mailto:] On Behalf Of
Sent: Tuesday, May 15, 2018 1:50 PM
To:
Subject: [grouper-users] grouper.installer.properties options

 

I have been building a Grouper Demo that uses grouper.ui-2.3.0. I find myself

rebuilding the ui for small changes very often.

When I rebuild it is necessary to patch the ui again for pspng and loader

settings my  demo uses. When patching the ui it needs to patch the api first,

but when patching the api that has already been patched I get the prompt often

that classes already exist, and I have to tell it to force install those

classes, which the default answer is false. If I do not force install the

classes it will not patch the ui completely saying that api patches have not

been done. This requires me to hit 't' hundreds of times every time I

rebuild/patch to force install everything.

I have been studying how to set up a patching script using

grouper.installer.properties, however the only option seems to be setting

grouperInstaller.autorun.useDefaultsAsMuchAsAvailable = true

This would not work unless I could change the default answer. Is there a

property to answer a prompt the same every time, or change the default answer?

Or is there a better way to patch these where I don't have to force install

classes? Because rebuilding/repatching seems like a common usage I assume

there is a better way that I am just not finding in the documentation.