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

Steven Rowe edited comment on SOLR-3204 at 3/7/12 12:45 AM:
------------------------------------------------------------

bq. Solr is a end-user product, so I have no idea why it is in maven at all. 

bq. the 'artifact' for an ordinary user is a .war file, a server-side webapp 
that a user places into their servlet container... maybe the maven artifact 
should be consistent with that? Wouldn't this avoid exposing any internal 
implementation details of whats actually inside that .war file, such as any 
external dependencies?

Solr can be used in embedded fashion (though I don't have any experience with 
that).

Also, solrj is a client jar.

*edit*: oops, solrj isn't relevant here - we're talking about solr-core.

                
      was (Author: steve_rowe):
    bq. Solr is a end-user product, so I have no idea why it is in maven at 
all. 

bq. the 'artifact' for an ordinary user is a .war file, a server-side webapp 
that a user places into their servlet container... maybe the maven artifact 
should be consistent with that? Wouldn't this avoid exposing any internal 
implementation details of whats actually inside that .war file, such as any 
external dependencies?

Solr can be used in embedded fashion (though I don't have any experience with 
that).

Also, solrj is a client jar.


                  
> solr-commons-csv must not use the org.apache.commons.csv package
> ----------------------------------------------------------------
>
>                 Key: SOLR-3204
>                 URL: https://issues.apache.org/jira/browse/SOLR-3204
>             Project: Solr
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 3.5
>            Reporter: Emmanuel Bourg
>            Priority: Blocker
>             Fix For: 3.6
>
>         Attachments: SOLR-3204.patch, solr-csv.patch
>
>
> The solr-commons-csv artifact reused the code from the Apache Commons CSV 
> project but the package wasn't changed to something else than 
> org.apache.commons.csv in the process. This creates a compatibility issue as 
> the Apache Commons team works toward an official release of Commons CSV. It 
> prevents Commons CSV from using its own org.apache.commons.csv package, or 
> forces the renaming of all the classes to avoid a classpath conflict.

--
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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to