lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dawid Weiss (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4262) add ivy sync=true, consolidate licensing, disallow conflicting dependencies
Date Sat, 28 Jul 2012 20:22:34 GMT


Dawid Weiss commented on LUCENE-4262:

Ah, now I recall -- the tool I wrote was to lookup license/notice files and I did use mapper
elements exactly for the purpose of potentially putting those files somewhere else. sha checker
could be probably rewritten to use the same strategy although this is of very low priority
if it works now I guess.
> add ivy sync=true, consolidate licensing, disallow conflicting dependencies
> ---------------------------------------------------------------------------
>                 Key: LUCENE-4262
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Task
>            Reporter: Robert Muir
>             Fix For: 4.0, 5.0
>         Attachments: LUCENE-4262.patch, LUCENE-4262.patch, LUCENE-4262.patch
> From a discussion on IRC:
> * Hoss had the typical clean-jars problem
> * I mentioned we should instead use the ivy option of "sync=true", which is just like
retrieve except nukes any stuff (e.g. old jars) that shouldn't be there.
> * the problem with this is it would also nuke the .sha1 and licensing stuff (its easy
to try and see).
> So the idea came about we could just have a licenses/ folder for each "product" (lucene,
solr) and this has the .sha1's and licensing stuff.
> Steve asked what if different modules depended on different versions of the same jar:
this is bogus and we should just disallow it! 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


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

View raw message