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

Uwe Schindler commented on LUCENE-5755:
---------------------------------------

I think the change of build system is unrelated to the giant classpath problem. 
We could do the same with ANT, too (the giant classpath could be created in the 
root build.xml).

I think the main problem of ANT is the slowness when compiling while comparing 
timestamps over and over. E.g. if I start solr tests it takes endless until 
they start. The worst is creating solr's javadocs (the main reason is, that ant 
forgets everything it did before after it exits subant task). Stuff like solrj 
is built dozens of times just to build javadocs of morphlines. With a better 
dependency management (gradle), we could improve that.

Running all tests in the same set of JVMs but separate classpaths is 
theoretically possible with a special test runner: If we have a separate 
Classloader per module, we can still run them sequential in one JVM (changing 
classloader when changing module in one sequence) + parallel with multiple 
JVMs. But this would be something carrotsearch's testrunner would need to take 
care of.

> Explore alternative build systems
> ---------------------------------
>
>                 Key: LUCENE-5755
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5755
>             Project: Lucene - Core
>          Issue Type: Task
>            Reporter: Dawid Weiss
>            Assignee: Dawid Weiss
>            Priority: Minor
>
> I am dissatisfied with how ANT and submodules currently work in Lucene/ Solr. 
> It's not even the tool's fault; it seems Lucene builds just hit the borders 
> of what it can do, especially in terms of submodule dependencies etc.
> I don't think Maven will help much too, given certain things I'd like to have 
> in the build (for example collect all tests globally for a single execution 
> phase at the end of the build, to support better load-balancing).
> I'd like to explore Gradle as an alternative. This task is a notepad for 
> thoughts and experiments.
> An example of a complex (?) gradle build is javafx, for example.
> http://hg.openjdk.java.net/openjfx/8/master/rt/file/f89b7dc932af/build.gradle



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to