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.
Summary: | Run, Build, Clean on Maven EAR project should do action on -web and -ejb sub project as well | ||
---|---|---|---|
Product: | javaee | Reporter: | Jiri Skrivanek <jskrivanek> |
Component: | Maven | Assignee: | Martin Janicek <mjanicek> |
Status: | VERIFIED WONTFIX | ||
Severity: | normal | CC: | ymajoros |
Priority: | P3 | ||
Version: | 7.3 | ||
Hardware: | PC | ||
OS: | Windows 7 | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Jiri Skrivanek
2012-07-26 11:41:41 UTC
Valid problem, similar to the issue 195990. At the moment we don't use any EAR configuration on child sub-projects, but agree that it would be good to have this implemented. I strongly disagree! We have a very large EAR Project with hundreds of submodules. So a complete build of all submodules would take very long. If you change a file in one of your submodules just build the submodule and press "run" on your EAR Project. The EAR Project will be packed with the new submodules and you will see your changes immediately because the EAR project is build before Netbeans deploys it. I don't want Netbeans to build all my submodules just because I want the build a current EAR. There is already a "Build with Dependencies" Option on the EAR Projects that does exactly what you want. Maybe just add a "Clean and Build with Depencies" option but please don't change the default operations on the EAR project. I have to agree with your deadalus objections, closing as WONTFIX. I opened a similar issue: 218807. But I don't think saying we need to manually compile is a good solution. It wasn't like this when my project was an ant project. Change something, hit "run" and it runs. I'm not saying everything should be built (not fully, anyway). I'm just saying "run" should run the current version of my project with its modules. Why does it work (and quite fast) for an ant project? It works with Eclipse, too. *** Bug 218807 has been marked as a duplicate of this bug. *** (In reply to comment #4) > I opened a similar issue: 218807. > > But I don't think saying we need to manually compile is a good solution. > > It wasn't like this when my project was an ant project. Change something, hit > "run" and it runs. > > I'm not saying everything should be built (not fully, anyway). I'm just saying > "run" should run the current version of my project with its modules. Which basically means you would need to recompile all dependent modules. Or what do you think NetBeans should do when running the EAR project? (I can see only two options - either compile everything or just compile current project and try to run it) > Why does it work (and quite fast) for an ant project? It works with Eclipse, too. Do not know to be honest (CCing to David to find it out:)). David do you think how is this implemented in Ant based projects? ymajoros maybe your problem is caused by something else - Compile on Save seem to be working incorrectly for some EAR projects (please follow the issue 219916 if you are interested) |