This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
We have a maven enterprise project that contains several web and ejb modules. All modules will be combined in a single ear file. Since some weeks we have problems with the deployment of the application. Sometimes netbeans deploys the ear itself to glassfish instead of the "gfdeploy" folder content. Autodeploy doesn´t work in this cases. The developer must close/refresh/deploy/undeploy the project several times and after that the gfdeploy content will be deployed. You will not find any error messages in the log that gives us a hint whats going wrong. On one developer machine close/open modules does not work to fix the problem. Also on this machine there is no gfdeploy folder in the target of assembly project. The same problems occurs with 7.1BETA Version.
Forgot to say that the permanent problem cannot be solved through new IDE installation, deletion of .netbeans folder and so on. The code is the same as on the other machines...
I want to make sure that I am reading your description correctly. Please correct any mistakes that I make below... 1. You have NB and GF installed on a machine. 2. GF is registered in NB as a local instance/domain (not a remote domain) 3. you have created an ent app with multiple sub projects that are maven based. 4. you do some number of initial deployments and they are directory based. 5. at some point, you make a change to the app (or one of its submodules) and it 'stops' being directory deployed. 6. if you 'close/refresh/deploy/undeploy' a few times, the IDE switches back to using a directory deployment strategy. If this is restatement is 'correct', please provide answers to the following questions... 1. what is the work-flow that you are following? 2. What menu items are you triggering when you notice this witch happening?
Yes, absolutely correct. Here is the common workflow: 1. Open Netbeans IDE 2. Open Maven Enterprise project with required modules 3. Right click on Maven assembly module -> Build with dependencies 4. Run/Debug Normally the content of gfdeploy will be deployed and everything works fine. Sometimes it doesn't work and the ear will be deployed directly. Several refreshes and open/close project solves the problem. On one machine refreshing doesn't help. Also there is no gfdeploy folder. Code is always the same. In assembly pom the auto deploy property is set. Replacing the project with a fresh copy, deletion of local maven repository or netbeans user directory has no affect. My machine works fine. A colleague from me has had the temporal deploy problem so I decided to help him. I opened his project with my IDE and tries to build. Since this time my own project doesn' work anymore. Gfdeploy is not created and the ear is deployed directly.
The problem is solved. We have a <modules> section in our main project. Someone removed a module definition while changing something, therefore "Open required projects" doesn´t open that project. Because the dependency still exists everything works fine except of the directory deploy. I added the reference again, open required projects and everything works as expected.