[
https://issues.apache.org/jira/browse/SOLR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260832#comment-13260832
]
Robert Muir commented on SOLR-3405:
-----------------------------------
Well i think so, I mean the way maven publishes solr, it publishes it as if it
were an _api_, not an application.
But the binary release treats solr as an application. This is a big difference!
Because of this we previously also published some war dependencies
(commons-csv) also as _api_ in maven too.
This is what got people all upset, but if you look at our binary package we
don't ever package their stuff up this way.
Releasing an application is easier. we don't care about dependencies (except
that they are legal): just that our .war works.
and if the .war also wants to be in maven, then it should declare no
dependencies (it works by itself).
> 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]
