lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benson Margulies (JIRA)" <>
Subject [jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging
Date Tue, 24 Apr 2012 19:59:34 GMT


Benson Margulies commented on SOLR-3405:

Rob, my experience here is that you pose a very specific question (e.g. do _war_ files force
public dependencies) and when I answer it, you switch the subject to a different question.
Not an illegitimate or uninteresting question, but a different question.

The instantaneous effect of committing that patch will be to break the convenience maven build
until someone else does something else. If noggit is out there on central, then the fix will
be a trivial adjustment to the template pom. If it's not, then my suggestion for a relatively
painless solution is 

1) to add a CSV file to the top of the tree, where each line consists of:


2) To add each one as a dependency to the corresponding pom with <optional>true</optional>

3) implement code in the 'ant get-maven-poms' target to download them and run maven install:install-file
on them using the information in the CSV.

If you all *want* one of these to be a non-optional dependency, then it's a job for someone
to coax it onto central, probably via ossrh. That's work, but it doesn't have to happen in
a hurry.

The CXF file could be created by scraping the ivy files, but that seems a lot of work.

Steve, of course, gets first dibs on solving the problem, and he might not like my proposal.

> 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.0
> 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