You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@tomee.apache.org by jieryn <ji...@gmail.com> on 2015/03/13 02:45:27 UTC

Strange ROOT.unpacked directory

Using Apache TomEE 1.7.1 PLUS. I can't remember if this is new, or
relatively new, or.... but automatic unpack of the ROOT.war
application seems to be triggering the creation of ROOT.unpacked
directory, which is then auto-deployed to Tomcat/TomEE.

How can I stop this behavior? Thanks!

Re: Strange ROOT.unpacked directory

Posted by jieryn <ji...@gmail.com>.

Always using ROOT.war with automatic unpack. I am trying to see if
this is related to cargo-maven2-plugin:redeploy via /manager
application.

On Fri, Mar 13, 2015 at 2:01 AM, Romain Manni-Bucau
<rm...@gmail.com> wrote:
> Hi
>
> Can happen if ROOT is a file IIRC. Also recall having worked on sthg like
> it - not related to ROOT - on snapshots
> Le 13 mars 2015 02:46, "jieryn" <ji...@gmail.com> a écrit :
>
>> Using Apache TomEE 1.7.1 PLUS. I can't remember if this is new, or
>> relatively new, or.... but automatic unpack of the ROOT.war
>> application seems to be triggering the creation of ROOT.unpacked
>> directory, which is then auto-deployed to Tomcat/TomEE.
>>
>> How can I stop this behavior? Thanks!
>>

Re: Strange ROOT.unpacked directory

Posted by Romain Manni-Bucau <rm...@gmail.com>.

Hi

Can happen if ROOT is a file IIRC. Also recall having worked on sthg like
it - not related to ROOT - on snapshots
Le 13 mars 2015 02:46, "jieryn" <ji...@gmail.com> a écrit :

> Using Apache TomEE 1.7.1 PLUS. I can't remember if this is new, or
> relatively new, or.... but automatic unpack of the ROOT.war
> application seems to be triggering the creation of ROOT.unpacked
> directory, which is then auto-deployed to Tomcat/TomEE.
>
> How can I stop this behavior? Thanks!
>