lucene-dev mailing list archives

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


Steven Rowe commented on SOLR-3405:

So then i can commit my patch, and we could release tomorrow and maven should work? great!

But i suspect this isnt the case, you are conflating the 'maven build' with 'maven artifacts'

I am not conflating the two; as Benson mentioned, marking those non-mavenized dependencies
as optional in the POMs of modules that need them would allow "maven artifacts" on Maven Central
to be useable.  

The mode of use, however, would be: 

* checkout the tagged release, including dev-tools, from subversion (or maybe from git instead?)
* run {{ant get-maven-poms resolve ; mvn -N -Pbootstrap install}} in order to put the non-mavenized
jars in one's local maven repository
* add *optional* dependencies, using Benson's "groupId-invented/artifactId-invented" coordinates,
to one's own project's POMs.

> 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