This repository was archived by the owner on Dec 12, 2025. It is now read-only.
Add middleware to support Maven-managed dependencies on Fiori Pipeline #728
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change adds a middleware definition to support libraries with dependencies during builds on the Fiori Pipeline.
Currently the pipeline copies dependencies into the project's src directory to run test automation. This causes the framework to fail to initialize because of conflicting manifest.json files.
Since the files are already consolidated into the Maven target directory at target/dependency/META-INF/resources, using a middleware to retrieve dependency files from there instead of placing them in the src directory resolves the build failure.