Jindent 3.5.2 released
Bugfixes:
- Jindent's license scheme threw validation error on JRE 1.5.0 Update 2. This is fixed now.
Bugfixes:
Changes/New Features in Jindent:
Bugfixes in Jindent
Bugfixes in JindentCommander 1.12
Bugfix in JindentCustomizer 1.21
Bugfixes in JindentCommander 1.11
Changes/New Features in Jindent 3.5
assert keyword support).	
     	spaceBeforeAssertColon = boolean spaceAfterAssertColon = boolean
blankLinesBeforeFilteredCode = n blankLinesAfterFilteredCode = n
for-statements.;;;;; will be preserved now.! and tilde ~:spaceBeforeBang = boolean spaceAfterBang = boolean spaceBeforeBangAfterAndOr = boolean spaceAfterBangAfterAndOr = boolean spaceBeforeTilde = boolean spaceAfterTilde = boolean
spaceBeforeConditionBang = boolean
-auto now."*not available*" for variables fileName 
      	and fullFileName if the Jindent interface is invoked 
      	through streams.-bakext extension
conventionString is deprecated now, therefore it got separated into two keys: 
date = timePattern conventionNote = String
'date' is an environment variable which can be used in all templates.
import statements are not separated by classes anymore.noBlankLinesAfterLeftBraceGeneral = boolean noBlankLinesAfterLeftBraceMethod = boolean noBlankLinesAfterLeftBraceClassInterface = boolean noBlankLinesAfterLeftBraceTryCatch = boolean
This switch can be usefull if generally blank lines before 
	      comments are desired, but at the beginning
	      of a block it could create a unnecessary gap, for instance:
void myMethod(int i)
{
    // first comment
    int x = a(i) + b(i);
    System.out.println(x);
    // second comment
    int y = c(x) + d(x);
    System.out.println(y);
}
			The new switches (here noBlankLinesAfterLeftBraceMethod = true) can change this output to:
void myMethod(int i)
{
    // first comment
    int x = a(i) + b(i);
    System.out.println(x);
    // second comment
    int y = c(x) + d(x);
    System.out.println(y);
} 
		paddingParenthesis is deprecated now and got divided into new switches: 
paddingMethodDeclarationParenthesis = boolean paddingMethodCallParenthesis = boolean paddingStatementParenthesis = boolean
wrapAfterConditionalOperators = boolean wrapAfterComparisonOperators = boolean wrapAfterNumericalOperators = boolean
alignTooLongDeclarations = boolean alignTooLongAssignments = boolean separateChunksByTooLongLines = boolean
alignTooLongComments got improved.indentWrappedThrows, indentWrappedExtends, indentWrappedImplements 
      	properties have effect on normal wrapping too now.wrapDeclarationAssignmentsToRightSide = boolean
setCodeWarnings(boolean) added to JindentParser interface. 
     	JindentProperties() creates an empty property object with invalid 
     		entries now. To create a property object with Jindent's default setting we introduced a new class 
     		DefaultJindentProperties.DefaultJindentProperties object. 
     	-inputEncoding enc -outputEncoding enc -resourceEncoding enc
indentCaseFromSwitch = boolean
new property setting is:
indentCaseFromSwitch = n
//JDOC-
This switch can be used to skip automatical javadoc insertion for methods/classes/interfaces/fields.
It can be used to preserve javadoc inheritance which is supported by Sun's javadoc tool.
Changes/New Features in JindentCommander:
-e added to run a JindentCommander project file without showing the GUI. 
     	Changes/New Features in JindentCustomizer:
$fullFileName$ and $fileName$ work in JindentCustomizer now. 
     	Bugfixes in Jindent:
neverIndentFirstColumnComments = true.[] in several source code parts is fixed.abstract, strictfp and final classes inspaceBeforeStatementParenthesis = false setting is fixed. Now works proper for: 
     		return(...), throw(...)indentLeftBrace... caused by nasty placed comments.JindentBean interface is not obfuscated anymore. 
     	alignTooLongComments works correct now. 
     	"/*---" and ending with "---*/" 
     		will not automatically deleted anymore. 
     	CloneNotSupportedException of method clone() 
       	in the classes JindentProperties and JindentEnvironment 
       	is never thrown. To avoid confusion they are removed. 
     	InsertMissingJavadocTags = true combined with formatJavadocComments = true works 
     		proper now. 
     	"" in templates are accepted now. 
     	Bugfix: