Cache source bundle generation in local Maven repository

[Copilot]

Source bundles were regenerated on every build using temp files, slowing builds and creating garbage. This adds caching similar to wrapped bundles.

Approach

Cache eclipse source bundles alongside the original maven source JARs:

• xyz-source.jar → xyz-eclipse-source.jar (same directory)
• Timestamp-based invalidation: regenerate only when source file is newer

Changes

• MavenBundleWrapper: Added getEclipseSourceBundle() that returns cached bundle or generates new one
• MavenTargetDefinitionContent: Replaced temp file creation with cached bundle lookup
• MavenBundleWrapperTest: Unit tests for cache creation, reuse, and invalidation

// Before: temp file created every build
File tempFile = File.createTempFile("tycho_wrapped_source", ".jar");
tempFile.deleteOnExit();

// After: cached in maven repo alongside source
File eclipseSourceFile = MavenBundleWrapper.getEclipseSourceBundle(
    sourceFile, manifest, symbolicName, bundleVersion);

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• testng.org
  • Triggering command: /opt/hostedtoolcache/CodeQL/2.24.0/x64/codeql/tools/linux64/java/bin/java /opt/hostedtoolcache/CodeQL/2.24.0/x64/codeql/tools/linux64/java/bin/java -jar /opt/hostedtoolcache/CodeQL/2.24.0/x64/codeql/xml/tools/xml-extractor.jar --fileList=/home/REDACTED/work/tycho/.codeql-scratch/dbs/java/working/files-to-index10366803578815674553.list --sourceArchiveDir=/home/REDACTED/work/tycho/.codeql-scratch/dbs/java/src --outputDir=/home/REDACTED/work/tycho/.codeql-scratch/dbs/java/trap/java (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Source bundles are generated over and over again</issue_title>
<issue_description>I noticed that source bundles are generated by Tycho on each build. This unnecessarily slow down the build and creates garbage. We should similar to how its down with wrapped bundles, cache the result in the local maven repository and only regenerate it if it actually changed. </issue_description>

<agent_instructions>Please implement a fix for this. The approach should be working by using the filename of the source bundle we wrap (e.g. xyz-source.jar) and then create a xyz-eclipse-source.jar at the same location. To check if the source bundle is outdated we want to use the last modifed time of both files.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes Source bundles are generated over and over again #5812

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[laeubi]

This looks fine to me, as we share this code with m2e a similar change should be done here likely as well.

[eclipse-tycho-bot]

💚 All backports created successfully

Status	Branch	Result
✅	tycho-5.0.x

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details