Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: exclude project maven dependencies from isolated class loader (#20523) (CP: 24.5) #20529

Merged
merged 1 commit into from
Nov 21, 2024

Conversation

vaadin-bot
Copy link
Collaborator

No description provided.

…20523)

If the user project directly or transitively depends on maven artifacts,
mojos can fail at runtime because of Maven API loaded from both isolated
class loader and maven.api realm.
This change prevents maven artifacts from being added to the isolated class loader.
@vaadin-bot
Copy link
Collaborator Author

This PR is eligible for auto-merging policy, so it has been approved automatically. If there are pending conditions, auto merge (with 'squash' method) has been enabled for this PR[Message is sent from bot]

@vaadin-bot vaadin-bot enabled auto-merge (squash) November 21, 2024 10:21
Copy link

sonarcloud bot commented Nov 21, 2024

Copy link

Test Results

1 147 files  ±0  1 147 suites  ±0   1h 26m 45s ⏱️ + 1m 23s
7 480 tests ±0  7 430 ✅ ±0  50 💤 ±0  0 ❌ ±0 
7 854 runs  +7  7 794 ✅ +7  60 💤 ±0  0 ❌ ±0 

Results for commit 31ec637. ± Comparison against base commit 233a222.

@vaadin-bot vaadin-bot merged commit 936db62 into 24.5 Nov 21, 2024
25 of 26 checks passed
@vaadin-bot vaadin-bot deleted the cherry-pick-20523-to-24.5-1732184033262 branch November 21, 2024 10:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants