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.
In NB 3.6, we could compile or build one package. There were compile and build items in the package context menu. This is not possible anymore with NB 4.0, but is much needed.
Reassigning for evaluation.
Don't think the UI spec ever provided for enabling F9 on a folder in a source root, but it would be easy enough to do AFAIK - just set javac.includes to e.g. "org/foo/pjg/". Don't consider this important since F9 itself was only really intended as a quick way to syntax-check a single file open in the editor; F11 (Build Project) remains the canonical way to compile.
Building the whole app takes longer, even without cleaning before, because NB has to look, which files changed (we have >1700 Java sources). If I am sure, that I only want that package, then it should be possible to compile or build (both was possible in NB 3.6) only one package. Also, build should come back for a single file (only compile possible now).
No intention of reintroducing an action such as Clean & Build File.
I have another advantage for the build only one package action: In our company, every developer "owns" one or more packages. If you want to see, what's deprecated only in "your" package, you switch deprecated warnings on and build only "your" package.
Yes, could be useful in such a setup... though for new code I would almost certainly recommend that each of those code modules be made into a separate project, under the assumption they are separated functionally and have controlled interdependencies. Not an option for existing code unless you are willing to move versioned files around and fool with any existing build scripts, however.
*** Issue 47790 has been marked as a duplicate of this issue. ***
Should be fixable for 4.0.
one more reason to fix thisone: we have a package with own text components, which we use in the form editor. if we are using the form editor, we need these text components to be compiled. so even if there are other classes which are not able to compile, we need the possibility to compile only the package with our text components.
Checking in ant/src/org/apache/tools/ant/module/api/support/ActionUtils.java; /cvs/ant/src/org/apache/tools/ant/module/api/support/ActionUtils.java,v <-- ActionUtils.java new revision: 1.5; previous revision: 1.4 done Processing log script arguments... More commits to come... Checking in java/j2seproject/src/org/netbeans/modules/java/j2seproject/J2SEActionProvider.java; /cvs/java/j2seproject/src/org/netbeans/modules/java/j2seproject/J2SEActionProvider.java,v <-- J2SEActionProvider.java new revision: 1.28; previous revision: 1.27 done Processing log script arguments... More commits to come... Checking in java/project/src/org/netbeans/spi/java/project/support/ui/Bundle.properties; /cvs/java/project/src/org/netbeans/spi/java/project/support/ui/Bundle.properties,v <-- Bundle.properties new revision: 1.7; previous revision: 1.6 done Checking in java/project/src/org/netbeans/spi/java/project/support/ui/PackageViewChildren.java; /cvs/java/project/src/org/netbeans/spi/java/project/support/ui/PackageViewChildren.java,v <-- PackageViewChildren.java new revision: 1.43; previous revision: 1.42 done
Pavel check if web/project needs a similar fix...
It's only available in the build menu, not in the context menu of the package. Could you please implement it there, too? Also, there is only the compile option. But to see, what's deprecated in this package, the classes first have to be deleted, otherwise only the changed sources are being compiled. So, a clean+compile option is missing.
The action is also in the package pop up menu as "Compile Package" and can be invoked by "F8". The clean and build package is a bit strange. The deprecation should be handled by task list and not by build system. Jano, what you do you think about it?
Since which build? I do not have it in the package popup menu. Not in the project tab and not in the files tab.
Regarding the "need" for clean + build: This was possible in NB 3.6. It was called "build" then. See original description here.
It does what it is currently supposed to do (Thomas get a current build to see), which is compile the package, i.e. whatever files in it are not yet compiled. Ability to either have a separate Clean & Build {Files | Package} action, or to make the current Compile {Files | Package} action do a clean first, is a reasonable RFE for a future release, but please file it *separately* because this is fixed.
1. It's still not in the context menu in build 20041017, only in the build menu. 2. The ORIGINAL Summary was "No way to build or compile only one package". Someone altered it to only "compile".
1) It is in a context menu of pacakge. In the logical view select package. The third action is "Compile Package F9". See attached image. 2) Agree with Jesse.
Created attachment 18359 [details] Screen Shot
OK, I got it. I am using -J-Dorg.netbeans.spi.java.project.support.ui.packageView.USE_TREE_VIEW=true and then it's not in the context menu. Also, it is not in the context menu, if you are in the "Files" tab.
If you have USE_TREE_VIEW=true we just use the same appearance as the Files tab. I think there is no need for a special context menu here. The KB shortcut works in any case. The UI is only specified for the regular package view for 4.0; USE_TREE_VIEW is unsupported. The item, along with many other project-oriented things, is intentionally not shown in the Files tab. BTW Tomas does F9 now compile subpackages? Or only files directly in the package?
The "Compile Package" action compiles files and subpackages.