[
https://issues.apache.org/jira/browse/SOLR-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13224284#comment-13224284
]
Grant Ingersoll edited comment on SOLR-3204 at 3/7/12 1:18 PM:
---------------------------------------------------------------
I guess I'm missing something. We aren't part of the Commons project. The
Commons code is Apache licensed, we are using it as we see fit under the T&C of
the ASL. What prevents someone else from going and doing the same thing
outside of Apache? In fact, it happens all the time, even at Apache. Commons
CLI 2 is the biggest one, as I know of several projects that "release" that b/c
Commons itself never has. Here are also several who do it for Lucene. The
problem *is* Maven and it isn't going away.
Here are some examples:
#
http://search.maven.org/#artifactdetails%7Corg.hibernate.apache.lucene.solr%7Capache-solr-analyzer%7C1.2.0%7Cjar
#
http://search.maven.org/#artifactdetails%7Corg.apache.clerezza.ext%7Corg.apache.lucene%7C0.1-incubating%7Cbundle
Tomcat does the same thing to Commons (file upload, for example):
# http://search.maven.org/#search%7Cga%7C4%7Ccommons
I could keep going. Just do searches for popular Apache libraries in Maven and
you will see what I mean. Maven is not a red herring. It is the problem.
was (Author: gsingers):
I guess I'm missing something. We aren't part of the Commons project. The
Commons code is Apache licensed. What prevents someone else from going and
doing the same thing outside of Apache? In fact, it happens all the time, even
at Apache. Commons CLI 2 is the biggest one, as I know of several projects
that "release" that b/c Commons itself never has. Here are also several who do
it for Lucene. The problem *is* Maven and it isn't going away.
Here are some examples:
#
http://search.maven.org/#artifactdetails%7Corg.hibernate.apache.lucene.solr%7Capache-solr-analyzer%7C1.2.0%7Cjar
#
http://search.maven.org/#artifactdetails%7Corg.apache.clerezza.ext%7Corg.apache.lucene%7C0.1-incubating%7Cbundle
Tomcat does the same thing to Commons (file upload, for example):
# http://search.maven.org/#search%7Cga%7C4%7Ccommons
I could keep going. Just do searches for popular Apache libraries in Maven and
you will see what I mean. Maven is not a red herring. It is the problem.
> 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
