On 9/25/14 09:41 , Raymond Auge wrote:
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.
I don't think that is the argument.
Sometimes you have to let some use cases suffer a little bit so that
everyone doesn't pay the conceptual cost of a more complicated API.
Everything you add is something that people will have to debate whether
they need to use it or not...and unfortunately, they end up using it
whether they need to or not.
-> richard
On Thu, Sep 25, 2014 at 9:39 AM, BJ Hargrave <hargr...@us.ibm.com
<mailto:hargr...@us.ibm.com>> wrote:
> From: "Richard S. Hall" <he...@ungoverned.org
<mailto: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_ <mailto:hargr...@us.ibm.com>
office: +1 386 848 1781 <tel:%2B1%20386%20848%201781>
mobile: +1 386 848 3788 <tel:%2B1%20386%20848%203788>
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org <mailto: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
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
