Context

Describe the context or motivation for this PR. Include links to any related Azure DevOps Work Items or GitHub issues.
📌 Associated WI:AB#2327840

Task Name

MavenV4

Description

Remove second maven run(during code coverage publishing step) to avoid running maven lifecycle phases twice.
The second adds verify phase when JaCoCo is selected as the code coverage -

This is because JaCoCo plugin binds its check goal to the Maven verify phase, which ensures that all tests have run and their coverage data is available -#6458 (comment).

This PR combines below 2 maven runs adding verify phase to the first run:

run to execute maven goals:

maven run before publishing code coverage:

Risk Assessment (Low / Medium / High)

Low. Changes covered under feature flag

Change Behind Feature Flag (Yes / No)

Yes

Tech Design / Approach

• Design has been written and reviewed.
• Any architectural decisions, trade-offs, and alternatives are captured.

Documentation Changes Required (Yes/No)

Indicate whether related documentation needs to be updated.

• User guides, API specs, system diagrams, or runbooks are updated.

Unit Tests Added or Updated (Yes / No)

Indicate whether unit tests were added or modified to reflect these changes.

Additional Testing Performed

canary test pipeline runs:

FF enabled -Pipelines - Run 20251125.8
FF disabled -Pipelines - Run 20251125.7

Logging Added/Updated (Yes/No)

• Appropriate log statements are added with meaningful messages.
• Logging does not expose sensitive data.
• Log levels are used correctly (e.g., info, warn, error).

Telemetry Added/Updated (Yes/No)

• Custom telemetry (e.g., counters, timers, error tracking) is added as needed.
• Events are tagged with proper metadata for filtering and analysis.
• Telemetry is validated in staging or test environments.

Rollback Scenario and Process (Yes/No)

• Rollback plan is documented.

Dependency Impact Assessed and Regression Tested (Yes/No)

• All impacted internal modules, APIs, services, and third-party libraries are analyzed.
• Results are reviewed and confirmed to not break existing functionality.

Checklist

• Related issue linked (if applicable)
• Task version was bumped — seeversioning guide
• Verified the task behaves as expected