lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (JIRA) <>
Subject [jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging
Date Fri, 27 Apr 2012 03:05:50 GMT


Jan Høydahl commented on SOLR-3405:

bq. But you need to realize a lot of software has official releases, they just dont care about
bq. A great example of that is the noggit release. Again i've had a patch up for a month,
and I think it makes our release more clean to depend on this real release, than to have code
copied from apache labs.

I don't think Noggit is a good example. It is written by Yonik and prohibited from releasing
anything since it's part of Apache Labs, so probably noone knows about it. If it rather had
started its life as part of Lucene's source code and later been spawned out as its own project,
it would have gotten more love and care, would have had Javadocs, some documentation etc.
So having Noggit distributed to Maven is as close as asking your colleague to publish it.

I would rather state that most Java libraries *do* care about Maven.
> maven artifacts should be equivalent to binary packaging
> --------------------------------------------------------
>                 Key: SOLR-3405
>                 URL:
>             Project: Solr
>          Issue Type: Task
>          Components: Build
>            Reporter: Robert Muir
>             Fix For: 4.1
> Lets take the commons-csv scenario: 
> * apache-solr-3.5.0 binary distribution contains no actual commons-csv.jar anywhere,
>   in fact it contains no third party jars (the stuff present in solr/lib) at all.
> * binary distribution contains only the jars necessary for *solrj* and *contrib plugins*,
and a solr.war
> I think the maven artifacts should match whats in the binary release (no third party
> inside the .war are "exposed", we just publish the .war itself). This exposes a lot less
surface area.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message