lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-3405) maven artifacts should be equivalent to binary packaging
Date Thu, 26 Apr 2012 14:50:16 GMT

    [ https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262650#comment-13262650
] 

David Smiley commented on SOLR-3405:
------------------------------------

There is a lot of discussion here and I don't want to complicate anything.

What I do want to say, as a user of Maven and of Lucene/Solr's Maven artifacts specifically,
is that it is *awesome* that I can have a maven based project that has a dependency on the
Solr test framework and it just works thanks to all of the dependency resolution of Maven,
and thanks to Maven and IDE integration, IntelliJ grabs all the source which helps tremendously
-- its automatic.  My code can either be strictly a SolrJ client or it can extend Lucene or
Solr.  I don't want this to go away.  Once upon a time it didn't work or the dependencies
metadata declared were poor and I did my part in making it work well (and certainly Steve
did too).
                
> maven artifacts should be equivalent to binary packaging
> --------------------------------------------------------
>
>                 Key: SOLR-3405
>                 URL: https://issues.apache.org/jira/browse/SOLR-3405
>             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
jars 
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message