auto(un)deploy problems

[hakoni]

Hi gentlemen,

I have an issue with netbeans 6.5 / 7.0 and glassfish web applications that I hope someone can help me with.

Setup: a test glassfish app-server, and a production glassfish app-server, registered in netbeans.

a project deploys/undeploys to the server specified in the "Project->Run->Server" , so to have a test server/production server requires to change that property.

When developing, sometimes it is required to perform a clean/build, to make sure all dependencies are ok from all sub projects and libraries. But the problem is when the above mentioned property is set to a production server, it will first undeploy the webservice from the app-server, clean the project and build. (making the webservice unavailable in the meantime) and if any dependencies fails, it results in an unbuildable project, and an unavailable webservice on the production server.

Making things worse. on an ear -project I have, even changing the server in the project properties, from the production server, to the test server, I horribly experienced an undeploy from the production server, before it switched to the test server. Just because I changed that option in the project properties.

I have not enabled "Deploy on Save" in any of my projects

So, is there any way to disable those automatically initiated undeploy catastrophes? Or, should I only use a test-server from the ide, then build war/ear packages to deploy to production servers manually only?

I'm curious how other users are handling development under a test/production environment like this?

Kind regards, Håkon

[Jeffrey.Rodriguez]

I noticed the same thing myself today.

It's a part of the project's build-impl, undeploy-clean is a dependency of clean.

I hope this is a bug as it's highly undesirable, and occurs on local and remote domains making it too dangerous to put production servers in Netbeans' server manager.

[Andy Stevens]

2009/2/18 Jeffrey.Rodriguez <address-removed>:

[Jeffrey.Rodriguez]