You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by Holly Cummins <ho...@googlemail.com> on 2012/07/18 13:20:24 UTC
[VOTE] Apache Aries jmx bundles release candidate
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
Re: [VOTE] Apache Aries jmx bundles release candidate
Posted by Holly Cummins <ho...@googlemail.com>.
Thanks again to everyone for your votes on these bundles. The vote has
been running for 72 hours. Once again we managed to get enough votes
within the 72 hour window. :)
Here are the results:
[+1] 4 There are 4 binding votes from PMC members (David Bosschaert,
Emily Jiang, Tim Ward, Mark Nuttall).
[0] 0
[-1] 0
I'll promote the release to maven repositories and the Apache download
site. I won't update links on the Aries download page yet,
since we haven't released anything which uses these bundles yet.
Cheers,
Holly
On Fri, Jul 20, 2012 at 6:57 PM, Emily Jiang <em...@googlemail.com> wrote:
> +1
>
> On Fri, Jul 20, 2012 at 11:28 AM, Mark Nuttall <mn...@apache.org> wrote:
>
>> +1
>>
>> Again, everything checks out as per the script.
>>
>> -- Mark
>>
>> On 18 July 2012 12:20, Holly Cummins <ho...@googlemail.com>
>> 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
>> >
>>
>
>
>
> --
> Thanks
> Emily
> =================
> Emily Jiang
> ejiang@apache.org
Re: [VOTE] Apache Aries jmx bundles release candidate
Posted by Emily Jiang <em...@googlemail.com>.
+1
On Fri, Jul 20, 2012 at 11:28 AM, Mark Nuttall <mn...@apache.org> wrote:
> +1
>
> Again, everything checks out as per the script.
>
> -- Mark
>
> On 18 July 2012 12:20, Holly Cummins <ho...@googlemail.com>
> 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
> >
>
--
Thanks
Emily
=================
Emily Jiang
ejiang@apache.org
Re: [VOTE] Apache Aries jmx bundles release candidate
Posted by Mark Nuttall <mn...@apache.org>.
+1
Again, everything checks out as per the script.
-- Mark
On 18 July 2012 12:20, Holly Cummins <ho...@googlemail.com> 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
>
Re: [VOTE] Apache Aries jmx bundles release candidate
Posted by Holly Cummins <ho...@googlemail.com>.
This is the updated list of what's being released. I don't think we
need to revote, since nothing's been re-spun, only removed. However,
this release is still looking for one more vote. :)
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-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.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
On Wed, Jul 18, 2012 at 12:20 PM, Holly Cummins
<ho...@googlemail.com> 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
Re: [VOTE] Apache Aries jmx bundles release candidate
Posted by Holly Cummins <ho...@googlemail.com>.
It looks to me like jmx-core has the same issue, unfortunately, and
it's already been released. However, I agree we should fix this where
we can, so I'll remove jmx-bundle from the release, roll all the tags
back, and fix up its pom. I don't think that will push back the date
when we have the whole component released and can move to jmx-next.
Good spot, Tim. Thanks.
On Fri, Jul 20, 2012 at 7:41 AM, David Bosschaert
<da...@gmail.com> wrote:
> On 19 July 2012 23:05, Timothy Ward <ti...@apache.org> wrote:
>>
>> 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!
>
> Main reason I'd like to see this one out is to get a release of the
> 'old' JMX. I implemented 'jmx-next' in the sandbox already, but we
> agreed that it would be good to get a release of what was there before
> upgrading.
>
> So I'm not sure it's needed to fix the old JMX, as it will soon be
> superceded anyway. But I will look at the jmx-bundle in jmx-next to
> ensure that it uses version ranges.
>
> In any case I'm fine with either option if someone has time to fix
> this issue in the old JMX...
>
> Cheers,
>
> David
Re: [VOTE] Apache Aries jmx bundles release candidate
Posted by David Bosschaert <da...@gmail.com>.
On 19 July 2012 23:05, Timothy Ward <ti...@apache.org> wrote:
>
> 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!
Main reason I'd like to see this one out is to get a release of the
'old' JMX. I implemented 'jmx-next' in the sandbox already, but we
agreed that it would be good to get a release of what was there before
upgrading.
So I'm not sure it's needed to fix the old JMX, as it will soon be
superceded anyway. But I will look at the jmx-bundle in jmx-next to
ensure that it uses version ranges.
In any case I'm fine with either option if someone has time to fix
this issue in the old JMX...
Cheers,
David
RE: [VOTE] Apache Aries jmx bundles release candidate
Posted by Timothy Ward <ti...@apache.org>.
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: david.bosschaert@gmail.com
> Date: Wed, 18 Jul 2012 12:58:44 +0100
> Subject: Re: [VOTE] Apache Aries jmx bundles release candidate
> To: dev@aries.apache.org
>
> +1 (Yay!)
>
> David
>
> On 18 July 2012 12:20, Holly Cummins <ho...@googlemail.com> 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
Re: [VOTE] Apache Aries jmx bundles release candidate
Posted by David Bosschaert <da...@gmail.com>.
+1 (Yay!)
David
On 18 July 2012 12:20, Holly Cummins <ho...@googlemail.com> 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