Artifacts as API is a giant kludge. Furthermore adding/removing capabilities to/from the system is not specific to this use case, it could be used for a great many things.
Perhaps there's a better way without adding more API, resolver hook, etc, but I have repeat: artifacts are not API. On Thu, Sep 25, 2014 at 9:39 AM, BJ Hargrave <hargr...@us.ibm.com> wrote: > > From: "Richard S. Hall" <he...@ungoverned.org> > > > I would think that for such special use cases, generating a bundle > > would suffice, since it can easily be done at run time. Why keep > > adding features for more and more specialized use cases when they > > can be accomplished already? > > +1 > > > -- > > *BJ Hargrave* > Senior Technical Staff Member, IBM > OSGi Fellow and CTO of the *OSGi Alliance* <http://www.osgi.org/> > *hargr...@us.ibm.com* <hargr...@us.ibm.com> > > office: +1 386 848 1781 > mobile: +1 386 848 3788 > > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > https://mail.osgi.org/mailman/listinfo/osgi-dev > -- *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> (@rotty3000) Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> (@Liferay)
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
