You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by Gert Vanthienen <ge...@gmail.com> on 2012/05/25 22:37:32 UTC
Re: Releasing OSGi bundles of other Apache projects....
L.S.,
Thanks to Dan for pointing this out (and sorry for the horribly late reply,
while closing the bundles vote, a little bell started ringing in my head
about this thread) - with our latest bundles release containing another set
of bundles for some other Apache communities (i.e. Hadoop, Lucene, Qpid,
Solr), how about we start doing the right thing by reaching out to these
communities and checking if they are interested in adding OSGi support to
their own artifacts and perhaps see if we can help out with that (or if
they're happy to keep things the way they are now, that's fine too, I
guess, but at least they're aware that we're repackaging their artifacts).
So basically, I'm looking for volunteers (aren't we always?) here to help
with this or perhaps we even have people that are already involved in these
particular communities as well
Regards,
Gert Vanthienen
------------------------
FuseSource
Web: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
On Mon, Mar 26, 2012 at 2:24 PM, Jean-Baptiste Onofré <jb...@nanthrax.net>wrote:
> Hi Dan,
>
> First of all, thanks to inform us about the board discussion.
>
> I think we are all agree that it's not a perfect approach. The big
> advantage of this approach is that we don't have to wait a project release.
> We can fix OSGi statements issues really quickly and we are not "blocker"
> and can deliver bundles quickly.
>
> Your statement looks good to me.
>
> In addition, I propose:
> - to release the ServiceMix pending bundles (we have a set of 13 bundles
> to release). If no opposition, I will prepare the release tonight.
> - to iterate on all ServiceMix bundles, and for all active projects, open
> a issue tracker and provide a patch to add OSGi statement. It may be a long
> process but I'm volunteer to tackle that.
>
>
> Regards
> JB
>
> On 03/21/2012 08:26 PM, Daniel Kulp wrote:
>
>>
>> Due to some concerns from one project, the board had a discussion on
>> todays
>> call about guidelines for projects to release code from other projects
>> namespaces (includes java package names). The general opinion is that
>> such
>> practices should be discouraged. At the very least, doing so should
>> require communication with the original project to make sure there are no
>> objections to the release, to encourage them to look at the proposed
>> release, and hopefully even get them to do the release themselves.
>>
>> This, of course, has an effect on the ServiceMix bundle releases. For
>> cases
>> where ServiceMix re-bundles another Apache project, we need to make sure
>> we
>> work with the original community to make sure they are OK with the
>> addition
>> of the OSGi manifest and the forms they are in.
>>
>> With my newly appointed BoD hat on, I've taken on the action item to
>> figure
>> out a suggested policy to accomplish this and add that to:
>>
>> http://www.apache.org/dev/**release.html<http://www.apache.org/dev/release.html>
>>
>> Since the SMX folks are highly involved in such things, I'd love their
>> input. My initial thought is something like:
>>
>> ------------------------------**------------------
>>
>> * Can Apache Projects release artifacts that may affect the "namespaces"
>> of
>> other Apache Project? (example is releasing a jar that contains .class
>> files in the packages of another Apache project, even if the classes are
>> in
>> a jar with a different name, maven groupId/artifactId, etc...)
>>
>> Such releases are strongly discouraged. It's much better to work with
>> the
>> original project to have them create a release that would meet the needs
>> of
>> your project. However, projects may not be in a position to create
>> needed
>> releases in a timely manner so this is not always possible. The
>> preferred solution, if possible, is to import the code into your own
>> projects namespace to not conflict with the original project. Use of
>> tools
>> like shade or jarjar or similar can help with that. However, that's also
>> not always practical or possible. (example: OSGi manifest additions) In
>> that case, a release can be made by another project as long as there are
>> no
>> objections (by lazy consensus) by the original project.
>>
>> ------------------------------**------------------
>>
>> Does anyone have any additional thoughts? Again, the idea is to work
>> with
>> the original communities to make sure we're not doing anything against
>> their
>> wishes.
>>
>>
>>
>>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: Releasing OSGi bundles of other Apache projects....
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Just an update, I'm preparing a new bundles release. For each bundle in
this release, I also prepared a patch that I will propose to the
projects, creating a Jira if required.
@Dan, maybe you can mention to the board that the ServiceMix team
started to work as requested.
@team, I will send a summary on the submitted patches.
Regards
JB
On 05/30/2012 02:14 AM, Freeman Fang wrote:
> Yeah, +1 we should link to the corresponding JIRA issue in the target
> project, just done it for hadoop[1] as I just add hadoop-core 1.0.3
> bundle[2].
> Feel free to comment on that hadoop issue[1] if you want.
> [1]https://issues.apache.org/jira/browse/HADOOP-8446
> [2]https://issues.apache.org/jira/browse/SMX4-1147
>
> Freeman
> On 2012-5-29, at 下午4:14, Gert Vanthienen wrote:
>
>> Hey Ioannis,
>>
>>
>> I agree we should probably always have been doing that - not sure we're
>> consistently doing that at the moment, though (I'm sure I myself have
>> created a few bundles in the past and have not always pursued things all
>> the way through, so it's very likely that I'm not alone here)
>>
>> How about we just add a link to the corresponding JIRA issue in the
>> target
>> project to our bundle creation issue? That way, we will have an easy way
>> to see what the status of the effort is in the target community and can
>> decide (in cooperation with the other community) on whether or not to go
>> ahead with releasing our own bundles depending on how soon they are
>> able to
>> deliver an OSGi-ready artifact. That way, we do have a more formal
>> link to
>> what happens in the other community and we can still decide on a case by
>> case basis what the best strategy is.
>>
>>
>> Regards,
>>
>> Gert Vanthienen
>> ------------------------
>> FuseSource
>> Web: http://fusesource.com
>> Blog: http://gertvanthienen.blogspot.com/
>>
>>
>> On Sat, May 26, 2012 at 9:09 PM, Ioannis Canellos <io...@gmail.com>
>> wrote:
>>
>>>>
>>>> how about we start doing the right thing by reaching out to these
>>>> communities and checking if they are interested in adding OSGi
>>>> support to
>>>> their own artifacts
>>>
>>>
>>> Aren't we already doing so?
>>> I would have though that most of the people creating bundles, in most
>>> cases
>>> try to contribute the OSGi support to the target project first (just to
>>> avoid the maintenance overhead).
>>>
>>> There are a lot of cases though, were the target community takes really
>>> long to apply the patch, even longer to make a release containing the
>>> patch. Not to mention cases were they are not that "cooperative".
>>>
>>> So I'd fell so much better if we had a formal way of communicating our
>>> intention to provide OSGi support either as contribution or as a
>>> ServiceMix
>>> bundle. And also some guidelines of what is a reasonable period we
>>> should
>>> wait for a response / release before providing our bundle. "Lazy
>>> consensus"
>>> seems a bit subjective.
>>>
>>> --
>>> *Ioannis Canellos*
>>> *
>>> FuseSource <http://fusesource.com>
>>>
>>> **
>>> Blog: http://iocanel.blogspot.com
>>> **
>>> Twitter: iocanel
>>> *
>>>
>
> ---------------------------------------------
> Freeman Fang
>
> FuseSource
> Email:ffang@fusesource.com
> Web: fusesource.com
> Twitter: freemanfang
> Blog: http://freemanfang.blogspot.com
> http://blog.sina.com.cn/u/1473905042
> weibo: http://weibo.com/u/1473905042
>
>
>
>
>
>
>
>
>
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Releasing OSGi bundles of other Apache projects....
Posted by Freeman Fang <fr...@gmail.com>.
Yeah, +1 we should link to the corresponding JIRA issue in the target
project, just done it for hadoop[1] as I just add hadoop-core 1.0.3
bundle[2].
Feel free to comment on that hadoop issue[1] if you want.
[1]https://issues.apache.org/jira/browse/HADOOP-8446
[2]https://issues.apache.org/jira/browse/SMX4-1147
Freeman
On 2012-5-29, at 下午4:14, Gert Vanthienen wrote:
> Hey Ioannis,
>
>
> I agree we should probably always have been doing that - not sure
> we're
> consistently doing that at the moment, though (I'm sure I myself have
> created a few bundles in the past and have not always pursued things
> all
> the way through, so it's very likely that I'm not alone here)
>
> How about we just add a link to the corresponding JIRA issue in the
> target
> project to our bundle creation issue? That way, we will have an
> easy way
> to see what the status of the effort is in the target community and
> can
> decide (in cooperation with the other community) on whether or not
> to go
> ahead with releasing our own bundles depending on how soon they are
> able to
> deliver an OSGi-ready artifact. That way, we do have a more formal
> link to
> what happens in the other community and we can still decide on a
> case by
> case basis what the best strategy is.
>
>
> Regards,
>
> Gert Vanthienen
> ------------------------
> FuseSource
> Web: http://fusesource.com
> Blog: http://gertvanthienen.blogspot.com/
>
>
> On Sat, May 26, 2012 at 9:09 PM, Ioannis Canellos
> <io...@gmail.com> wrote:
>
>>>
>>> how about we start doing the right thing by reaching out to these
>>> communities and checking if they are interested in adding OSGi
>>> support to
>>> their own artifacts
>>
>>
>> Aren't we already doing so?
>> I would have though that most of the people creating bundles, in
>> most cases
>> try to contribute the OSGi support to the target project first
>> (just to
>> avoid the maintenance overhead).
>>
>> There are a lot of cases though, were the target community takes
>> really
>> long to apply the patch, even longer to make a release containing the
>> patch. Not to mention cases were they are not that "cooperative".
>>
>> So I'd fell so much better if we had a formal way of communicating
>> our
>> intention to provide OSGi support either as contribution or as a
>> ServiceMix
>> bundle. And also some guidelines of what is a reasonable period we
>> should
>> wait for a response / release before providing our bundle. "Lazy
>> consensus"
>> seems a bit subjective.
>>
>> --
>> *Ioannis Canellos*
>> *
>> FuseSource <http://fusesource.com>
>>
>> **
>> Blog: http://iocanel.blogspot.com
>> **
>> Twitter: iocanel
>> *
>>
---------------------------------------------
Freeman Fang
FuseSource
Email:ffang@fusesource.com
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
http://blog.sina.com.cn/u/1473905042
weibo: http://weibo.com/u/1473905042
Re: Releasing OSGi bundles of other Apache projects....
Posted by Gert Vanthienen <ge...@gmail.com>.
Hey Ioannis,
I agree we should probably always have been doing that - not sure we're
consistently doing that at the moment, though (I'm sure I myself have
created a few bundles in the past and have not always pursued things all
the way through, so it's very likely that I'm not alone here)
How about we just add a link to the corresponding JIRA issue in the target
project to our bundle creation issue? That way, we will have an easy way
to see what the status of the effort is in the target community and can
decide (in cooperation with the other community) on whether or not to go
ahead with releasing our own bundles depending on how soon they are able to
deliver an OSGi-ready artifact. That way, we do have a more formal link to
what happens in the other community and we can still decide on a case by
case basis what the best strategy is.
Regards,
Gert Vanthienen
------------------------
FuseSource
Web: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
On Sat, May 26, 2012 at 9:09 PM, Ioannis Canellos <io...@gmail.com> wrote:
> >
> > how about we start doing the right thing by reaching out to these
> > communities and checking if they are interested in adding OSGi support to
> > their own artifacts
>
>
> Aren't we already doing so?
> I would have though that most of the people creating bundles, in most cases
> try to contribute the OSGi support to the target project first (just to
> avoid the maintenance overhead).
>
> There are a lot of cases though, were the target community takes really
> long to apply the patch, even longer to make a release containing the
> patch. Not to mention cases were they are not that "cooperative".
>
> So I'd fell so much better if we had a formal way of communicating our
> intention to provide OSGi support either as contribution or as a ServiceMix
> bundle. And also some guidelines of what is a reasonable period we should
> wait for a response / release before providing our bundle. "Lazy consensus"
> seems a bit subjective.
>
> --
> *Ioannis Canellos*
> *
> FuseSource <http://fusesource.com>
>
> **
> Blog: http://iocanel.blogspot.com
> **
> Twitter: iocanel
> *
>
Re: Releasing OSGi bundles of other Apache projects....
Posted by Ioannis Canellos <io...@gmail.com>.
>
> how about we start doing the right thing by reaching out to these
> communities and checking if they are interested in adding OSGi support to
> their own artifacts
Aren't we already doing so?
I would have though that most of the people creating bundles, in most cases
try to contribute the OSGi support to the target project first (just to
avoid the maintenance overhead).
There are a lot of cases though, were the target community takes really
long to apply the patch, even longer to make a release containing the
patch. Not to mention cases were they are not that "cooperative".
So I'd fell so much better if we had a formal way of communicating our
intention to provide OSGi support either as contribution or as a ServiceMix
bundle. And also some guidelines of what is a reasonable period we should
wait for a response / release before providing our bundle. "Lazy consensus"
seems a bit subjective.
--
*Ioannis Canellos*
*
FuseSource <http://fusesource.com>
**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*