[P1] Fix parent POM build errors

[sfloess]

Problem

Maven build fails with parent POM resolution errors:

[FATAL] Non-resolvable parent POM for org.flossware.jplatform:platform-java-api:1.1: 
The following artifacts could not be resolved: org.flossware.jplatform:platform-java-parent:pom:1.1 (absent)

Root Cause

Module POMs reference:

<parent>
    <artifactId>platform-java-parent</artifactId>
    ...
    <relativePath>../pom.xml</relativePath>
</parent>

But parent POM has:

<artifactId>platform-java</artifactId>  <!-- Mismatch! -->

Impact

• Severity: HIGH
• Category: Build System
• mvn compile fails for individual modules
• mvn -pl <module> doesn't work
• IDE import may fail

Required Action

Option 1: Rename parent artifactId to platform-java-parent:

<artifactId>platform-java-parent</artifactId>

Option 2: Update all child POMs to reference platform-java:

<parent>
    <artifactId>platform-java</artifactId>

Recommendation: Option 1 (less changes, clearer naming)

Priority

P1 - High - Blocks local development and CI/CD enhancements.

Affected Modules

All 42 modules have incorrect parent reference.

[sfloess]

✅ Issue Resolved - No Action Needed

This issue is obsolete. The parent POM artifactId mismatch has already been corrected.

Current State (Verified):

• ✅ Parent POM: <artifactId>platform-java-parent</artifactId>
• ✅ Child POMs: All reference platform-java-parent correctly
• ✅ Build succeeds: mvn compile -pl platform-api → SUCCESS
• ✅ Module builds work independently

Test Results:

$ mvn clean compile -pl platform-api
[INFO] BUILD SUCCESS
[INFO] Total time:  2.940 s

Root Cause:
The issue was likely fixed in a previous refactoring session. The parent/child artifactId references are now consistent across all 42 modules.

No further action required.

Closing as obsolete.