Grouper Users - Open Discussion List

[Jeffrey Williams <>]

I'm running a loader using  tier/grouper:appliance, which I believe has PSPNG's *.class, *.java files installed in the same location (/opt/grouper/2.3.0/grouper.apiBinary-2.3.0/conf/edu/internet2/middleware/grouper/pspng/) as tier/grouper:master.

I'm trying to patch PSPNG inside the container and seem to be hitting a installDir conflict with API.

Here's the gist of my grouper.installer.properties file:

download.server.url = "/opt/grouper/2.3.0/tarballs

grouper.version = 2.3.0

grouperInstaller.autorun.appToUpgrade = api

grouperInstaller.autorun.grouperWhereInstalled = /opt/grouper/2.3.0/grouper.apiBinary-2.3.0

grouperInstaller.autorun.installDirectory = /opt/grouper/2.3.0/

grouperInstaller.autorun.useDefaultsAsMuchAsAvailable = true

grouperInstaller.default.appToUpgrade = pspng

grouperInstaller.default.existingInstalledDirectory = /opt/grouper/2.3.0/grouper.apiBinary

grouperInstaller.default.installDirectory = /opt/grouper/2.3.0/grouper.apiBinary-2.3.0

grouperInstaller.default.installOrUpgrade = patch

ran using: java -cp .:grouperInstaller.jar edu.internet2.middleware.grouperInstaller.GrouperInstaller

...and it tries to patch the API as the config hints at.   Same result if we run it interactively.  This is with the latest 2.3 grouperInstaller.jar.

I feel like one or both of the install directories is incorrect, but I don't have a counterexample that makes sense.  What could I be missing here?

--

Jeffrey Williams 

Identity Engineer
Identity & Access Services
https://its.uncg.edu