[ 
https://issues.apache.org/jira/browse/LUCENE-4262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13424411#comment-13424411
 ] 

Dawid Weiss commented on LUCENE-4262:
-------------------------------------

bq. Sha1 checker needs to also be fixed (or is it in the license checker?).

Hi. Don't know what you actually did - trying to dig myself out from a big pile 
of e-mail - but the lookup of sha1 files was initially written using mappers so 
it should be possible to modify these mappers only (ant level), without 
touching the code?
                
> add ivy sync=true, consolidate licensing, disallow conflicting dependencies
> ---------------------------------------------------------------------------
>
>                 Key: LUCENE-4262
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4262
>             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: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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]

Reply via email to