I’d understand if you had this issue against 5.1 snapshots, in which case 
you just need to force-update snapshots [and file issues if you still see 
it]. Always compare git SHAs with the repo if you’re unsure. Snapshots may 
be updated multiple times a day so don’t just rely dates.



But if you have this issue against a 5.0.x, that means you’re doing 
something in the overlay that should not be there. You want to make sure 
there is nothing in your overlay that references master or 5.1 SNAPSHOTs 
basically.



--Misagh



From: [email protected] [mailto:[email protected]] On Behalf Of mrcasa 
bengaluru
Sent: Monday, February 6, 2017 9:40 PM
To: [email protected]
Subject: Re: [cas-user] Error starting CAS 5.x (conflicting module versions, 
Groovy)



I have exactly the same issue with the recent 5.1.0-RC2-SNAPSHOT.

I use gradlew bundled 3.2.1 version with CAS while I use 3.3 with another 
private project. Not sure if this is related. At the this time. although the 
code compiles, it fails at runtime with the same message as above.

Caused by: groovy.lang.GroovyRuntimeException: Conflicting module versions. 
Module [groovy-jsr223 is loaded in version 2.4.7 and you are trying to load 
version 2.4.8
    at 
org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl$DefaultModuleListener.onModule(MetaClassRegistryImpl.java:512)
 
~[groovy-2.4.7.jar!/:2.4.7]



On Tue, Feb 7, 2017 at 1:49 AM, Misagh Moayyed <[email protected] 
<mailto:[email protected]> > wrote:

An exact version would be helpful.



--Misagh



From: [email protected] <mailto:[email protected]> 
[mailto:[email protected] <mailto:[email protected]> ] On Behalf Of Paul 
Chauvet
Sent: Monday, February 6, 2017 9:14 PM
To: [email protected] <mailto:[email protected]>
Subject: [cas-user] Error starting CAS 5.x (conflicting module versions, 
Groovy)



Hello all,



We’re in the process of rolling out CAS 5.x.  Things were deploying fine in 
our test environment, and we moved on to UI customizations, but sometime 
recently when building from source it has caused an error which prevents 
Tomcat from deploying the .war file.



I’ve attached the Catalina log export, but the root issue appears to be in 
this line:

Caused by: groovy.lang.GroovyRuntimeException: Conflicting module versions. 
Module [groovy-jsr223 is loaded in version 2.4.8 and you are trying to load 
version 2.4.7



The same error happens now on deployment in Tomcat, even for builds that 
worked perfectly fine several weeks ago.  We are using Gradle for building 
the CAS .war.  Our CAS-5 build was made for us by Unicon, and all we were 
working on is some UI changes.  I thought it might have been those UI 
changes, but even the exact version provided for us by Unicon for v5 doesn’t 
work anymore.



If other info is needed (build.gradle files or something else), please let 
me know.  Any thoughts or ideas on this would be greatly appreciated!



Paul Chauvet

Information Security Officer

State University of New York at New Paltz

845-257-3828

[email protected] <mailto:[email protected]>





-- 
- CAS gitter chatroom: https://gitter.im/apereo/cas
- CAS mailing list guidelines: 
https://apereo.github.io/cas/Mailing-Lists.html
- CAS documentation website: https://apereo.github.io/cas
- CAS project website: https://github.com/apereo/cas
--- 
You received this message because you are subscribed to the Google Groups 
"CAS Community" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to [email protected] 
<mailto:[email protected]> .
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/CY4PR2001MB1062B1AB7814984B01D9BBDEA7400%40CY4PR2001MB1062.namprd20.prod.outlook.com
 
<https://groups.google.com/a/apereo.org/d/msgid/cas-user/CY4PR2001MB1062B1AB7814984B01D9BBDEA7400%40CY4PR2001MB1062.namprd20.prod.outlook.com?utm_medium=email&utm_source=footer>
 
.

-- 
- CAS gitter chatroom: https://gitter.im/apereo/cas
- CAS mailing list guidelines: 
https://apereo.github.io/cas/Mailing-Lists.html
- CAS documentation website: https://apereo.github.io/cas
- CAS project website: https://github.com/apereo/cas
--- 
You received this message because you are subscribed to the Google Groups 
"CAS Community" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to [email protected] 
<mailto:[email protected]> .

To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/002901d280b6%245fa92710%241efb7530%24%40unicon.net
 
<https://groups.google.com/a/apereo.org/d/msgid/cas-user/002901d280b6%245fa92710%241efb7530%24%40unicon.net?utm_medium=email&utm_source=footer>
 
.



-- 
- CAS gitter chatroom: https://gitter.im/apereo/cas
- CAS mailing list guidelines: 
https://apereo.github.io/cas/Mailing-Lists.html
- CAS documentation website: https://apereo.github.io/cas
- CAS project website: https://github.com/apereo/cas
--- 
You received this message because you are subscribed to the Google Groups 
"CAS Community" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to [email protected] 
<mailto:[email protected]> .
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/CALpZ%2BOQ_O7_Yv%2BZZH2NspMQpyNt%3D2siXjiuYcvxF9BZT%3DaszxQ%40mail.gmail.com
 
<https://groups.google.com/a/apereo.org/d/msgid/cas-user/CALpZ%2BOQ_O7_Yv%2BZZH2NspMQpyNt%3D2siXjiuYcvxF9BZT%3DaszxQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
 
.

-- 
- CAS gitter chatroom: https://gitter.im/apereo/cas
- CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html
- CAS documentation website: https://apereo.github.io/cas
- CAS project website: https://github.com/apereo/cas
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/005601d280ba%24e12841f0%24a378c5d0%24%40unicon.net.

Reply via email to