[
https://issues.apache.org/jira/browse/LUCENE-3930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-3930:
--------------------------------
Attachment: LUCENE-3930.patch
updated patch:
* core+contrib+modules work. though we need to remove jars and move to
dependencies.
* i found the source of the maven-ant-tasks OOM that hits us in
prepare-release. It hit me here too. The problem is that you should not allow
the taskdef to run in dist-maven if it already ran. so the one for ivy has
unless=ivy.uptodate (which sits in that uptodateAndCompiled propset). Finally i
ensured the modules 'crawl' passes this around. We should fix dist-maven the
same way.
* bogusly every contrib/module currently needs an ivy.xml (even with no
dependencies). I'd like to remove this but i just havent mucked with it yet.
> nuke jars from source tree and use ivy
> --------------------------------------
>
> Key: LUCENE-3930
> URL: https://issues.apache.org/jira/browse/LUCENE-3930
> Project: Lucene - Java
> Issue Type: Task
> Components: general/build
> Reporter: Robert Muir
> Assignee: Robert Muir
> Attachments: LUCENE-3930.patch, LUCENE-3930.patch, LUCENE-3930.patch
>
>
> As mentioned on the ML thread: "switch jars to ivy mechanism?".
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
