Effective POM Resolution Refactor (#187)

Author: adesjardin

.github/workflows/build.yml

@@ -10,6 +10,10 @@ on:
     branches:
       - 'main'
 
+# Opt into Node.js 24 for actions (required for actions using Node 20 after deprecation)
+env:
+  FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true
+
 jobs:
   Build:
     uses: avioconsulting/shared-workflows/.github/workflows/gradle-build.yml@main

.settings/org.eclipse.buildship.core.prefs

@@ -160,6 +160,38 @@ Examples:
 - `mule-linter-maven-plugin`: Maven-facing wrapper; keep it thin and compatible with Maven conventions.
 - `mule-linter-cli`: command-line packaging and distribution.
 
+## Parent POM Resolution
+
+Parent POMs are resolved using embedded Maven Resolver (Eclipse Aether):
+- Resolves full parent chain (child → parent → grandparent → ...)
+- Uses ~/.m2/settings.xml for repository configuration and authentication
+- Caches resolved parents in ~/.m2/repository (standard Maven cache)
+- Only resolves parent POMs (not dependencies or plugins)
+
+**New Resolution Methods:**
+- `PomFile.resolveProperty(String)` - Returns ResolvedProperty with source tracking
+- `PomFile.resolveDependency(String, String)` - Returns ResolvedDependency with inheritance info
+- `PomFile.resolvePlugin(String, String)` - Returns ResolvedPlugin with management info
+
+**Backward Compatibility:**
+- Existing methods (`getPomProperty()`, `getDependency()`, `getPlugin()`) still work
+- Parent resolution is explicit - call `pomFile.resolveParents(ParentPomResolver.getInstance())` to enable inheritance
+- `PomFile.resolveParents()` throws `ParentPomResolutionException` on failure (fail-fast)
+- `MuleApplication` catches resolution exceptions and logs warnings, allowing rules to operate on raw POM data
+
+**Resolver Architecture:**
+- `ParentPomResolver.getInstance()` returns a shared singleton instance
+- The singleton is initialized lazily on first use (~500ms startup cost)
+- A JVM shutdown hook automatically calls `close()` on the singleton to release resources
+- Do NOT call `close()` on the singleton instance from application code
+- For tests or custom scenarios, use `new ParentPomResolver(path)` and manage lifecycle yourself
+
+**System Properties:
+- `mule.linter.localRepo`: Custom local repository path (default: ~/.m2/repository)
+
+**Environment:**
+- `M2_HOME`: Used to find global settings.xml
+
 ## Consolidated POM Test Structure
 
 The `mule-linter-core` module has consolidated POM-related tests into 4 comprehensive test classes: