lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (LUCENE-5442) Build system should sanity check transative 3rd party dependencies
Date Mon, 02 Jun 2014 09:15:02 GMT


ASF subversion and git services commented on LUCENE-5442:

Commit 1599134 from [~steve_rowe] in branch 'dev/trunk'
[ ]

LUCENE-5442: smoke tester: '' is not a foreign invader

> Build system should sanity check transative 3rd party dependencies
> ------------------------------------------------------------------
>                 Key: LUCENE-5442
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: general/build
>            Reporter: Hoss Man
>            Assignee: Steve Rowe
>             Fix For: 4.9, 5.0
>         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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message