This error message most likely indicates there were some left over
directories from last deployment which prevents the new deployment from
expanding files in the applications repository.
I am not sure why a successful undeployment will still leave files
behind, so it will be interesting to take a look if we can reproduce
this. I have also checked in some changes yesterday to clean up any left
over directories before we starts the new deployment, so that should
help the new deployment to go through regardless of why the directories
were left behind from previous (un)deployment.
- Hong
Amy Roh wrote:
> This works for me. Can you send me the test war and steps to reproduce?
>
> Deepa Singh wrote:
>> I have a v3 build. When I deploy a war application. It goes fine.
>> Undeploy it, displays success message like this
>>> SUCCESS : jsfastrologer undeployed successfully
>>
>> Now, make some changes to the app, and deploy again,I get this error.
>>> [exec] FAILURE : Error while creating directory for jar expansion
>>
>> Is this a known problem with recent v3 builds?
>>
>> Thanks
>> -Deepa
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>