lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-3204) solr-commons-csv must not use the org.apache.commons.csv package
Date Wed, 07 Mar 2012 15:44:57 GMT


Robert Muir commented on SOLR-3204:

It's 5 classes it looks like - and it's Apache licensed and there is no release - can't we
simply suck this into our code base with a readme and JIRA about removing it and switching
to a release when one occurs? Get the whole dependency thing right out of Maven's claws.

Yes while this is the case, and as Emmanuel states, the purpose of his patch, its not a scalable
solution in general.
Its also expensive to fork software... there is always the danger that we then become out-of-sync
and never sync back up.

(feel free to hit me, for Uwe's example of snowball, which is a perfect example)

What about the other cases that fall into this same 'maven namespace' category, e.g. the UIMA
case for example?

How to fix the general problem? Thats why I think that the only proper way to fix the bug
is to attack it at the heart:
Thats the fact that for maven project A to depend upon project B that is not in maven, maven
project A must "publish" some "fake maven release" of project B.
> solr-commons-csv must not use the org.apache.commons.csv package
> ----------------------------------------------------------------
>                 Key: SOLR-3204
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message