check upload repository for version presence support patches by allowing to upload artifacts with secondary pom and different groupId add repositories and pluginRepositories to pom upon release, so that the resulting code is standalone buildable auto-select settings based on some configuration implement "dry" mode as full release on local vcs + local deployment validate changes.xml against schema check that tag base exists support rollback (undo/revert whatever possible) implement one-pass (single build) sequence support uploading logs and intermediate files support manual signing in upload phase - waiting for signed files in a share, using a simple handshake support for strict version format settings.xml (target repo, policies etc.) must be selected based on some criteria (version level, vcs repo, groupId) update public documentation on release introduce properties to hold various data from the prepare step implement a plugin that adds changes to the reference documentation introduced vcs/@type to indicate vcs type - svn, cvs, git, ... simplified installation - using buildbox installer just like in buildozer implemented support for option "--pom-change", currently allowing only to modify url commit prefix is just "[releasator]" whole changes module merged right into releasator, to simplify development in current stage implemented support for option "--changes-item-simple", allowing to add item element on the fly converted to args-inject style slightly simplified implementation removed step "package" as it seems to be useless implemented support for option --preload-repository, to improve performance - especially for testing groupId of changes.xml and toplevel pom must match reorganized tests so that it's easier to add more test scenarios created few pages for mvn site removed bash version of releasator fixed bad version number generation in submodules of multimodule project added result checking with xmlunit eliminated any use of CommandLineExec eliminated the experimental part, it resides in branches now to be available for further development separately fixed version obtaining support getting version of maven 2.2.0 and higher scm is added to every single pom, and removed afterwards tagged pom.xml contained -SNAPSHOT in its name provide correct maven version refactored scm handling to get better state for resolving related bugs list of artifact by modules is now added refactored to fully use changes api prefix "scm:svn:" is no longer mandatory suppressed experimental part to reduce size of produced jar support for changing artifact name to the one in changes.xml during release - allows to have distinct artifactIds in pom.xml during development translated releasator from bash to java workarround - retry release:prepare after first fail and svn update generated release tag was bad when using non-top trunk paths fail when no-namespaced pom.xml is detected in module tree more logical directory name; added pom name as last parameter strict version format checking pom names are expanded before release and collapsed afterwards project started