aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominik Przybysz <alien11...@gmail.com>
Subject Re: [VOTE] Release Aries JMX components (take 2)
Date Tue, 02 Jan 2018 17:32:59 GMT
It's ok for me if we stop releasing jmx-blueprint-bundle and jmx-bundle,
but then I think we should also remove those sub projects from aries repo.

My vote is not a 'veto'.

2018-01-02 18:25 GMT+01:00 David Bosschaert <david.bosschaert@gmail.com>:

> Hi Dominik,
>
> Nothing has changed in jmx-api, that's why I didn't release that one.
>
> The jmx-bundle and jmx-blueprint-bundle you are referring to are 'uber'
> bundles that are a combination of other bundles. Since we agreed on this
> list to do modular releases for Aries JMX [1] these uber bundles aren't
> really compatible with that... I guess they can still be released but they
> would need some sort of aggregate version number.
>
> Personally I don't see a strong reason to release these aggregate bundles,
> as using them is really an OSGi anti-pattern IMHO. However if anyone feels
> that these should be released they can be released separately.
>
> @Dominik, I hope your -1 is not a 'veto', if it is please let us know.
> Otherwise I think we can continue this release vote and, as mentioned those
> bundles can still be released later.
>
> Best regards,
>
> David
>
> [1]
> https://lists.apache.org/thread.html/1f870e20c5f13da6dd0995f501e9ee
> 279a30532efa77125203307ecd@%3Cdev.aries.apache.org%3E
>
> On 2 January 2018 at 16:17, Dominik Przybysz <alien11689@gmail.com> wrote:
>
> > -1
> >
> > Versions are ok, but you have still missed two bundles which also should
> be
> > released together in this release.
> > I saw your message that nothing in them wasn't changed but they shouldn't
> > change - they are bundles which shade those ones you have released:
> > https://github.com/apache/aries/blob/trunk/jmx/jmx-
> > blueprint-bundle/pom.xml
> > https://github.com/apache/aries/blob/trunk/jmx/jmx-bundle/pom.xml
> >
> > 2018-01-02 16:05 GMT+01:00 Francois Papon <francois.papon@openobject.fr>
> :
> >
> > > +1 (non-binding)
> > >
> > > François
> > >
> > >
> > > Le 02/01/2018 à 17:10, David Bosschaert a écrit :
> > > > Hi all,
> > > >
> > > > I'm calling a vote on various Aries JMX components, now with versions
> > > > updated from 1.2 to 1.2.0.
> > > > The org.apache.aries.jmx.api component has not changed since the last
> > > > release and is thus not included in this set.
> > > >
> > > > 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.0
> > > > org.apache.aries.jmx.blueprint.core version 1.2.0
> > > > [ARIES-1707] BlueprintMetadata.getBlueprintContainer throws
> > inconsistent
> > > > exceptions
> > > >
> > > > org.apache.aries.jmx.whiteboard version 1.2.0
> > > > [ARIES-1766] Configure log severity for Whiteboard JMX registration
> > > > exceptions
> > > > [ARIES-1630] jmx core fails if configadmin is not present
> > > >
> > > > Staging repository:
> > > > https://repository.apache.org/content/repositories/
> orgapachearies-1123
> > > >
> > > > 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
> >
>



-- 
Pozdrawiam / Regards,
Dominik Przybysz

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message