You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Bob Kerns (JIRA)" <ji...@apache.org> on 2013/03/15 23:46:15 UTC
[jira] [Commented] (LUCENE-3167) Make lucene/solr a OSGI bundle
through Ant
[ https://issues.apache.org/jira/browse/LUCENE-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13603944#comment-13603944 ]
Bob Kerns commented on LUCENE-3167:
-----------------------------------
To respond to Robert Muir question about why you (people who work on search engines) should do it.
I see two reasons:
1) People downstream may not KNOW how to do it, or have the time, or want to make all the possible choices over again, when people who know the engine and its packaging are more capable of sorting all that stuff out properly. I didn't get it right the first time (thank's to screwing up with) and now have to repeat. It's taken you guys a year and a half; obviously not trivial!
2) People downstream would like to do it in a way that does not outright conflict with other people downstream doing it! This is really a big, big deal. If I package it, and put it in a product, and someone else packages it, and puts it in their product -- like for example, the Eclipse foundation -- bad things can happen. I can't even predict WHAT bad things might happen, because I don't know what we might do differently. We could get lucky and not screw each other, but do I really want to trust the other guy -- ALL the other guys -- to do it right? Or do I do something like rename the packages to avoid any potential insanity? That has other problems...
Bottom line? I'd rather you guys do it -- even if you don't do a good job of it. Even if I could do it 10x better, it is still 100x better for you to do it.
Maybe I'll be able to help later, once I've sorted out my immediate needs. But in the meantime, I just wanted to let you know the effort is appreciated -- even if it doesn't turn out perfectly.
Thanks.
> Make lucene/solr a OSGI bundle through Ant
> ------------------------------------------
>
> Key: LUCENE-3167
> URL: https://issues.apache.org/jira/browse/LUCENE-3167
> Project: Lucene - Core
> Issue Type: New Feature
> Environment: bndtools
> Reporter: Luca Stancapiano
> Attachments: LUCENE-3167_20130108.patch, LUCENE-3167.patch, LUCENE-3167.patch, LUCENE-3167.patch, lucene_trunk.patch, lucene_trunk.patch
>
>
> We need to make a bundle thriugh Ant, so the binary can be published and no more need the download of the sources. Actually to get a OSGI bundle we need to use maven tools and build the sources. Here the reference for the creation of the OSGI bundle through Maven:
> https://issues.apache.org/jira/browse/LUCENE-1344
> Bndtools could be used inside Ant
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: [jira] [Commented] (LUCENE-3167) Make lucene/solr a OSGI bundle
through Ant
Posted by Erick Erickson <er...@gmail.com>.
bq: Maybe I'll be able to help later, once I've sorted out my immediate
needs.
Well, that pretty much describes everyone here I think. If you can break
some time loose to make this happen and, as Robert points out, not increase
the burden on the RM I think it would be a valuable addition.
If _your_ workplace would benefit from having this happen, perhaps you can
persuade them to assign you the task of fixing this upstream. i.e. in Solr?
That's often the way things work in open source, people/companies address
their own pain points and push it upstream where not only do others
benefit, they also have the opportunity to help maintain it. Which can
decrease their costs the next time around.
You're already having to do it for the second time, it seems to me a case
can be made to your management to do this once and push it upstream.
But it _can't_ add to the RMs burden if we want to get releases out
regularly. Adding error-prone work is going to meet resistance I suspect.
Well, it already has.
Best
Erick
On Fri, Mar 15, 2013 at 6:46 PM, Bob Kerns (JIRA) <ji...@apache.org> wrote:
>
> [
> https://issues.apache.org/jira/browse/LUCENE-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13603944#comment-13603944]
>
> Bob Kerns commented on LUCENE-3167:
> -----------------------------------
>
> To respond to Robert Muir question about why you (people who work on
> search engines) should do it.
>
> I see two reasons:
>
> 1) People downstream may not KNOW how to do it, or have the time, or want
> to make all the possible choices over again, when people who know the
> engine and its packaging are more capable of sorting all that stuff out
> properly. I didn't get it right the first time (thank's to screwing up
> with) and now have to repeat. It's taken you guys a year and a half;
> obviously not trivial!
>
> 2) People downstream would like to do it in a way that does not outright
> conflict with other people downstream doing it! This is really a big, big
> deal. If I package it, and put it in a product, and someone else packages
> it, and puts it in their product -- like for example, the Eclipse
> foundation -- bad things can happen. I can't even predict WHAT bad things
> might happen, because I don't know what we might do differently. We could
> get lucky and not screw each other, but do I really want to trust the other
> guy -- ALL the other guys -- to do it right? Or do I do something like
> rename the packages to avoid any potential insanity? That has other
> problems...
>
> Bottom line? I'd rather you guys do it -- even if you don't do a good job
> of it. Even if I could do it 10x better, it is still 100x better for you to
> do it.
>
> Maybe I'll be able to help later, once I've sorted out my immediate needs.
> But in the meantime, I just wanted to let you know the effort is
> appreciated -- even if it doesn't turn out perfectly.
>
> Thanks.
>
> > Make lucene/solr a OSGI bundle through Ant
> > ------------------------------------------
> >
> > Key: LUCENE-3167
> > URL: https://issues.apache.org/jira/browse/LUCENE-3167
> > Project: Lucene - Core
> > Issue Type: New Feature
> > Environment: bndtools
> > Reporter: Luca Stancapiano
> > Attachments: LUCENE-3167_20130108.patch, LUCENE-3167.patch,
> LUCENE-3167.patch, LUCENE-3167.patch, lucene_trunk.patch, lucene_trunk.patch
> >
> >
> > We need to make a bundle thriugh Ant, so the binary can be published and
> no more need the download of the sources. Actually to get a OSGI bundle we
> need to use maven tools and build the sources. Here the reference for the
> creation of the OSGI bundle through Maven:
> > https://issues.apache.org/jira/browse/LUCENE-1344
> > Bndtools could be used inside Ant
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
> administrators
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>