[
https://issues.apache.org/jira/browse/LUCENE-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13447640#comment-13447640
]
Uwe Schindler commented on LUCENE-4354:
---------------------------------------
There is a trick with maven-ant-tasks to get a refid to a <fileset/> with all
maven dependencies (something like that, maybe Steven knows how to set this up):
{code:xml}
<maven:dependencies xmlns:maven="urn:maven-artifact-ant"
filesetId="foobar.fileset" useScope="runtime"/>
{code}
After that the ANT fileset should point (like ivy:cachefilset) to all
dependency jars. It should be easy to run the license checker on top of this
fileset (refid="foobar.fileset").
See also for a code example:
http://ptrthomas.wordpress.com/2009/03/08/why-you-should-use-the-maven-ant-tasks-instead-of-maven-or-ivy/
> 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.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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
