-1 Jars are ok, but I would suggest to release the bundles to maven with versions *1.2.0*, not *1.2*. It would be more compatible to previous versioning scheme, e. g. https://mvnrepository.com/artifact/org.apache.aries.jmx/org.apache.aries.jmx.blueprint.core/1.1.0
There were also two other bundles released previously and they are missing in this release: - https://mvnrepository.com/artifact/org.apache.aries.jmx/org.apache.aries.jmx - https://mvnrepository.com/artifact/org.apache.aries.jmx/org.apache.aries.jmx.blueprint Should it be like this? 2017-12-30 21:12 GMT+01:00 David Bosschaert <[email protected]>: > Here's my +1 > > David > > On 29 December 2017 at 22:28, David Bosschaert <[email protected] > > > wrote: > > > Hi, > > > > I'm calling a vote on various Aries JMX components > > > > org.apache.aries.jmx.core version 1.1.8 > > org.apache.aries.jmx.core.whiteboard version 1.1.6 > > [ARIES-1630] jmx core fails if configadmin is not present > > > > org.apache.aries.jmx.blueprint.api version 1.2 > > org.apache.aries.jmx.blueprint.core version 1.2 > > [ARIES-1707] BlueprintMetadata.getBlueprintContainer throws inconsistent > > exceptions > > > > org.apache.aries.jmx.whiteboard version 1.2 > > [ARIES-1766] Configure log severity for Whiteboard JMX registration > > exceptions > > [ARIES-1630] jmx core fails if configadmin is not present > > > > Staging repositories (Nexus chose to split it into separate repos): > > https://repository.apache.org/content/repositories/orgapachearies-1120 > > https://repository.apache.org/content/repositories/orgapachearies-1121 > > https://repository.apache.org/content/repositories/orgapachearies-1122 > > > > Please vote: > > > > +1 Approve the release > > -1 Do not approve the release (please explain why) > > > > This vote will be open for at least 72 hours. > > > > Best regards, > > > > David Bosschaert > > > -- Pozdrawiam / Regards, Dominik Przybysz
