Yes, tested on local laptop to debug lib conflicts with wildfly modules
before I deployed to linux wildfly instance.
On Wednesday, February 2, 2022 at 5:02:45 AM UTC-6 Udo Hermann wrote:
> Hi Pablo, thanks for the reply. Did this really work for you?
>
> Pablo Vidaurri schrieb am Dienstag, 1. Februar 2022 um 18:21:41 UTC+1:
>
>> Try the following:
>>
>> gradle.properties, set tomatVersion and appServer to blank:
>> appServer=
>> tomcatVersion=
>>
>> Include this dependency in build.gradle:
>> implementation "org.apereo.cas:cas-server-webapp:${project.'cas.version'}
>>
>> Create src/main/webapp/WEB-INF/jboss-deployment-structure.xml with
>> following contents:
>> <jboss-deployment-structure>
>> <deployment>
>> <dependencies>
>> <module name="jdk.unsupported" />
>> </dependencies>
>> <exclude-subsystems>
>> <subsystem name="jaxrs" />
>> </exclude-subsystems>
>> </deployment>
>> </jboss-deployment-structure>
>>
>> Do a gradlew clean build, then grab the cas.war and deploy to your
>> wildfly instance
>>
>> On Tuesday, February 1, 2022 at 10:19:26 AM UTC-6 Udo Hermann wrote:
>>
>>> Hi, I just have a simple question: has anyone already managed to deploy
>>> the CAS WAR Overlay 6.4.4.2 (vanilla) into a JBoss EAP 7.2 on Windows 10?
>>>
>>> Thx
>>>
>>> Udo
>>>
>>
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
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/524403d3-4a3f-453a-bfd4-b3accfc43897n%40apereo.org.
