I've staged a release candidate for the a few miscellaneous Aries jars, blueprint-parser and eba-maven-plugin.
WHAT'S BEEN RELEASED? The modules are staged and tagged as follows: blueprint-parser: https://svn.apache.org/repos/asf/aries/tags/blueprint-parser-1.0.0/ eba-maven-plugin: https://svn.apache.org/repos/asf/aries/tags/eba-maven-plugin-1.0.0/ VERIFYING THE RELEASE Instructions for verifying the release are at http://aries.apache.org/development/verifyingrelease.html. Alternately, cut and paste the following to run a full check: wget --no-check-certificate https://svn.apache.org/repos/asf/aries/scripts/verify_staged_release.sh chmod a+x verify_staged_release.sh ./verify_staged_release.sh 051 mytempdirectory 2>&1 | tee verifyresults.txt grep FAIL verifyresults.txt grep ERROR verifyresults.txt SOURCE ZIPS Artifacts are in one staged repo, https://repository.apache.org/content/repositories/orgapachearies-051/. Links to the *.zip files for each module are provided below: https://repository.apache.org/content/repositories/orgapachearies-051/org/apache/aries/eba-maven-plugin/1.0.0/eba-maven-plugin-1.0.0-source-release.zip https://repository.apache.org/content/repositories/orgapachearies-051/org/apache/aries/blueprint/blueprint-parser/1.0.0/blueprint-parser-1.0.0-source-release.zip The RAT and IANAL build checks passed. Note that, although RAT is configured to ignore *.MF and other files that do not require the ASF licence, theses files are still reported incorrectly as RAT failures. As before, archetype-catalog.xml files fail the SHA checks but probably shouldn't be checked. The vote will be open for 72 hours, closing Wednesday evening. [ ] +1 [ ] 0 [ ] -1 Holly
