If you deploy to an external container like Tomcat, you can instead of using the war, explode it into the webapp directory. Wars and jars are just zip files. Or let Tomcat explode it for you the first time, stop Tomcat, then delete war. You can edit content without having to rebuild.
I think that the HTML / CSS can be updated live enough if you use the method above. If nothing else it saves you the build step even if you have to bounce Tomcat. On Thu, 2020-04-09 at 12:16 -0700, Yan Zhou wrote: > Hi there, > > CAS5.3.x overlay. It looks like we have to build it into a WAR file > first, then either run it as an executable WAR or deploy to external > container. > > There is also a way to run CAS as an executable WAR via Spring Boot's > maven plugin, but that requires NO change to CAS dependencies, which > is not my use case (I have made a lot changes in CAS dependencies). > > Is there some way that I can do a hot swap, e.g., see the static > HTML/CSS change with the refresh of a browser? > > Even in standalone mode, it takes several minutes for CAS 5.3 to > startup. > Thanks, > Yan > -- - 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/bb3e28f3ade53f5c94ca10aea400869a577a8e00.camel%40ndsu.edu.
