Wouter van Reeven wrote:
> In the older versions of GlassFish you needed to provide
>
> --force=true
>
> to redeploy. But if you didn;t provide that, the deployment would fail.
Well, in older releases, --force was true by default. So, deploy followed
by deploy of the "same name" will always succeed. In v3, --force is
false by default (an incompatible change).
What Felipe reports below is something we are going to fix. I think creating
_ copies of app names, context-roots, application folders is needless and
we are fixing it ...
>
> HTH, Wouter
>
> On Fri, Oct 16, 2009 at 05:20:02PM +0200, Felipe Ga�cho wrote:
>> Every time I deploy my JSF 2.0 Glassfish creates a second copy ...
>>
>>
>> asadmin --user=admin deploy arena-jsf20.war
>> asadmin --user=admin deploy arena-jsf20.war
>>
>>
>> now I have two applications on my Glassfish v3b67 Administrative Console:
>>
>> 1) arena-jsf20
>> 2) arena-jsf20_1
>>
>>
>> what parameter should I use to redeploy the application on the same
>> context, without Glassfish generating a second one ?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: quality-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: quality-help_at_glassfish.dev.java.net
>