To use a newer version of maven-hpi-plugin, either ensure that you are building your plugin against sufficiently newer version of Jenkins (such as the current LTS base 1.509) or explicitly add the following fragment in your plugin pom.xml. It is probably simpler to just upgrade to Juno or later. To resolve the problem in this manner, you need to use m2e 1.1 and newer AND you need to use maven-hpi-plugin 1.87 and newer.īeware that certain versions/editions of Eclipse bundles m2e by default, in those cases you cannot upgrade m2e by itself. maven-hpi-plugin 1.87 contains this definition, thereby avoding the errors. M2e 1.1 introduced a mechanism to allow Maven plugins to define how the plugins should be handled by m2e. Upgrade to m2e 1.1+ and use maven-hpi-plugin 1.87+ There are two ways to resolve this problem. If you are curious, see the write-up from m2e developers as to why they did this. This is because m2e wants to know how to deal with additional Maven plugins we use for building Jenkins plugins. When you import a Jenkins plugin project with m2e, you might see a number of errors reporting "Plugin execution not covered by lifecycle configuration". Plugin execution not covered by lifecycle configuration See Plugin tutorial#Eclipse for the recommended way of using Eclipse. This page collects common pitfalls and solutions for problems you may encounter while developing Jenkins plugins in Eclipse.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |