[
https://issues.apache.org/jira/browse/LUCENE-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13604224#comment-13604224
]
Robert Muir commented on LUCENE-3167:
-------------------------------------
{quote}
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.
{quote}
Sure, its always better to ask someone else to take the burden. But I want the
release process to continue to be smooth. The less unnecessary things we take
on the better. The less manual stuff that needs to be checked the better.
We could package up linux RPMs and freebsd ports too, but we just leave this
for downstream people. Could we do it better than those folks since we know the
packaging? I don't know, but I don't really care either. Its better that we
spend our time working on search engines so there are actual releases to put
out there.
Recently I threw up a 4.2.0 release candidate on a wednesday night, by monday
the release was out. By wednesday my friend forwards an email from freebsd
showing they had updated their package already:
http://svnweb.freebsd.org/ports?view=revision&revision=314108 . Thats pretty
damn efficient downstream packaging and a relatively short release cycle. It
required almost no manual effort: I'm insisting that we keep it this way.
So again, this is just like maven. I push back hard, really hard on the issue
because I'm really just saying "don't add a feature without tests and force the
release manager to manually verify the shit works". I said the same things
about maven and someone (thanks Steve!) added automatic testing of maven and
then I never said another word about it.
> 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: [email protected]
For additional commands, e-mail: [email protected]
