[Java] Clean-up: make it so interim time during implementation produces correct artifacts

[edburns]

Since the merging of #2301 , the Java Maven POM incorrectly produced artifacts containing linux-x64 in the filename, regardless of the actual os-arch of the build. This is incorrect. The correct behavior is to make it so only when the actual os-arch is linux-x64 should such artifacts be produced.

[github-actions]

Bug Confirmed ✅

Investigation

I examined java/copilot-native/pom.xml, introduced in #2301.

Root cause: Line 43 unconditionally hardcodes the classifier:

<copilot.native.classifier>linux-x64</copilot.native.classifier>

The comment above it reads:

Phase 4 hard invariant: linux-x64 is the only supported platform. Additional classifiers are added in a later phase, each with its own fetch execution and maven-jar-plugin execution.

This confirms the hardcoding is intentional as a temporary interim measure, not the desired end state. Every build — regardless of actual OS/arch — produces an artifact named ...-linux-x64.jar.

Fix needed

The POM should detect the actual OS/arch (e.g., via Maven's os-maven-plugin or built-in ${os.name}/${os.arch} properties with activation profiles) and set copilot.native.classifier accordingly, so only a linux-x64 build produces a linux-x64 artifact.

Labeled as bug.

Generated by Bug Handler for #2344 · sonnet46 21.3 AIC · ⌖ 5.11 AIC · ⊞ 5.9K · ◷

[kaawmnain24-netizen]

ye