[maven-release-plugin] prepare for next development iteration
Merge branch 'release/3.3.1' into dev
[issue #17] changed lists to jxlists so that sorting could be done
Merge branch 'bug/17-unsorted-usergroup-list' into dev
[issue #18] triggered refresh of the usergroups of the classes involved in the change so that proper info is displayed
Merge branch 'bug/18-refresh-ug-after-class-change' into dev
[issue #19] sorting permissions alphabetically before displaying
Merge branch 'bug/19-perms-of-class-props-not-sorted' into dev
[issue #20] proper connection status changed implementation so that children will not be set twice
[issue #20] introduced a KeyContainer that stores the key object and its initial hashcode so that we circumvent the issue of mutable hashmap keys
Merge branch 'bug/20-disconnect-issue' into dev
[issue #22] completely removed query management
Merge branch 'feature/22-remove-query-management' into dev
[issue #24] removed cids class node catalog and moved navigator nodes directly under the catalog node
Merge branch 'feature/24-remove-cids-class-node-management' into dev
[issue #21] adapted existing and created new options panels so that the preferred usage of the sign service can be set up individually
[issue #21] added username / password configuration for sign service
[issue #21] added alias entry field so that the user may choose the desired alias to use for signing
[issue #21] added new properties to deploy information class so that they can actually be used, removed ant.properties file, as it is not needed anymore, added clerkster client ant task implementation so that the clerkster client can be used from ant, and ultimately rewrote the deploy jar implementation so that the build.xml from the resources will no longer be used, but a new build file is created dynamically every time, with contents depending on the current project configuration
[issue #21] moved new build xml generation to deploy all jars implementation and did some minor adaptions so that this operation now works similar for any number of jars to process, however, the implementation lacks some testing as the clerkster service is not completely setup right now, maybe minor adaptions will have to follow