Move lifecycle-mapping plugin into Eclipse specific profile #616
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
org.eclipse.m2e:lifecycle-mapping plugin is used only when the project is edited in Eclipse IDE, it's not relevant for other maven invocation. Unfortunately it emits bellow warning during maven execution: [WARNING] The POM for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 is missing, no dependency information available [WARNING] Failed to retrieve plugin descriptor for org.eclipse.m2e:lifecycle-mapping:1.0.0: Plugin org.eclipse.m2e:lifecycle-mapping:1.0.0 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 So this patches moves the plugin invocation into its own profile, which is automatically invoked only when a project is loaded into Eclipse IDE. Signed-off-by: Martin Perina <mperina@redhat.com>
mwperina
requested review from
ahadas,
bennyz,
dangel101,
emesika,
liranr23,
ljelinkova and
smelamud
mwperina
added a commit
to mwperina/ovirt-engine
that referenced
this pull request
Sep 1, 2022
As a part of oVirt#616 lifecycle-mapping has been move into eclipse specific profile in root pom.xml, but unfortunately other places were missed. Signed-off-by: Martin Perina <mperina@redhat.com>
mwperina
added a commit
to mwperina/ovirt-engine
that referenced
this pull request
Sep 2, 2022
As a part of oVirt#616 lifecycle-mapping has been move into eclipse specific profile in root pom.xml, but unfortunately other places were missed. Signed-off-by: Martin Perina <mperina@redhat.com>
mwperina
added a commit
that referenced
this pull request
Sep 2, 2022
As a part of #616 lifecycle-mapping has been move into eclipse specific profile in root pom.xml, but unfortunately other places were missed. Signed-off-by: Martin Perina <mperina@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
org.eclipse.m2e:lifecycle-mapping plugin is used only when the project
is edited in Eclipse IDE, it's not relevant for other maven invocation.
Unfortunately it emits bellow warning during maven execution:
[WARNING] The POM for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 is missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for org.eclipse.m2e:lifecycle-mapping:1.0.0: Plugin org.eclipse.m2e:lifecycle-mapping:1.0.0 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0
So this patches moves the plugin invocation into its own profile, which
is automatically invoked only when a project is loaded into Eclipse
IDE.
Signed-off-by: Martin Perina mperina@redhat.com