Desktop native debug artifacts aren't publishd

[spacey-sooty]

Describe the bug
Desktop native debug artifacts aren't published, this prevents ./gradlew simulateJavaDebug from working.

To Reproduce
Steps to reproduce the behavior:

1. Open an example project
2. run ./gradlew simulateJavaDebugg
3. See failure to download artifacts

Expected behavior
The artifacts should be published allowing simulateJavaDebug to work.

Screenshots
If applicable, add screenshots to help explain your problem.

Version (required):

• OS: Ubuntu 24.04
• Project Information: WPILib Information:
  Project Version: 2026.1.1-beta-1
  VS Code Version: 1.105.1
  WPILib Extension Version: 2026.1.1-beta-1
  Project Year: 2026beta
  Language: java
  C++ Extension Version: 1.28.3
  Java Extension Version: 1.38.0
  Java Debug Extension Version: 0.58.2
  Java Dependencies Extension Version 0.24.1
  Java Version: 17
  Java Location: /home/jade/wpilib/2026/jdk
  Vendor Libraries:
  AdvantageKit (26.0.0-beta-1)
  CTRE-Phoenix (v6) (26.0.0-beta-1)
  photonlib (v2026.0.1-beta)
  WPILib-New-Commands (1.0.0)

Additional context
Add any other context about the problem here.

[jwbonner]

We can look into this in the future, though the native debug artifacts are available in the offline zip if needed. This should very rarely impact teams since simulateJavaDebug is only required for debugging native dependencies (e.g. if vendors are debugging their native libraries in AdvantageKit projects). simulateJavaDebug is not required at all for debugging Java projects.

[Ruthie-FRC]

We can look into this in the future, though the native debug artifacts are available in the offline zip if needed. This should very rarely impact teams since simulateJavaDebug is only required for debugging native dependencies (e.g. if vendors are debugging their native libraries in AdvantageKit projects). simulateJavaDebug is not required at all for debugging Java projects.

is this a feature that would be useful if implemented? if so, I'd be happy to work on this in my free time!

[jwbonner]

@Ruthie-FRC I certainly see no harm in publishing the additional artifacts to Maven, since GradleRIO's task names have a habit of tripping up users even though simulateJavaDebug isn't what it sounds like. I haven't looked at the Maven publishing code in a while, the issue is with the desktop builds that are published through a separate Python script to avoid file conflicts when uploading.

[Ruthie-FRC]

sounds great! due to the expected inclement weather where I live delaying robotics, I might not be able to start work on it until February (I have to play some catch-up with our cad designs), but afterwards I'd be happy to work on this!

[Ruthie-FRC]

NVM i worked though most of the backlog already. @jwbonner could you please assign the issue to me so I don't forget about it?

[Ruthie-FRC]

starting work!

[Ruthie-FRC]

ok its been a while but I'm making progress on it I just got distracted with the season lol