+1 ... used the verify script and there's an error in the output, but a rebuild of the offending javadoc works out fine.
On 5 July 2012 22:20, Holly Cummins <[email protected]> wrote: > I've staged a second release candidate for the Aries 1.0.0 util and > blueprint.api bundles. The difference between this candidate and the > first candidate is that the javadoc for the org.apache.aries.util > bundle documents *all* the classes in that bundle, rather than just > the ones in the util/util project. > > The modules are staged and tagged in > > https://svn.apache.org/repos/asf/aries/tags/org.apache.aries.util-parent-1.0.0/ > https://svn.apache.org/repos/asf/aries/tags/org.apache.aries.blueprint.api-1.0.0/ > > 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 032 mytempdirectory 2>&1 | tee verifyresults.txt > grep FAIL verifyresults.txt > grep ERROR verifyresults.txt > > Failures are reported since there are no SHAs for the > archetype-catalog.xml file in the repository, but I believe this is > acceptable (and I can update the script to filter these out if > everyone else agrees). > > Artifacts are in one staged > repo,https://repository.apache.org/content/repositories/orgapachearies-032/. > > Links to the *.zip files for each module are provided below. > > https://repository.apache.org/content/repositories/orgapachearies-032/org/apache/aries/blueprint/org.apache.aries.blueprint.api/1.0.0/org.apache.aries.blueprint.api-1.0.0-source-release.zip > https://repository.apache.org/content/repositories/orgapachearies-032/org/apache/aries/org.apache.aries.util-parent/1.0.0/org.apache.aries.util-parent-1.0.0-source-release.zip > > The RAT and IANAL build checks passed. > > The vote will be open for 72 hours. > > [ ] +1 > [ ] 0 > [ ] -1
