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.
see subject. the consequences are that modified jar dependencies won't trigger redeploy etc..
Hi there, I followed your discussion about the deploy on save functionality (http://forums.netbeans.org/ntopic13927.html) and found this issue. I downloaded Netbeans 6.8 M2 and tested the deploy on save feature but it didn't work for my purposes. I have very simple Maven JavaEE project structure. One Ear-Project, 1 War, 1 EJB. My goal is that changes I make to the war project (e.g to the xhtml) are automatically deployed to the application server (in my case, glassfish V2.1). A simple refresh on the browser should show the changes. So I activated the deploy on save on both the war project and the ear project, changed something in the xhtml file but the changes aren't published. Could you please tell me if I am doing something wrong? Or is this feature just not implemented yet? Greetings Daniel
it's not done yet.
I tested it with 6.8 RC1, and not working. Product Version: NetBeans IDE 6.8 RC1 (Build 200911252200) Java: 1.6.0_15; Java HotSpot(TM) 64-Bit Server VM 14.1-b02 System: Linux version 2.6.31-15-generic running on amd64; UTF-8; hu_HU (nb) The module dependencies with <type>war</type> should be auotmatically copied to the main project's target dir on CoS enabled.
(In reply to comment #3) > I tested it with 6.8 RC1, and not working. > > Product Version: NetBeans IDE 6.8 RC1 (Build 200911252200) > Java: 1.6.0_15; Java HotSpot(TM) 64-Bit Server VM 14.1-b02 > System: Linux version 2.6.31-15-generic running on amd64; UTF-8; hu_HU (nb) > > The module dependencies with <type>war</type> should be auotmatically copied to > the main project's target dir on CoS enabled. I confirm that the compile on save feature is not implemented in Netbeans 6.8 RC1. If it should work, please tell us what to do to make it work. Greetings
Changing the default owner to issues@javaee.
I am not sure what is happing with this bug. It still exists. I know that I could switch to JavaEE and change the project to deploy ejbs within a war project, which would make deploy on save work but that's no solution. Due to this bug I can't change several projects from ant to maven.
So is this a duplicate of enhancement 177230?
yes, it is a duplicate of 177230.
duplicate *** This bug has been marked as a duplicate of bug 177230 ***