[ 
https://issues.apache.org/jira/browse/SOLR-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Rowe resolved SOLR-3664.
------------------------------

       Resolution: Fixed
    Fix Version/s: 4.6
                   5.0
         Assignee: Steve Rowe

Should be fully addressed by LUCENE-5249 and LUCENE-5257.

> risk of inconsistency in solr(contrib)->module->thirdparty dependencies
> -----------------------------------------------------------------------
>
>                 Key: SOLR-3664
>                 URL: https://issues.apache.org/jira/browse/SOLR-3664
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Hoss Man
>            Assignee: Steve Rowe
>             Fix For: 5.0, 4.6
>
>
> Currently, if something in solr has an indirect dependency on a third-party 
> package via a dependency on a lucene module, that is tracked in a 
> solr/\*\*/ivy.xml files and redundant copies of the third-party 
> LICENSE/NOTICE/jar.sha1 files are committed under solr/\*\*
> This presents a risk that these files may fall out of sync if/when the 
> dependencies of the lucene module are updated in the future (ie: a developer 
> could update a lucene module to depend on a new package -- or a new version 
> of an existing package -- w/o remembering to upgrade the corresponding ivy 
> related files in solr)
> we should try to eliminate this risk



--
This message was sent by Atlassian JIRA
(v6.1#6144)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to