[
https://issues.apache.org/jira/browse/SOLR-2435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13244538#comment-13244538
]
Robert Muir commented on SOLR-2435:
-----------------------------------
{quote}
in the ICU4J case, at a minimum we can promote the jar up out of the individual
contirbs and into the main "lib" dir ... but since it's also in modules, it
should be possible to have it copied into the lucene-libs dir (although i'm not
totally up to speed on what builds that dir right now)
{quote}
Seeing as now this issue only affects the _binary release_ and no longer the
source one :)
I think its much less of an issue. I'm not sure how it helps to have icu4j in
lucene-libs versus coming into lib/.
I definitely don't think its a blocker (as we said before, especially now that
it doesnt affect source release),
but its nice to clean up: the junit one is especially confusing, so I'm
committing that one to trunk.
> Duplicate Jars in release packages
> ----------------------------------
>
> Key: SOLR-2435
> URL: https://issues.apache.org/jira/browse/SOLR-2435
> Project: Solr
> Issue Type: Bug
> Reporter: Hoss Man
> Fix For: 4.0
>
> Attachments: SOLR-2435_duplicate_junit.patch,
> SOLR-2435_duplicate_junit.patch
>
>
> Reviewing the 3.1 release candidates, i've noticed that in a few places we
> have duplicated jars.
> of particular note is the "ICU4J" jar, which not only exists in two different
> solr contrib lib directories, but also exists in modules.
--
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]
