Hi, All four build fine, and the poms/manifests for three of them are fine. Unfortunately the manifest for jmx-bundle doesn't use version ranges in most of its imports:
Import-Package: javax.management,javax.management.openmbean,org.apache .aries.util;version="[1.0,2)",org.osgi.framework;version="1.5.0",org. osgi.jmx;version="1.0.0",org.osgi.jmx.framework;version="1.5.0",org.o sgi.jmx.service.cm;version="1.3.0",org.osgi.jmx.service.permissionadm in;version="1.2.0",org.osgi.jmx.service.provisioning;version="1.2.0", org.osgi.jmx.service.useradmin;version="1.1.0",org.osgi.service.cm;re solution:=optional;version="1.3.0",org.osgi.service.log;version="[1.3 ,2)",org.osgi.service.packageadmin;version="[1.2,2)",org.osgi.service .permissionadmin;resolution:=optional;version="1.2.0",org.osgi.servic e.provisioning;resolution:=optional;version="1.2.0",org.osgi.service. startlevel;version="[1.1,2)",org.osgi.service.useradmin;resolution:=o ptional;version="1.1.0",org.osgi.util.tracker;version="[1.4,2)" I think all of these are set in the pom - I'm not sure if the right answer is to remove all of the versions in the <aries.osgi.import> tag and let the bundle plugin figure it out, or to put in the right version ranges. The former is more maintainable (and nicer) but might not give the intended result. I'm sure we all agree this is a showstopper. If I can +1 the three other bundles and ask for the jmx-bundle to be fixed/respun then great, otherwise I'm afraid David will have to wait a little longer. Sorry! Regards, Tim Ward ------------------- Apache Aries PMC member & Enterprise OSGi advocate Enterprise OSGi in Action (http://www.manning.com/cummins) ------------------- > From: [email protected] > Date: Wed, 18 Jul 2012 12:58:44 +0100 > Subject: Re: [VOTE] Apache Aries jmx bundles release candidate > To: [email protected] > > +1 (Yay!) > > David > > On 18 July 2012 12:20, Holly Cummins <[email protected]> wrote: > > 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
