[
https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13261670#comment-13261670
]
Steven Rowe commented on SOLR-3405:
-----------------------------------
{quote}
bq. So, this time without avoiding the question: why should we not publish
solr-core on Maven Central?
Because maven requires that its dependencies are also in maven, whereas the
binary distribution does not: it exposes its "innards".
{quote}
This is an argument against Maven generally, not exclusively the Solr
artifacts; I view it as a thinly veiled re-assertion that Lucene/Solr should
not support Maven at all. Again: -1.
The fix here is not to stop publishing on Maven Central, but rather as you say
on the issue: make the Maven Central artifacts like the binary artifacts.
Using your logic, excluding solr-core from the Maven Central artifacts would
make the two "not the same", and hence would be WRONG!!!
> 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.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 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]
