[
https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262781#comment-13262781
]
David Smiley commented on SOLR-3405:
------------------------------------
Ugh; I can't stay away from this soap opera train wreck.
I'm not on the PMC so perhaps I should bud out, but if a successful conclusion
to this JIRA issue means that dependencies such as commons-csv don't wind up in
maven central, thus preventing me from effectively utilizing Solr as an API
with Maven, I'm -1. All sorts of open-source dependencies are in maven central
published "unofficially" using coordinates of another project that needed it
there, customized or not. What's it to you?
I understand if Rob, Mike, etc. want nothing to do with Maven and I think
that's just fine. But please don't stand in Steve and I's way.
> 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: [email protected]
For additional commands, e-mail: [email protected]
