[
https://issues.apache.org/jira/browse/LUCENE-5755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14045920#comment-14045920
]
Matt Davis commented on LUCENE-5755:
------------------------------------
I have managed to get all lucene modules to compile under gradle. All test
cases fail due to the system out issue. It will compile successfully with
./gradlew build -x test but will fail with a ./gradlew build due to the test
cases. It is not running javacc either but my guess is that this would due the
trick https://github.com/RobertFischer/gradle-javacc-plugin. I have not
validated that the output it is generating is at all valid. Solr modules are
not compiling yet either.
If anyone wants to play around with it:
https://github.com/apache/lucene-solr/pull/59
> 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]
