[
https://issues.apache.org/jira/browse/LUCENE-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13447716#comment-13447716
]
Robert Muir commented on LUCENE-4354:
-------------------------------------
selckin: that problem is more than maven actually, e.g. things like SOLR-3736.
Really you are right, if we have a dependency we should be testing that its
working :)
But its good to check the inverse, at least we know we are not depending on
things we didnt know about, or the wrong versions: this
only complements that.
> 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
>
>
> 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]
