[
https://issues.apache.org/jira/browse/SOLR-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-3664:
---------------------------
Description:
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
was:
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
> 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
>
> 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 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]
