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

Dawid Weiss commented on SOLR-3405:
-----------------------------------

I still think this is a misunderstanding of what a "maven release" is by the 
board. I mean the POM states clearly:
{noformat}
  <groupId>org.apache.solr</groupId>
  <artifactId>solr-commons-csv</artifactId>
  <name>Solr Specific Commons CSV</name>
  <version>3.5.0</version>
  <description>Solr Specific Commons CSV v1.0-SNAPSHOT-r966014</description>
{noformat}
So it's not commons-csv. It's solr-*SPECIFIC*-commons-csv. Maven folks don't 
just download jars from maven central, they use pom dependencies. If you depend 
on the above, it's hard to call it an official commons-csv release...

                
> 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]

Reply via email to