-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No builders are available to build a model of type 'com.microsoft.java.bs.gradle.model.GradleSourceSets'. #180
Comments
@Arthurm1 @Tanish-Ranjan If you think of any possibilities of the root cause, please let me know. |
@jdneo I can't reproduce this. The latest develop branch builds and runs locally fine for me. I'm running on Windows 11, Gradle 8.10, JDK 21. Do you have a test repo it doesn't work on? The model is registered by the plugin so I can only think the plugin hasn't been applied to the project you're testing.
with init.gradle as....
|
I think this exception was collected from telemetry. The error message does seem to point that the ModelBuilder wasn't registered. |
I have no idea how to reproduce it either. It shows in the BI that some sessions are failed due to this error. And I checked some earlier version but cannot observe this error. |
Oh I see - you get this telemetry back from VSCode? Does it give any exception stack trace or info on what gradle version, what OS, what JDK? I guess no users have raised a github issue? |
Yes
Yes we have the stacktrace
So far, no. |
Possibly an installation issue. Maybe the old If this is so then it would be fixed by killing Gradle and restarting. Then I guess no one would report the problem. I wonder if versioning these jars e.g. |
I don't understand. So somehow after the pre-release installation the old plugin was still loaded in gradle? But the new plugin should have added the model builder for GradleSourceSets, in which case it shouldn't have thrown the error. |
This a good point, even if we do not publishing them to Gradle portal, we should add version number to it |
I'm just guessing that the Gradle daemon keeps plugin classes loaded so if a new |
I tried to add version number to plugin.jar in #186 and made a pre-release last night. There are still one session have this error. Since that the stable release 3.16.4 has released for very long time and till now there is no one session has this error, I think maybe plugin version is not the cause. From another perspective, when GradleSourceSetsMetadata was introduced earlier, the plugin.jar also didn’t have version information. However, no such errors appeared in the telemetry, indicating that the issue might not be related to the version |
This error appears after we add #168 and #165
Need to figure out why it appears.
The text was updated successfully, but these errors were encountered: