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 244057 - deploy on save triggered when it shouldn't
Summary: deploy on save triggered when it shouldn't
Status: RESOLVED DUPLICATE of bug 253630
Alias: None
Product: javaee
Classification: Unclassified
Component: Maven (show other bugs)
Version: 8.0
Hardware: PC Other
: P3 normal with 1 vote (vote)
Assignee: Martin Janicek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-25 05:06 UTC by ymajoros
Modified: 2015-08-06 12:49 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ymajoros 2014-04-25 05:06:44 UTC
I have a maven Java EE project which consists in this structure:

- parent pom
- EAR
- EJB
- WAR

Deploy on save is unchecked on all 4, compile on save is enabled, "copy static resources" is enabled on WAR.

Sometimes, my application gets redeployed when I save a file. Actually, the EJB or WAR module gets redeployed. I don't want this, this option is unchecked. When that happens, closing Netbeans helps solve it. If I don't, it keeps doing it.

This is on Glassfish 4, but it has been happening for years on various configurations.

I opened similar bugs, but I think this report is unique.
Comment 1 Martin Janicek 2014-07-15 13:13:42 UTC
Hi, could you please try to find and describe reproducible test case? 

I created new web application with DoS enabled and included simple servlet. Changing the servlet caused DoS to redeploy it's class file, resulting in changed result shown in browser. 

After that I disabled DoS and tried to do the same. This time the old result persist and servlet's class file didn't refresh. Both scenarios seems to work as expected.

Please reopen the issue together with additional information. Thanks in advance!
Comment 2 ymajoros 2014-07-15 14:03:14 UTC
Sorry, I can't but the bug still happens and is real. It has happened for years from time to time. I don't know why, but  I know it comes back once in a while. 

I understand it would be easier to be able to reproduce it (for me too btw), but I don't know how to do it. I just know that unchecking/rechecking all options right fixes it, sometimes after restarting NB.

Just tell me if there is anything I can do when it happens to help diagnose the root problem.
Comment 3 Martin Janicek 2014-07-15 14:28:10 UTC
(In reply to ymajoros from comment #2)
> Sorry, I can't but the bug still happens and is real. It has happened for
> years from time to time. I don't know why, but  I know it comes back once in
> a while. 

I believe you. The problem is I have absolutely no idea how to move forward with such issue when I don't know basically anything.

> I understand it would be easier to be able to reproduce it (for me too btw),
> but I don't know how to do it. I just know that unchecking/rechecking all
> options right fixes it, sometimes after restarting NB.
> 
> Just tell me if there is anything I can do when it happens to help diagnose
> the root problem.

Please run NetBeans with option -J-Dorg.netbeans.modules.maven.j2ee.level=0 and attach message.log when the problem occurs.

Also some context might help. If you will encounter the problem again and you have done some setting changes before or anything unusual, I might be able to at least guess where is the trouble coming from.

I'm sorry, but I don't know how to help at the moment. I will let the issue opened, decreased to P3 and we will see if I will be able to see something else from your log.
Comment 4 Petr Hejl 2015-08-06 12:49:33 UTC

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