Grouper Developers Forum

["Redman, Chad" <>]

Thanks. I also had similar notes in 
https://bugs.internet2.edu/jira/browse/GRP-2046 :


27/Feb/19 9:07 AM

My quick testing, needed these to get gsh to work:

(new) javax.xml.bind:jaxb-api:2.3.1
(new) com.sun.xml.bind:jaxb-impl:2.3.2
(new) com.sun.xml.bind:jaxb-core:2.3.0.1
(upgrade) org.codehaus.groovy:groovy-all:2.5.6:pom
(upgrade) org.javassist:javassist:3.24.1-GA

There is no longer a groovy-all jar. It's split up into 21 different jars, 
and we probably don't need all of them (e.g. the test jars).

This was enough to get gsh working, but I haven't tested the UI yet.

The grouperClient build deprecation warnings are about the same as before, so 
the com.misc.Unsafe calls haven't gone away, despite the threats.



-Chad


-----Original Message-----
From:  
[] On Behalf Of Jim Fox
Sent: Tuesday, April 23, 2019 12:56 PM
To: 
Subject: [grouper-dev] javassist with java 11


( In case you don't already know. )

I installed our group service on a google cloud compute engine that ended 
up with openjdk version "11.0.2" of java.  The grouper API could not 
connect to my database (postgres 9) until I replaced 
'javassist-3.22.0-GA.jar' with 'javassist-3.25.0-GA.jar'.

See

https://stackoverflow.com/questions/52913597/springboot-org-hibernate-mappingexception-could-not-get-constructor-for-org-hi

don't know if it's exactly the same thing, but the jar upgrade allowed 
grouper to assess the database.

Jim