Not sure I follow, concretely the reason it is no more mainstream is we are too deeply integrated with tomcat and the fact you can use the drop in way with tomcat (random versions for the samples) 8.5.11 doesn't mean you can use it with tomcat 8.5.12 forcing you to migrate both anyway.
If you only care about maintaining "jars" you can still use /opt/tomcat/<version>/lib /opt/tomee/<version>/lib and dont need the war itself but just its lib dir. The trick there is to just configure accordingly common.loder in conf/catalina.properties. Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory <https://javaeefactory-rmannibucau.rhcloud.com> 2017-03-23 20:36 GMT+01:00 HWinMT <[email protected]>: > I'm guessing that when there is a security issue discovered in a version of > Tomcat that the TomEE download is updated fairly promptly? It is the reason > I keep up with the war file for other 3rd party apps I maintain that come > with their own Tomcat that is not maintained and we fail a PCI scan and I > need to move it. > > Thanks. > > > > -- > View this message in context: http://tomee-openejb.979440. > n4.nabble.com/TomEE-7-0-3-WebProfile-Drop-In-War-tp4681368p4681370.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
