David,

Thanks for the response.  I did not search back far enough to find these 
threads.

We used this method mainly because we have a completely automated Tomcat that 
we could layer in the TomEE WAR.  We will duplicate the automation, unless 
anyone has other ideas.

Thank you,
Rod.


On 10/10/19, 10:49 PM, "David Blevins" <[email protected]> wrote:

    Nationwide Information Security Warning: This is an external email. Do not 
click on links or open attachments unless you trust the sender.
    
------------------------------------------------------------------------------
    
    Hi Rod!
    
    Here are couple of the past conversations on this part:
    
     - 
https://lists.apache.org/thread.html/e8b0f70bffdc452b5e849bd4d4ebd1dee9801330f633c4eccb6ddde1@<dev.tomee.apache.org>
     - 
https://lists.apache.org/thread.html/7fabe1ca67034a450a70896f4cc645cf7580c53261c64d2b9f124f5f@<dev.tomee.apache.org>
    
    The work to actually remove them hasn't been done yet.  That said I would 
definitely revert to using the download if you possibly can.
    
    Resources is definitely part of the issue, complexity is the other.  
Cutting technical debt that wasn't well tested and appeared to not be used to 
focus resources was part of the goal.
    
    
    -- 
    David Blevins
    http://twitter.com/dblevins
    http://www.tomitribe.com
    
    > On Oct 10, 2019, at 7:04 PM, Jenkins, Rodney J (Rod) 
<[email protected]> wrote:
    > 
    > I have been away for a bit and trying to catch up.  I see that 8.0.0 was 
released.  What I did not see is the WAR only release.
    > 
    > I searched the list and I did not see a discussion about removing this.  
So, I do have a couple questions:
    > 
    > Will the WAR only distribution be supported in the future?
    > We have been using this to build our internal products, should we revert 
to using the download with embedded tomcat?
    > If it is not going to be supported, is it a resources issue, or why was 
that decision made?
    > 
    > Thank you,
    > Rod.
    > 
    
    
    

Reply via email to