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

Robert Muir commented on SOLR-3204:
-----------------------------------

The arguments that this is more than a maven issue are bogus.
Do you take me for a fool?

The same arguments could be had for even *released* dependencies like 
httpclient-3.0 that we use. What if a user wants to use 4.0?

To ant, whether its released or unreleased, its just a jar in a /lib and in the 
users classpath.
But thats not the real issue here: These people are angry about maven 
repositories.

So quit screwing around with crazy ideas about duplicating whole codebases and 
fix the real problem:

open a bug report at Maven with the Description:

*Allow maven project A to depend upon project B without B being in maven at all*

Thats the bug, it stops the replication of the virus, and i don't see any 
reason why maven wouldnt want to fix it? If they object, then it only proves my 
point that its really the GPLv3 of build tools.



                
> 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