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 Wed, 25 Apr 2012 17:46:22 GMT


Michael McCandless commented on SOLR-3405:

I have stated that I think we shouldn't release maven if its "different" than our
other packaging because I think that causes it to be more of a mystery.

you can s/maven/rpm/ and i feel the same way about all of this: these are
just different packaging formats but I think the underlying products we release should be
the same.

I think the maven artifacts should not be built from the source tree, they should instead
be built from the binary release (e.g. unzipping the .zip + augmenting with poms).


This would make me more comfortable with our Maven artifacts...

Do we know of any downstream repos that package up Solr?  Do they
also match the artifacts in our binary release?

Could such a stronger decoupling of "our releases" and "pushing
to Maven Central" also mean that issues like SOLR-2770 (where, I
think, only the Maven POMs were messed up for the 3.4.0 release) might
be correctable in the future w/o having to cut another "real"

> 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