[
https://issues.apache.org/jira/browse/SOLR-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13223329#comment-13223329
]
Uwe Schindler commented on SOLR-3204:
-------------------------------------
bq. Robert, if you are not releasing code then how did the artifact find its
way into the Maven Central repository? The maintainers of the repository will
ONLY accept artifacts when they come from the appropriate place - in this case
that would need to be Apache's repository. I can't imagine how anyone other
than Solr's team could have caused that to happen.
We are releasing Maven Artifacts of Solr just for convenience using a special
ANT script (which is unsupported by our committers). The community wants it, so
we do it. Maybe that script also published one of the snapshot artifacts (is
there also a Jetty prerelease artifact?); but that was not our intention. We
should simply remove it.
> 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-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: [email protected]
For additional commands, e-mail: [email protected]
