Merge pull request #70 from jfdenise/release

Document that annotated type rule can take a suffix

maven/docs/rules.properties

@@ -8,7 +8,7 @@ org.wildfly.rule.add-on-description=The description
 org.wildfly.rule.add-on-description.value= e.g.: `Server command line tools: jboss-cli, add-user, elytron-tool`
 org.wildfly.rule.add-on-fix-=The rule fixes an error. The rule name must be suffixed with the type of error. Known error types: `no-default-datasource`, fix a missing default datasource, `unbound-datasources`, fix an unbound datasource
 org.wildfly.rule.add-on-fix-.value=No value for `no-default-datasource`. For `unbound-datasources`, env variable with `ITEM` value replaced by discovered JNDI path. e.g.: `JNDI env,MSSQLSERVER_JNDI=ITEM`
-org.wildfly.rule.annotated.type=Expected annotated type, annotation and annotation field values. Field values can be regex. 
+org.wildfly.rule.annotated.type=Expected annotated type, annotation and annotation field values. Field values can be regex. This rule can take a suffix and be used multiple times for a given layer.
 org.wildfly.rule.annotated.type.value=The type followed by the annotation (with some optional field=value). For example: `org.example.MyType,org.example.MyAnnotation[field1=foo,field2=bar*]`
 org.wildfly.rule.annotations=Expected annotations 
 org.wildfly.rule.annotation.field.value=Expected annotation with field values. Field values can be regex. This rule can be added multiple time to a layer, it must contains a suffix to be unique.