[
https://issues.apache.org/jira/browse/LUCENE-4262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-4262:
--------------------------------
Attachment: LUCENE-4262.patch
I tried this out: seems to work well.
I moved all license .txt/.sha1 to lucene/licenses and solr/licenses
respectively.
I added sync=true (its a property though) so that old jars get cleaned during
resolve (eliminating the clean-jars hassle).
I disabled this sync for solr-core and solrj since they share the same lib/
directory, but its working everywhere else.
Everything works, but i have no idea how to fix the license checker. Sha1
checker needs to also be fixed (or is it in the license checker?).
> 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
> Attachments: 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]
