lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging
Date Fri, 27 Apr 2012 06:34:06 GMT


Robert Muir commented on SOLR-3405:

 If we are worried about supporting the 1-off crazy patched jar, we can point it to something
as crazy as:

Really? Then you can also tell infra to disable the release mirroring system: hey its useless,
we just have svn.

Somehow I don't think that would go over well: they would probably just delete the jar.

We still dont have:
* a way to handle patched dependencies for maven
* a way to handle dependencies that are not in maven
* a packaging system for maven consistent with our other packaging.

In other words: maven is out of control. 

I'm now with Mike, I think we have to get this out from under our PMC and do it some other
> 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