[
https://issues.apache.org/jira/browse/LUCENE-9347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17093322#comment-17093322
]
Uwe Schindler commented on LUCENE-9347:
---------------------------------------
Thanks [~dweiss], I just mentioned this because I was looking how forbiddenapis
changes affect Lucene in the new gradle build. My main use case when developing
was just: "get it working ey"! So the parallel approach in Lucene was just
convenient to me for integration testing. BTW, for my quick test setup, I just
commented out the {{plugin}} and put some {{buildscript}} hack with
{{mavenLocal()}} before.
About the task avoidance: I have no idea how this magic affects you at all. I
think for standard projects there's nothing at all. So it's more some selling
point by the gradle guys. In short: It won't change anything. For forbiddenapis
it was also only some reason to move major version to 3.0, nothing more! My
personal opinion as a Gradle plugin developer: Gradle is a pain - sorry - I
could live without it!
> Update to forbiddenapis 3.0
> ---------------------------
>
> Key: LUCENE-9347
> URL: https://issues.apache.org/jira/browse/LUCENE-9347
> Project: Lucene - Core
> Issue Type: Task
> Components: general/build
> Reporter: Uwe Schindler
> Assignee: Uwe Schindler
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Forbiddenapis 3.0 was released a minute ago:
> - Support for Java 14
> - Gradle Task Configuration Avoidance support
> See:
> https://github.com/policeman-tools/forbidden-apis/wiki/Changes#version-30-released-2020-04-27
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
