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 Thu, 26 Apr 2012 22:36:48 GMT


Robert Muir commented on SOLR-3405:

It's been too easy to include questionable libs or non-released libs, and that's the real
problem if you ask me.
So publishing to mvn-repo actually keeps us accountable in legally being good Apache citizens
as well as shipping higher quality, more stable stuff. 

Thats bullshit. Being in maven repositories doesn't make anything more legal. 

Requiring that all dependencies be in maven harms software projects:
* it prevents good features from being added, for example the most popular Tika issue (outlook
support) is just hung on this stupid stuff (TIKA-623)
* it encourages buggy software. Perhaps its "conventional" that software projects just pass
the blame down along, but if we have bugs that break our release we should make our release
work instead of passing blame.

It's a Good Thing™ that Noggit got its release.

I agree. I upload my patch to start using it nearly a month ago. Its too bad no maven supporters
have done anything to make it accessible via maven.

The fact its a real release is good, and the patch is good. Its time to commit it.

> 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