I've staged a release candidate for the next set of jmx bundles. This round gets *almost* the whole jmx component released - just the blueprint uber-bundle and the itests to go.
WHAT'S BEEN RELEASED? The modules are staged and tagged as follows: jmx-blueprint-core: https://svn.apache.org/repos/asf/aries/tags/org.apache.aries.jmx.blueprint.core-1.0.0 jmx-bundle: https://svn.apache.org/repos/asf/aries/tags/org.apache.aries.jmx-1.0.0 jmx-core-whiteboard: https://svn.apache.org/repos/asf/aries/tags/org.apache.aries.jmx.core.whiteboard-1.0.0 jmx-whiteboard: https://svn.apache.org/repos/asf/aries/tags/org.apache.aries.jmx.whiteboard-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 065 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-065/. Links to the *.zip files for each module are provided below: https://repository.apache.org/content/repositories/orgapachearies-065/org/apache/aries/jmx/org.apache.aries.jmx.blueprint.core/1.0.0/org.apache.aries.jmx.blueprint.core-1.0.0-source-release.zip https://repository.apache.org/content/repositories/orgapachearies-065/org/apache/aries/jmx/org.apache.aries.jmx/1.0.0/org.apache.aries.jmx-1.0.0-source-release.zip https://repository.apache.org/content/repositories/orgapachearies-065/org/apache/aries/jmx/org.apache.aries.jmx.core.whiteboard/1.0.0/org.apache.aries.jmx.core.whiteboard-1.0.0-source-release.zip https://repository.apache.org/content/repositories/orgapachearies-065/org/apache/aries/jmx/org.apache.aries.jmx.whiteboard/1.0.0/org.apache.aries.jmx.whiteboard-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. There are also some spurious RAT warnings for NOTICE.vm files. The vote will be open for 72 hours, closing Saturday lunchtime. [ ] +1 [ ] 0 [ ] -1
