Wouter van Reeven wrote:
> [snip]
>>>
>>> On 2 August 2010 16:37, Wouter van Reeven <wouter_at_van.reeven.nl> wrote:
>>>
>>> https://glassfish.dev.java.net/issues/show_bug.cgi?id=12864
>>>
>>>
>>>
[snip]
I have tried to add a comment to this issue, but the issuetracker is
being kind of broken at the moment, so I will post it here.
I have had a quick look at the issue and reckon that the problem is in
NB and/or Maven.
Let's take a look at some of the things and you might see what is
happening...
There are two families of projects supported by NetBeans: project driven
via ant and those driven via maven.
Both of these families use directory based deployment by default, since
this makes redeployment faster.
If you deploy an ant based project and then do a clean and build, the
ant script does an undeploy BEFORE attempting to delete files and
directories.
It looks like the maven based project does not trigger an undeploy
before the attempt to delete files and directories...
You do not run into this problem with asadmin based deployment, since
calls to asadmin deploy also trigger an undeploy.... Plus it is likely
that you are deploying the dot-ear file, not a deployable exploded
directory hierarchy.
You may want to look at the server properties for your v2.1.1 server and
untick Directory Deployment Enabled, which appears on the Options
'page', too see if that helps.
vbk