Skip to content

[MNG-7572] Allow plugin descriptor to require loading extensions#833

Draft
kwin wants to merge 6 commits intomasterfrom
feature/plugin-descriptor-with-extensions
Draft

[MNG-7572] Allow plugin descriptor to require loading extensions#833
kwin wants to merge 6 commits intomasterfrom
feature/plugin-descriptor-with-extensions

Conversation

@kwin
Copy link
Copy Markdown
Member

@kwin kwin commented Oct 18, 2022

Following this checklist to help us incorporate your
contribution quickly and easily:

  • Make sure there is a JIRA issue filed
    for the change (usually before you start working on it). Trivial changes like typos do not
    require a JIRA issue. Your pull request should address just this issue, without
    pulling in other changes.
  • Each commit in the pull request should have a meaningful subject line and body.
  • Format the pull request title like [MNG-XXX] SUMMARY, where you replace MNG-XXX
    and SUMMARY with the appropriate JIRA issue. Best practice is to use the JIRA issue
    title in the pull request title and in the first line of the commit message.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Run mvn clean verify to make sure basic checks pass. A more thorough check will
    be performed on your pull request automatically.
  • You have run the Core IT successfully.

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

@kwin kwin force-pushed the feature/plugin-descriptor-with-extensions branch from f2cf092 to 20fe5ec Compare November 16, 2022 18:16
@kwin
Copy link
Copy Markdown
Member Author

kwin commented Jun 10, 2023

@gnodet Any idea how to make it work with reactor builds which are both building and using the same plugin? That used to work for certain edge cases with the old approach (which only required evaluating the pom.xml). Should we just fall back to pom.xml and log in the case where the artifact is not yet built at the time where the build extensions are being loaded?

// potentially a plugin with extensions?
if ( !plugin.isExtensions() && isBuildExtension == Boolean.FALSE )
{
Artifact pluginMainArtifact = resolveExtensionMainArtifact( plugin, repositories, session );
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

How to deal with exceptions here in case the plugin artifact cannot be found?

@jira-importer
Copy link
Copy Markdown

Resolve #8219

@slawekjaranowski slawekjaranowski added the waiting-for-feedback Waiting for 90 days until issues or pull request will be closed label Apr 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

waiting-for-feedback Waiting for 90 days until issues or pull request will be closed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants