Lets you configure the global settings that apply to all supported languages.
Lets you control some general preferences.
Name
The name of the code convention. This should be a short and unique name that easily identifies a code convention.
Description
Stores a short description for the code convention. The optional description may be used to provide a more detailed explanation of a code convention.
Name and description may be inserted into source files during formatting. See the section called “Environment” for more information.
Lets you control miscellaneous options that doesn’t fit elsewhere.
Force formatting
Jalopy can keep track of which files have been formatted previously (Refer to the section called “History” for more information about this feature). If the history is enabled, Jalopy won’t format files that have not changed since the last formatting. However, you can disable this check to force a reformat. For example, you might need to update the copyright notice for the whole code base. Enabling this switch ensures that all source files are always formatted.
Test formatting
When enabled, formatting output is not written to disk and/or opened editors are not updated. This may be worthwhile when you want to determine what files cause warnings or errors during formatting. This way Jalopy can be used somewhat similar to a coding style checker (see the section called “Code Inspector” for the available style checks). This option is mostly useful for batch mode processing, therefore it can be enabled from the Console, Ant or Maven Plug-ins directly, and should be normally left disabled here. Refer to the section called “Logging” for more information about the possible logging options.
Since 1.0
Insert trailing newline
When enabled, Jalopy inserts an empty line at the end of every file. This may help to avoid problems with certain text formatters and processors. Note that Jalopy always inserts at least one empty line after footers, so there is no real need (but it doesn’t hurt) to check the mark in case footers are used. See the section called “Footer” for more information on footers.
Checkout read-only files
When enabled, Jalopy tries to checkout read-only files when it detects that a file is under source control. Such behavior should be the default with most SCM providers anyway, but if you happen to use a SCM system that does not work this way, this option might come to the rescue. Please note that this feature is currently only available with the Eclipse and IntelliJ IDEA Plug-ins.
Since 1.9.2
Keep editor state
When enabled, Jalopy will keep the current editor state when formatting editor contents. If an editor is currently dirty, i.e. contains unsaved changes, Jalopy will only update the editor. Otherwise the file is changed on disk as well. Please note that depending on your IDE an undo might not be possible when this option has been enabled.
Since 1.9
Use current file in preview
When enabled, Jalopy will use the source file that is currently opened in the editor as the preview file for the configuration dialog. Otherwise custom code snippets are used instead. The preview uses the actual editor file, not the current editor contents. One therefore needs to persist any changes before they show up in the preview. Please note that you need to close and re-open the configuration dialog before an option change will take effect.
Since 1.9