# Standard Web Project Properties Dialog Box: Compiling

Use to set compiling options.

In the Compiling page, you can set the following properties:

Element | Description
--- | ---
Copy Static Resources on Save | This option enables you to choose how the IDE handles non-Java files when the files are modified and saved. When selected, the files are automatically copied to the build directory of the project when the files are saved. When not selected the non-Java files are not copied when you save the files. You can invoke the Build command to copy the files to the build directory. This option is automatically enabled when you enable Deploy on Save.
Compile on Save | This option enables you to choose how the IDE handles Java files when the files are modified and saved. When selected, Java files are compiled when you save them and generated class files are stored in the build directory of the project. This option can save you time when you run or debug your application in the IDE. When not selected the Java files are not compiled when you save the files. You can invoke the Build command to compile the files. This option is automatically enabled when you enable Deploy on Save. Deploy on Save is automatically disabled when you disable this option.
Generate Debugging Info | If selected, the compiled classes will include information necessary for stopping at breakpoints and stepping through the application with the debugger.
Report Uses of Deprecated APIs | If selected, you are notified in the compilation output of any deprecated APIs that the code uses.
Enable Annotation Processing | Select this check box to enable annotation processing during building the project. When deselected, compilation proceeds without annotation processing. Any annotation processors on the classpath are ignored. This check box corresponds to the `-proc:none` option of the compiler.
Enable Annotation Processing in Editor | When selected, you can enable annotation processing in the IDE Editor. This means that any additional artifacts that are generated by processors (classes, methods, fields, etc.) will be visible through the IDE features, such as code completion, Navigator, GoTo Type and Find usages. Also, the Editor will display any diagnostic messages produced by annotation processors. In addition, completion suggestions for annotation attribute values produced by annotation processors will become available in Java code completion.
Annotation Processors | Click Add to explicitly specify an annotation processor for your project. In the Add Annotation Processor dialog box, enter a fully qualified name of the annotation processor. This setting corresponds to the `–processor` option of the compiler. Note that to use the annotation processor, you should also add it to the classpath or the processor path of your project in the Libraries category.
Additional Compiler Options. | Enter any additional compiler options in a space-separated list. For example, if you type -help -version, the Output window displays the Java compiler's synopsis of standard options together with the Java compiler's version information.
Test compile all JSP files during build | Specifies that the project's JSP files are to be compiled when you build the project. By default, the IDE does not compile JSP files while building a project. This is because JSP compilation can take a long time because JSP files have to be translated to servlets before they can be compiled.

Notes:

- Do not use compiler options like `-bootclasspath` to cross-compile between Java platforms. Instead, register the target Java platform by clicking Manage Platforms in the Libraries page and set the target JDK for the project.
- You can manage the project's classpath in the Libraries page. You can set up file filters for WAR file creation in the Packaging page.

Related Topics

Developing Applications with NetBeans IDE,

Copyright © 2016, Oracle and/or its affiliates. All rights reserved.