You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2011/06/02 13:22:40 UTC

DO NOT REPLY [Bug 51294] Since 7.0.12 do not work option unpackWARs=true for WARs outside appBase

https://issues.apache.org/bugzilla/show_bug.cgi?id=51294

--- Comment #3 from Mark Thomas <ma...@apache.org> 2011-06-02 11:22:40 UTC ---
The unpackWAR option of the context is so rarely used I had actually forgotten
it even existed.

http://tomcat.markmail.org/thread/rk6fw5ooohgiqklu explains why it was
introduced. Even then it was as an override to unpackWARs at the host level.

The original intention, the current implementation and the current
documentation are all different. For now, I'm going to take the easy way out
which is to align the documentation with the current implementation. I'm not
against changing the implementation to reflect the original intention but that
probably needs some discussion on the users list as to what behaviour makes
most sense.

I don't see any of the WAR unpacking options being changed to trigger the
unpacking of an external WAR in the appBase without a strong use case that
can't be met by alternative configurations.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org