Skip to content

Fix #7464: Use relative paths in generated resolved bndrun files for … - #7484

Closed
chrisrueger wants to merge 2 commits into
masterfrom
fix/7464-relative-paths-in-resolved-bndrun
Closed

chrisrueger wants to merge 2 commits into
masterfrom
fix/7464-relative-paths-in-resolved-bndrun

Conversation

@chrisrueger

@chrisrueger chrisrueger commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

…Gradle plugin

This change fixes a build cache issue where the Resolve task's outputBndrun file contained absolute paths in its -include directive. These absolute paths would become stale when files were retrieved from remote build caches, causing failures in CI/CD environments.

The fix generates a relative path from the output bndrun file's location to the input bndrun file. This makes the generated file portable across different machines and CI environments, and thus safe for caching.

The relative path approach is also aligned with bnd's documentation which recommends using relative paths for portability.

Created via AI / Copilot.

Closes #7464

…Gradle plugin

This change fixes a build cache issue where the Resolve task's outputBndrun file
contained absolute paths in its -include directive. These absolute paths would
become stale when files were retrieved from remote build caches, causing failures
in CI/CD environments.

The fix generates a relative path from the output bndrun file's location to the
input bndrun file. This makes the generated file portable across different
machines and CI environments, and thus safe for caching.

The relative path approach is also aligned with bnd's documentation which
recommends using relative paths for portability.
…Maven plugin

This change fixes a build cache issue where the resolver mojo's output bndrun file
contained absolute paths in its -include directive. These absolute paths would
become stale when files were retrieved from remote build caches, causing failures
in CI/CD environments.

The fix generates a relative path from the output bndrun file's location to the
input bndrun file. This makes the generated file portable across different
machines and CI environments, and thus safe for caching.

The relative path approach is also aligned with bnd's documentation which
recommends using relative paths for portability.
@chrisrueger
chrisrueger marked this pull request as draft October 15, 2026 09:29

@bjhargrave bjhargrave left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure I would change to use relative files. For gradle I would simply annotate the output bndrun file as non-cacheable.

@chrisrueger

Copy link
Copy Markdown
Contributor Author

Thanks for the feedback. I come up with another PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bndrun file is cached by Gradle

2 participants