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.

Bug 232899 - "Deploy on Save" does not work for submodules
Summary: "Deploy on Save" does not work for submodules
Status: NEW
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 7.3.1
Hardware: PC Windows 7
: P2 normal with 2 votes (vote)
Assignee: Petr Hejl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-17 13:34 UTC by daedalus
Modified: 2015-10-06 19:16 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
sample maven project (9.63 KB, application/zip)
2013-07-17 13:34 UTC, daedalus 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description daedalus 2013-07-17 13:34:52 UTC 
Created attachment 137317 [details]
sample maven project

Hello, 

I'm developing a Java-EE-6-Web-Profile application. I use maven as build managing tool. I tried with Netbeans 7.3, 7.3.1. and 7.4 beta. 

So basically I have one web-project (war) and multiple module projects (jars).
The web application has the modules declared as dependencies. 

I activated the "compile on save" feature on every single project. The web project hast also the "deploy on save" feature activated. 

It works but only for classes inside the web application. If a change a class inside a jar nothing happens. I have to manually build the module and redeploy the web application to see the change.

As my application is highly modular there is only one lonely class inside the web application everything else is inside the module jars so the "deploy on save" feature is sadly more or less useless for me. 

I created a small sample project to show the problem. 


So could you please support submodules as well for the deploy on save feature?
Comment 1 Petr Hejl 2013-07-17 19:48:10 UTC 
I believe build of the jar should trigger DoS on your web project. Does it work for you at least this way?
Comment 2 daedalus 2013-07-19 17:40:23 UTC 
Tried with Netbeans 7.3 and 7.4 beta but no success. 
I still had to manually redeploy the webapplication after building the submodule.
Comment 3 everflux 2015-03-28 14:43:08 UTC 
Same with Netbeans 8.x / current dev

Product Version: NetBeans IDE Dev (Build 201503280001)
Java: 1.8.0_40; Java HotSpot(TM) 64-Bit Server VM 25.40-b25
Runtime: Java(TM) SE Runtime Environment 1.8.0_40-b25

I have the following maven project layout:

project a ("commons") (jar artifact)
project b ("web") depending on project a

Changes in project are are not detected, although both projects are open in NetBeans and opening 'dependencies' of project b shows the maven-project dependency inside the NetBeans projects.

Even a clean-build on project b is not sufficient. I have to build project a and manually trigger a build of project b to pickup the changes. Would be really great if this could be improved since the workflow is really error prone and takes the fun out of NetBeans.
Comment 4 everflux 2015-03-28 14:50:25 UTC 
I can reproduce it with the glassfish container, seems not to be limited to tomcat.
Comment 5 kevin.isabelle 2015-10-06 19:16:05 UTC 
I confirm this bug. This is a real pain. Got to switch to Spring Eclipse for proper redeploy. Much much sadness.
Comment 6 kevin.isabelle 2015-10-06 19:16:45 UTC 
I tested the feature on Netbeans 8.0.2 and this is persisting.