[
https://issues.apache.org/jira/browse/LUCENE-5442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14013494#comment-14013494
]
ASF subversion and git services commented on LUCENE-5442:
---------------------------------------------------------
Commit 1598538 from [~steve_rowe] in branch 'dev/trunk'
[ https://svn.apache.org/r1598538 ]
LUCENE-5442: ant check-lib-versions will fail the build if there are unexpected
version conflicts between direct and transitive dependencies.
> Build system should sanity check transative 3rd party dependencies
> ------------------------------------------------------------------
>
> Key: LUCENE-5442
> URL: https://issues.apache.org/jira/browse/LUCENE-5442
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
> Reporter: Hoss Man
> Assignee: Steve Rowe
> Attachments: LUCENE-5442.patch
>
>
> SOLR-5365 is an example of a bug that croped up because we upgraded a 3rd
> party dep (tika) w/o realizing that the version we upgraded too depended on a
> newer version of another 3rd party dep (commons-compress)
> in a comment in SOLR-5365, Jan suggested that it would be nice if there was
> an easy way to spot problems like this ... i asked steve about it, thinking
> maybe this is something the maven build could help with, and he mentioned
> that there is already an ant task to inspect the ivy transative deps in order
> to generate the maven deps and it could be used to help detect this sort of
> problem.
> opening this issue per steve's request as a reminder to look into this
> possibility.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
