[
https://issues.apache.org/jira/browse/LUCENE-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-4354:
----------------------------------
Attachment: LUCENE-4354.patch
Patch, that not only implements the validation, it also cleans up
Maven-Tast/Traget dependnecies in ANT. I counted: All javadocs in Lucene
modules were built 2 times, for analyis 3 times!
This patch first runs generate-maven-artifacts as before (but faster) and can
then run validate-maven-dependencies (which depends on
generate-maven-artifacts). As this iterates all modules 2 times, you need lot's
of perm-gen. In fact sometimes (if my repository is empty), not even
generate-maven-artifacts passes without more permgen (Windows 7 64).
> 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
>
>
> 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]
