Skip to content
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

Open
wants to merge 22 commits into
base: trunk
Choose a base branch
from

Conversation

gilbertoca
Copy link

This contribution is based on work done by @poolborges, @karlvr and @struberg.
I've just compiled locally!

poolborges and others added 21 commits October 12, 2018 16:44
* 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
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
@rmaucher
Copy link

There was some interest to revive the component. So this is a starting point, thanks.
I would suggest:

  • Drop 7 and 8 support since they are EOL.
  • Test with a more recent Tomcat 9 (34 is from 5 years ago or something).
  • See if this really needs a set of classes per major version. Overall the differences should be minimal and this would avoid having something for 10.1 and 11. I would say a new set of classes should be added only if there is some breaking change.

@gilbertoca
Copy link
Author

gilbertoca commented Oct 17, 2024

@rmaucher what about incorporate those changes, tag then for use only up to jdk11 and Java EE 8, release as is?
So, after this, I will try to create a PR taking into account your third advise and change the repo to jdk11/17 and Jakarta 10?
ping @poolborges, @karlvr and @struberg.

@rmaucher
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants