-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial suport for Tomact9 - Tc9.x #43
base: trunk
Are you sure you want to change the base?
Conversation
* From tomcat8-maven-plugin to tomcat9-maven-plugin * From tomcat8-war-runner to tomcat9-war-runner
This was causing the artefact build to fail as it ignored the \ escapes.
Setup the webapp like it would be normally and let Tomcat handle everything. There is one hack to work around a hack in Weld’s WebAppBeanArchiveScanner, which explicitly looks for WEB-INF/classes.
Tomcat is headless. It’s a pain on macOS if this isn’t set.
This fixes a bug where conflicting files in jars would be loaded instead of the same file in the module’s build directory.
Improvements to Tomcat 9 support
Initial support for Tomact9 - tc9.x
Exit if Tomcat fails to start
Exit if Tomcat fails to start
Some aggregator or IT modules do not have any own class files but only tests. This did lead to a startup failure in later tc7 versions Credits to struberg
There was some interest to revive the component. So this is a starting point, thanks.
|
@rmaucher what about incorporate those changes, tag then for use only up to jdk11 and Java EE 8, release as is? |
I could be talked into hitting the merge button. However, there is no way I'll +1 this for a release, it needs a "full" rewrite. |
This contribution is based on work done by @poolborges, @karlvr and @struberg.
I've just compiled locally!