[
https://issues.apache.org/jira/browse/LUCENE-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-4354:
--------------------------------
Attachment: LUCENE-4354.patch
synced up patch to trunk.
One ugly thing in solr is that to validate the dependencies, we need to ensure
the lucene ones are installed.
for now this is ensured, since its only a validation/test task for jenkins
anyway and better to be safe i think?
> add validate-maven task to check maven dependencies
> ---------------------------------------------------
>
> Key: LUCENE-4354
> URL: https://issues.apache.org/jira/browse/LUCENE-4354
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Robert Muir
> Attachments: LUCENE-4354-dep-fix.patch,
> LUCENE-4354_hacked_lucene_only.patch, LUCENE-4354.patch, LUCENE-4354.patch,
> LUCENE-4354.patch, LUCENE-4354.patch, LUCENE-4354.patch, LUCENE-4354.patch,
> LUCENE-4354.patch, LUCENE-4354.patch, LUCENE-4354.patch, LUCENE-4354.patch
>
>
> We had a situation where the maven artifacts depended on the wrong version of
> tika: we should test that the maven dependencies are correct.
> An easy way to do this is to force it to download all of its dependencies,
> and then run our existing license checks over that.
> This currently fails: maven is bringing in some extra 3rd party libraries.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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]
