Hi, is the Compile on Save setting in the Compile section of the project properties turned on (i.e. set to "For both application and test execution")?  Thanks.

They are turned on. for all projects.

when saving this is printed in IDE log


INFO [org.netbeans.modules.j2ee.deployment.impl.TargetServer]: Cannot incrementally deploy to more than one target

When saving this is printed in IDE log

INFO [org.netbeans.modules.j2ee.deployment.impl.TargetServer]: Cannot incrementally deploy to more than one target

When saving this is printed in IDE log.

INFO [org.netbeans.modules.j2ee.deployment.impl.TargetServer]: Cannot incrementally deploy to more than one target

some more logging Finest 

FINEST [org.netbeans.modules.j2ee.deployment.impl.ServerRegistry]: Entering registry initialization
FINEST [org.netbeans.modules.j2ee.deployment.impl.ServerRegistry]: Entering registry initialization
FINE [org.netbeans.modules.j2ee.deployment.impl.DeployOnSaveManager]: Delivered copy artifact: /home/joe/NetBeansProjects/mavenproject1/mavenproject1-web/target/mavenproject1-web/index.jsp, null, isReferencedLibrary: false, isRelocatable: false, isServerResource: false
FINE [org.netbeans.modules.j2ee.deployment.impl.DeployOnSaveManager]: Performing pending deployments
FINEST [org.netbeans.modules.j2ee.deployment.impl.DeployOnSaveManager]: Artifacts updated: [/home/joe/NetBeansProjects/mavenproject1/mavenproject1-web/target/mavenproject1-web/index.jsp]
FINEST [org.netbeans.modules.j2ee.deployment.impl.ServerRegistry]: Entering registry initialization
FINEST [org.netbeans.modules.j2ee.deployment.impl.ServerRegistry]: Entering registry initialization
FINE [org.netbeans.modules.j2ee.deployment.impl.ServerInstance]: DebuggerInfo cannot be found for: GlassFish v2.x
INFO [org.netbeans.modules.j2ee.deployment.impl.TargetServer]: Cannot incrementally deploy to more than one target
FINE [org.netbeans.modules.j2ee.deployment.impl.TargetServer]: []
FINE [org.netbeans.modules.j2ee.deployment.impl.DeployOnSaveManager]: Deployment state MODULE_NOT_DEPLOYED
FINEST [org.netbeans.modules.j2ee.deployment.impl.ServerRegistry]: Entering registry initialization

Ok, assigning to Petr H as the deployment infrastructure owner. A few more questions:
- If you deploy explicitly using the Deploy action, does it work? Does the application get updated?
- Does automatic redeployment work for GlassFish v3? 

Thanks.

1 Can't find Deploy action in maven project.
2 Yes same problem

More: also has issues on my work computer that uses NetBeans 6.8.

Then i get this in the logs.

org.openide.filesystems.FileAlreadyLockedException: /home/jocke/NetBeansProjects/mavenproject1/mavenproject1-web/target/mavenproject1-web/index.jsp
        at org.netbeans.modules.masterfs.filebasedfs.fileobjects.LockForFile.registerLock(LockForFile.java:111)
        at org.netbeans.modules.masterfs.filebasedfs.fileobjects.LockForFile.tryLock(LockForFile.java:100)
        at org.netbeans.modules.masterfs.filebasedfs.fileobjects.FileObj.lock(FileObj.java:308)
        at org.netbeans.modules.maven.j2ee.web.CopyOnSave.copySrcToDest(CopyOnSave.java:100)
        at org.netbeans.modules.maven.j2ee.web.CopyOnSave.handleCopyFileToDestDir(CopyOnSave.java:329)
        at org.netbeans.modules.maven.j2ee.web.CopyOnSave.fileChanged(CopyOnSave.java:188)
[catch] at org.netbeans.modules.maven.j2ee.web.CopyOnSave$1.run(CopyOnSave.java:181)
        at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:602)
        at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:1084)

> 1 Can't find Deploy action in maven project.

Sorry, I meant Run action.

Please describe your steps precisely. You start with creation of ejb, yet couple of lines below you talk about parent project.

In your steps you run ejb project, so it is just logical that index.jsp is not redeployed.

Please provide the steps to reproduce in format like in this sample:
1) create EAR project
2) enable CoS in project and all children
3) create empty session bean in ejb

... etc.

1) create maven EAR project with JEE 5 as option
2) enable CoS in project and all children
3) create empty session bean in ejb
4) build maven parent project and all children
5) Set glassfish v2.1 as server in project/properties/run on EAR project 
6) Run EAR using run in context menu
7) browser shows Hello world index page
8) add one more hello world tag on index page and save
9) Refresh browser
10) browser still shows one hello world should be two. 


The index.jsp should have bean copied to  directory in ${name_of_ear_project}/target/gfdeploy/${name_of_war_project}/

So changes can be seen, this is how it works in ant based projects anyway.

This is a guy also having the same problem, this could be OS specific (Ubuntu)

http://stackoverflow.com/questions/2290935/hot-deploying-changes-with-netbeans-maven-and-glassfish

So could this be a duplicate of enhancement 177230? Looks like this was never supported, but certainly there is a lot of interest in this feature.

Yes it's a duplicate! sorry i really thought this was supported already. I am stuck with rsync for now, but i will sure vote on that issue.

Ok, marking as a duplicate of bug 177230. Perhaps the "web files" aspect (i.e. auto-deploying web resources) could be simpler to implement; auto-redeploying changed Java files will probably be harder.

*** This bug has been marked as a duplicate of bug 177230 ***

Please see your file context.xml it must look like 

<Context antiResourceLocking="false" path=...>




And see  the link 

http://tomcat.apache.org/tomcat-8.0-doc/config/context.html#Standard_Implementation


Please note that setting this to true has some side effects, including the disabling of JSP reloading in a running server