You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
In a certain included builds setup (see reproducer) the computeActualUsage* tasks fail with:
A failure occurred while executing com.autonomousapps.tasks.ComputeUsagesTask$ComputeUsagesAction
> Node IncludedBuildCoordinates(...) is not an element of this graph.
Task should not fail with an error and work as in 2.6.0
Additional context
The included build setup of the project linked above is too complex. The included build is used both as a Gradle plugin and as a component. Which causes some confusing effects already. Nevertheless, the dependency analysis worked previously. But it may be something special in the setup causing this and it may not be a general issue with included builds.
There do not seem to be that many changes between 2.6.0 and 2.7.0
This change in the "graph support" part sounds like it could be related:
# Version 0.5
* [New] `Graphs` has new overloads of `reachableNodes()` that accepts a predicate for node-matching.
The text was updated successfully, but these errors were encountered:
Build scan link
https://scans.gradle.com/s/unbm6xn2brvfo
Plugin version
2.7.0
(works in2.6.0
)Gradle version
8.12
(also reproduced with8.8
)JDK version
21.0.5
Describe the bug
In a certain included builds setup (see reproducer) the
computeActualUsage*
tasks fail with:To Reproduce
Steps to reproduce the behavior:
pbj-integration-tests
./gradlew computeActualUsageMain
Expected behavior
Task should not fail with an error and work as in
2.6.0
Additional context
The included build setup of the project linked above is too complex. The included build is used both as a Gradle plugin and as a component. Which causes some confusing effects already. Nevertheless, the dependency analysis worked previously. But it may be something special in the setup causing this and it may not be a general issue with included builds.
There do not seem to be that many changes between
2.6.0
and2.7.0
This change in the "graph support" part sounds like it could be related:
The text was updated successfully, but these errors were encountered: