Updates to build better update sites

[merks]

• Update execution-environment to accommodate newer BREEs.
• Update cbi-version to 1.5.2 to use the latest jarsigner.
• Configure tycho-p2-repository-plugin to include any available sources.
• Add org.eclipse.ecf.dependencies.feature for non-project dependencies that are wanted in the p2 update site; the commons-codec bundle is not needed by any currently published bundle.
• Include org.eclipse.ecf.dependencies.feature in the category.xml, though uncategorized.
• Remove the ssl features from the category.xml because they are not built and were being dragged in via an old version in the Platform SDK.
• Clean up the 2024-06.target.

[eclipse-ecf-bot]

Can one of the admins verify this patch?

[merks]

@scottslewis

FYI, this is pending. It's to avoid run afoul of the new stricter rule that is coming:

eclipse-simrel/.github#55

I don't understand the build failure, it does build locally for me...

[scottslewis]

I tried a rerun of the build. It just fails after 49 lines of output. I have no idea why. See log in the failed maven job above.

Below what the AI says for diagnosis. Seems to be something about the baseline...but doesn't immediately make sense to me.

As I'm preparing 3.16.3, I don't want to merge this until things build ok.

---

The failure in the job is related to the tycho-p2-extras-plugin during the execution of the compare-version-withThe failure occurred during the execution of the org-baselinesgoal. Specifically, it failed on the projectorg.eclipse.ecf.identity. This issue often occurs.eclipse.tycho.extras:tycho-p2-extras-plugin Maven plugin with when there is a mismatch or missing baseline version definitions the compare-version-with-baselines goal. This in the Maven build.

Potential Solution error typically arises when the plugin detects version inconsistencies between the project's artifacts

Steps to Resolve:

1. Check Baseline Definitions:
   • Verify if the baseline versions are properly and the specified baselines.

Solution

1. Verify Bas defined for the org.eclipse.ecf.identity projecteline Versions:
   • Ensure that the baseline versions are correctly specified in your POM files or baseline in your pom.xml or associated configuration files.

files.

• Check if the version of `org.eclipse2. Update Maven Command:
• The current Maven command.ecf.identity` matches the expected baseline version.

in the workflow is:
```yaml
run:2. Debugging the Issue:

• Re-run the build mvn clean verify -Pbaseline-checks -DskipTests=true
  locally with the -e (for full stack trace) ```
  Add debugging flags to get more information about the failure:

  run: mv and `-X` (for debug logs) Maven flags:
  ```bash

n clean verify -Pbaseline-checks -DskipTests=true - mvn clean verify -Pbaseline-checks -DskipTests=true -e -X
 ```
 This will provide detailed debug logse -X
 ```

• This will provide more detailed logs to pinpoint the exact issue.

3. **Verify Baseline Art to pinpoint the exact mismatch.

4. Adjust Workflowifacts**:

   • Ensure that the baseline repository or artifacts:
   • Update the workflow to include detailed logs during used for comparison are accessible and up the job run. Modify the Build with Maven step-to-date. If the baseline artifacts are missing or outdated in your workflow file to:

yaml
-4. Correct Versioning:

• If the error is name: Build with Maven
  run: mvn clean verify -P due to incorrect versioning, update the version numbersbaseline-checks -DskipTests=true -e -X

• in the pom.xml of the org.eclipse.ecf.identity project This change will provide more verbose logs in the CI to align with the baseline requirements.

Updated environment for future troubleshooting.

4. ** Workflow Example:
   Here’s how you can modify the workflowFix the Version Mismatch**:
   • If a version mismatch is confirmed to include debug flags:

- name: Build with, update the version of `org.eclipse.ecf Maven
  run: mvn clean verify -Pbaseline-checks.identity` in the `pom.xml` file to align with the expected baseline version.

5. **Resume Build**:
   - -DskipTests=true -e -X

Reference to Workflow File Once the issue is fixed, resume the build with the following:

You can find and edit the workflow file [ Maven command:
bash mvn <here](https://github.com/eclipse-ecf/ecf/blob/c347args> -rf :org.eclipse.ecf.identity

Reference

• Workflow File.

If the issue persists after debugging and verifying the baseline definitions, please share theecf/ecf/blob/c347902fa5d3b98778def9e770339574a00b8 updated logs with debug information for further analysis.d61/.github/workflows/maven.yml)

• Maven Plugin Execution Exception Help

Would you like me to search for the pom.xml file or any specific baseline configuration files to help address this issue?