Community
Participate
Working Groups
Build Identifier: 20110916-0149 We have custom plugins, requiring lifecycle-mapping's in the pom. This leads to annoying maven warnings whenever running mvn directly on a mojo (not a phase) from the command line. > [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 This would be easily solved if the pom (or some stub pom) for org.eclipse.m2e:lifecycle-mapping:1.0.0 were released into Maven central. Reproducible: Always Steps to Reproduce: 1. Define (or have m2e auto do it) some lifecyle-mapping metadata in a pom. <pluginManagement> <plugins> <!--This plugin's configuration is used to store Eclipse m2e settings only. It has no influence on the Maven build itself. --> <plugin> <groupId>org.eclipse.m2e</groupId> <artifactId>lifecycle-mapping</artifactId> <version>1.0.0</version> <configuration> <lifecycleMappingMetadata> ... 2. Run any direct mojo, eg mvn help:help
This dummy should help: mvn archetype:generate -DgroupId=org.eclipse.m2e -DartifactId=lifecycle-mapping -Dversion=1.0.0 -DarchetypeArtifactId=maven-archetype-mojo Generate the plugin project with the above command and install/deploy it
closing old/stale bugreports
Please compare with http://stackoverflow.com/questions/7905501/get-rid-of-pom-not-found-warning-for-org-eclipse-m2elifecycle-mapping and the following bug for source plugin (https://jira.codehaus.org/browse/MSOURCES-67). This indeed seems to happen, whenever a mojo-goal is directly executed. @Igor: Could you please comment on this issue? According to your post from http://permalink.gmane.org/gmane.comp.ide.eclipse.plugins.m2eclipse.user/6218 this should not happen with Maven. But indeed you can easily reproduce whenever you directly execute a Mojo goal (even with the most recent Apache Maven 3.1.1). Either we need to get that fixed within the Maven Core or a dummy artifact for lifecycle-mapping.jar should be uploaded to Maven Central.
This godforsaken bug (which has been around forever) still occurs. It's tremendously annoying to have to workaround this bug in every single project when you want a clean build.(In reply to Igor Fedorenko from comment #2) > closing old/stale bugreports
So, are we meant to open a new bug as this “old” one has been closed? It is still absolutely valid.
(In reply to Jan Klass from comment #5) > So, are we meant to open a new bug as this “old” one has been closed? > It is still absolutely valid. I'll be more than happy to reopen this bug if somebody provides a fix.
(In reply to Igor Fedorenko from comment #6) > (In reply to Jan Klass from comment #5) > > So, are we meant to open a new bug as this “old” one has been closed? > > It is still absolutely valid. > > I'll be more than happy to reopen this bug if somebody provides a fix. Isn't this what the "helpwanted" keyword is for? +1 that this needs to be re-opened, or it will just cause new duplicates to be opened in its place (as Jan has eluded to). Assume that I or someone else would have some time to work on squashing these types of bugs with submitted patches. As-is, if we search through the bug list looking for potential issues such as this to fix, they will never be found. Closed = no attention needed. This is not the case here. Please re-consider.
There was no interest in this bug for over a year before I closed it. Lets see reopening makes this issue important enough for somebody to contribute a patch. (if you are working on a patch, beware that m2e is moving contributions to gerrit, see bug 374665)
(In reply to Igor Fedorenko from comment #8) > There was no interest in this bug for over a year before I closed it. No one asked. :-) You just had a rare group of interested parties that didn't continually ask "Is it fixed yet? Is it fixed yet?". Thanks for the re-open. Can you please also add the "helpwanted" keyword?
I don't consider "is it fixed yet" a meaningful bug comment. Only new information and patches count towards bug's "liveliness" as far as I am concerned. We don't use "helpwanted" for m2e bugs. Feel free to pick any bug that is not assigned to anyone. You may want to comment on the bug that you are working on it, just in case someone else feels like working on the bug too.
So, what would be the desired fix? 1. Deploying the plugin to maven central. Although it will not change resulting code when building with maven, it solves the missing dependency. 2. Deploying a minimal bundle as the correct groupId and artifactId will have to be used, there will be two projects with the same groupId and artifactId in development - which is questionable. Are there other solutions? I guess 1. would be a rather easy fix. I guess would require one of the core devs/maintainers to manage maven central deployment.
(In reply to Jan Klass from comment #11) > So, what would be the desired fix? > > 1. Deploying the plugin to maven central. > Although it will not change resulting code when building with maven, it > solves the missing dependency. There is no plugin, so there isn't anything to deploy. > 2. Deploying a minimal bundle > as the correct groupId and artifactId will have to be used, there will be > two projects with the same groupId and artifactId in development - which is > questionable. This is doable, but involves quite of bit of leg work [1]. Personally, I don't want to spend non-trivial amount of time on a inconsequential problem like this, but maybe other m2e committers have different opinion. Few other solutions 3. Change maven to suppress the warning. 4. Change maven pom.xml format to directly support tooling specific configuration. This is the real solution, btw, everything else are workarounds that do not address the root cause of the problem. 5. Deploy the fake plugin to an alternative repository and use <plugin-repository> in the pom to make the repository visible. This is the easiest for me to do, so if somebody gives me the fake pom I can make it accessible through http://download.eclipse.org/technology/m2e/maven/ [1] https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide
As has been described in an earlier comment, I used > mvn archetype:generate -DgroupId=org.eclipse.m2e -DartifactId=lifecycle-mapping -Dversion=1.0.0 -DarchetypeArtifactId=maven-archetype-mojo and was able to deploy this to our repository, resolving the issue. So you should be able to do that to generate a valid package you can use.
I would rather like to have the issue fixed in Maven, since in my regard plugins listed only in pluginManagement should not be evaluated. Maybe someone could comment on the according bug in https://jira.codehaus.org/browse/MSOURCES-67.
(In reply to Jan Klass from comment #13) > As has been described in an earlier comment, I used > > > mvn archetype:generate -DgroupId=org.eclipse.m2e -DartifactId=lifecycle-mapping -Dversion=1.0.0 -DarchetypeArtifactId=maven-archetype-mojo > > and was able to deploy this to our repository, resolving the issue. > > So you should be able to do that to generate a valid package you can use. In order to not have to alter the pom configuration I deployed to a specific repository btw: $ mvn deploy -DaltDeploymentRepository=OWN_REPO_ID::default::OWN_REPO_URL
(In reply to Konrad Windszus from comment #14) > I would rather like to have the issue fixed in Maven, since in my regard > plugins listed only in pluginManagement should not be evaluated. Maybe > someone could comment on the according bug in > https://jira.codehaus.org/browse/MSOURCES-67. FYI, I moved the issue to maven core bucket, the new issue id is MNG-5564, but the old link should still work. I do not plan to work on a fix myself and I suggest any further discussions, proposed fixes, etc, happen on that bug and maven dev list. https://jira.codehaus.org/browse/MNG-5564
I am managing poms for a large project. Less-experienced developers continually add this eclipse-created hack into our poms. I keep taking it out -- it is garbage that has nothing to do with our software. This is an eclipse problem that eclipse needs to solve. They need to provide a plugin if there is one missing.
The workaround to use a Maven profile activated by the presence of the m2e.version property proposed in answer #3 of http://stackoverflow.com/questions/7905501/get-rid-of-pom-not-found-warning-for-org-eclipse-m2elifecycle-mapping is a viable short term "solution" for this: <profile> <id>only-eclipse</id> <activation> <property> <name>m2e.version</name> </property> </activation> <build> <pluginManagement> <plugins> <plugin> <groupId>org.eclipse.m2e</groupId> <artifactId>lifecycle-mapping</artifactId> <version>1.0.0</version> <configuration> ... </configuration> </plugin> </plugins> </pluginManagement> </build> </profile>
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
m2e 1.7 introduces a new syntax for lifecycle mapping metadata that doesn't cause this warning anymore: http://www.eclipse.org/m2e/documentation/release-notes-17.html#new-syntax-for-specifying-lifecycle-mapping-metadata <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>build-helper-maven-plugin</artifactId> <executions> <execution> <!-- This executes the goal in Eclipse on project import. Other options like are available, eg ignore. --> <?m2e? execute?> <phase>generate-sources</phase> <goals><goal>add-source</goal></goals> <configuration> <sources> <source>src/bootstrap/java</source> </sources> </configuration> </execution> </executions> </plugin>
IMO this bug has had no activity because people have given up hope. Reraised as https://bugs.eclipse.org/bugs/show_bug.cgi?id=541521 Push a pom to central, please.
Moved to https://github.com/eclipse-m2e/m2e-core/issues/
