Skip to content

Revert change from #480 - plugin dependencies must be resolved from plugin repositories#496

Merged
slawekjaranowski merged 1 commit intomasterfrom
rev-480
Oct 5, 2025
Merged

Revert change from #480 - plugin dependencies must be resolved from plugin repositories#496
slawekjaranowski merged 1 commit intomasterfrom
rev-480

Conversation

@slawekjaranowski
Copy link
Copy Markdown
Member

revert a change from:

add comments in code

@slawekjaranowski slawekjaranowski added this to the 3.6.1 milestone Oct 4, 2025
@Marcono1234
Copy link
Copy Markdown
Contributor

Marcono1234 commented Oct 4, 2025

Thanks! I have created #497 for adding an IT which relies on this, to verify that this does not break by accident in the future. Hopefully that is helpful.

@slawekjaranowski slawekjaranowski merged commit 02e72e2 into master Oct 5, 2025
29 checks passed
@slawekjaranowski slawekjaranowski deleted the rev-480 branch October 5, 2025 14:24
collectRequest.setRoot(new Dependency(RepositoryUtils.toArtifact(executableArtifact), classpathScope));
collectRequest.setRepositories(project.getRemoteProjectRepositories());
// as this method is called only determineRelevantPluginDependencies, se we need a plugin repository here
collectRequest.setRepositories(project.getRemotePluginRepositories());
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

small typo: "se" should be "so"...

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