Big +1. I realize I'm guilty of building the creation of the zip files on top of that process, but after 8 years of the TomEE bundle being available, its time to retire these apps I think.
On Thu, May 23, 2019 at 9:31 AM Jean-Louis Monteiro < jlmonte...@tomitribe.com> wrote: > I'd be in favor of removing. > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com > > > On Thu, May 23, 2019 at 10:28 AM David Blevins <david.blev...@gmail.com> > wrote: > > > We have a bit of unused legacy with regards to the following webapps: > > > > 34M tomee-microprofile-webapp-8.0.0-M3.war > > 58M tomee-plume-webapp-8.0.0-M3.war > > 51M tomee-plus-webapp-8.0.0-M3.war > > 6.6M tomee-webaccess-8.0.0-M3.war > > 32M tomee-webapp-8.0.0-M3.war > > > > From the early days of TomEE we created a "drop-in webapp" version for > > plain Tomcat users. This was largely for convenience to people who may > > have had to use a stock Tomcat in cloud or other environments. The idea > > being they could upgrade their Tomcat to a TomEE by dropping in the war. > > > > In practice, I don't believe anyone actually used it and we do not > heavily > > test this technique. There is a known limitation that if your webapp > > starts before the "tomee" webapp, the integration will have to do a > > separate undeploy/redeploy of your webapp which is clunky. As well the > > magic required to load the tomee webapp's contents into the Tomcat server > > classloader is obtuse and complicates the integration. > > > > We should discuss removing them from TomEE 8.0. > > > > There'd be a bit of work involved, but it would trim a good 181MB from > the > > release process. We have to upload that 181MB twice; once to Nexus and > > once to the Apache Mirror System staging repo. So in the end it reduces > > the upload overhead by 362MB, which is a big deal if you're on a network > > not blazingly fast. > > > > Thoughts? > > > > -- > > David Blevins > > http://twitter.com/dblevins > > http://www.tomitribe.com > > > > >
