[
https://issues.apache.org/jira/browse/LUCENE-3930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13241083#comment-13241083
]
Dawid Weiss commented on LUCENE-3930:
-------------------------------------
bq. Having jars in our source release is.
Is a requirement that the source release must "build out of the box"? Or is it
about code publication only? I don't know, I'm asking. This seems like a
revolutionary build change before the release :)
bq. Having the build OOM is. So I made a tradeoff.
I understand this, but my gut feeling still says that if you need to install
ivy in an ant global space you might as well set ANT_OPTS to increase
permgen... The tradeoff made is one of many.
bq. i need your help... its just that simple
Can't jump into it right now, sorry. I'll take a look when I get a spare cycle
though. I'm not sure it can be fixed but I'll take a look.
> 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
> Priority: Blocker
> Fix For: 3.6
>
> Attachments: LUCENE-3930-solr-example.patch,
> LUCENE-3930-solr-example.patch, LUCENE-3930.patch, LUCENE-3930.patch,
> LUCENE-3930.patch, ant_-verbose_clean_test.out.txt, patch-jetty-build.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
