Thad House

I don't think adding features like annotation processing would be that worth it. Once things get that complicated, adding things like that would be much better done through the DSL....

The main issue with this is we don't support gradlerio being loaded in multiple projects at the same time. What is happening is the sim tasks are being created for...

As a workaround, you can explicitly run the root tasks `:simulateNativeRelease` and `:simulateNativeDebug` and you won't see this.

Its not _intentional_, its more that I just haven't had time to do it. Its a little more complicated to grab the C++ tools on windows, as we also need...

We install the runtime DLLs next to the exe when the installer runs. So that side works. So it's just gradle that we need to implement that part. The gradle...

This is now included in wpilib, so it no longer is a vendor deps. You can just import the adis class directly. Do note that in the kickoff release it...

It's in the known issues on the docs, but we don't have an explicit issue in the repo. It's actually a bug in the fpga image, so affects all languages.

I would be ok with them having a way to add vendor deps, but I would be scared of modifying build.gradle directly. It's way too easy to screw up, and...

This is already done. We use the version number from the tags, and this is what gets placed in the manifest. The only fixed version number we have is the...

How would we know the correct GradleRio version? We could make it just generate the primary version number without any extra bits easily enough. But that would all be done...