Android Studio: Package Native Libraries into APK
Its been a month since I posted this original dilemma of mine. Since then I have attempted to get other variants of OpenAL for Android to compile and be usable withing a Java domain all ending in the...
View ArticleCould not run build action using gradle distribution
Please help … Running on OS X 10.15.5 and using Eclipse IDE 4.16.0 to load existing gradle project Minecraft Forge 1.12.2...
View ArticleClik here to view.
Unity build to Android failed, because file is in use
Windows PC, building in Unity 2020.1.0f1 to Android After updating to the latest version of Unity, I am no longer able to build any project to Android, though building to other platforms works...
View ArticleExtra side-effects of Project.getTasksByName()?
I am trying to update/rewrite an old Gradle plugin of ours, but have stumbled across something I don’t understand. (I am using Gradle 5.6.4 and cannot upgrade to Gradle 6.x yet.) Our plugin is applied...
View ArticleUnexpected "Duplicate path" warning in :processFuncTestResources task
@Pierre1 My case has been resolved by a suggestion by @sterling to use: sourceSets { funcTest } Your case seems to be different, so you probably need to report another issue (most likely before 7.0 is...
View ArticleExtra side-effects of Project.getTasksByName()?
You could just change your logic to allprojects { tasks.matching { it.name == 'foo' }.all { // logic goes here } } Then you wouldn’t need an afterEvaluate{...} closure or evaluationDependsOnX. See...
View ArticleExtra side-effects of Project.getTasksByName()?
Hi Lance, thanks for the reply. The plugin is already working much as you describe. The problem is with how it creates its matching condition. Basically, starting from the Gradle command line:...
View ArticleIgnore subproject with application plugin
I have a project that contains many subprojects, which are plugins for the main core part. One of these subprojects is the launcher for the program, as it’s not essential to the core, or for any other...
View ArticleClik here to view.
Extra side-effects of Project.getTasksByName()?
The plugin is already working much as you describe No, it’s not. The fact that it’s using Set<String> and Set<Task> shows the problem. Please read here for related topic Multiple...
View ArticleExtra side-effects of Project.getTasksByName()?
This Set<String> contains the task names read from Gradle’s command line parameters: Set<String> requestedTaskNames = new...
View ArticleExtra side-effects of Project.getTasksByName()?
I am certain that this Set<String> is “static” and not “live” I agree, this is fine However, I do agree that then using findByPath() to convert the Set<String> to Set<Task> is a Bad...
View ArticleGradle Enterprise Maven Extension 1.6.1 has been released
The Gradle Enterprise Maven Extension v1.6.1 has been released. See release notes for the changelog. Compatible with scans.gradle.com and Gradle Enterprise 2020.3 or later.
View ArticleGradle 6.6-rc-5 is now available for testing
Gradle 6.6-rc-5 is now available for testing; see the release notes
View ArticleGradle: artifactoryPublish execute from within build.gradle does not publish...
Thank you Chris for your response. I was able to get it to run last week. I did remove the execute and did something similar to your suggestion (which looks more professional) task publishAllApis () {...
View ArticleClik here to view.
Extra side-effects of Project.getTasksByName()?
Here’s a few comments on your original post. chrisjr: The documentation for Project.getTasksByName() says: NOTE: This is an expensive operation since it requires all projects to be configured. which I...
View ArticleClik here to view.
Extra side-effects of Project.getTasksByName()?
Hi, thanks for the explanation about Project.evaluationDependsOnChildren(). This particular plugin can only be applied by the root project, and is invoking evaluationDependsOnChildren() as the first...
View ArticleExtra side-effects of Project.getTasksByName()?
I consider afterEvaluate {...} and evaluationDependsOnX() as hacks that should be avoided. Think of the case where two plugins want to perform some logic in an afterEvaluate closure. You can often...
View ArticleTest retry plugin 1.1.7 has been released
A new patch release of the test-retry-plugin (https://github.com/gradle/test-retry-gradle-plugin) has been released. For details of all the included fixes check here.
View ArticleExtra side-effects of Project.getTasksByName()?
Oh, I agree. I wrote my first Gradle plugin back in the Gradle 3.x days, and was burnt by afterEvaluate() when I needed to coordinate with another (third party) plugin, but couldn’t because there is...
View Article
