lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging
Date Thu, 26 Apr 2012 22:36:48 GMT


Michael McCandless commented on SOLR-3405:

bq. I just resolved SOLR-3411 as "Not a Problem".

OK thanks Steve.  I'm glad it's not a real problem.

bq. From the Apache board perspective, I suspect that this would be viewed as a distinction
without a difference;

True, but I think that's OK.  It's a compromise.

bq. The PMC is supposed to only be voting on source releases anyway, right?

Legally, yes, but in practice, we are also testing and pushing out the
convenience binaries (and, Maven's artifacts) at the same time.  They
are all read-only once published.
> 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