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 192907 - [Compile on Save] Add possiblity to NOT deploy war file or ear file
Summary: [Compile on Save] Add possiblity to NOT deploy war file or ear file
Status: RESOLVED DUPLICATE of bug 188361
Alias: None
Product: javaee
Classification: Unclassified
Component: Maven (show other bugs)
Version: 7.0
Hardware: PC Windows XP
: P3 normal (vote)
Assignee: David Konecny
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-06 09:51 UTC by tomzi
Modified: 2010-12-07 22:57 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
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 tomzi 2010-12-06 09:51:49 UTC 
We use Jrebel in our project (which is a HUGE help), which basically listens to newly compiled class files, changed jsps, property files and so on and puts them directly into the jvm (don't know about the details :))

However if I turn on 'compile on save' netbeans does the compiling and jrebel will take the changes immediately, but netbeans would also deploy the .war (ear) file which it should not do, since jrebel takes care of that.

Please add an option to the compile on save feature that prevents deploying...
Comment 1 David Konecny 2010-12-07 22:57:02 UTC 
I fixed this recently. Should be in 7.0 Beta2. If you could test one of NB nightly builds and confirm that everything works for you would be a great help! See issue 188361 for more details. Thanks.

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