STS M2E“生命周期配置未涵盖插件执行”错误 - Flex-Mojos
我正在尝试为多模式 Flex 应用程序编写 pom.xml。我一直使用此资源作为示例：
http://www.sonatype.com/books/mvnref-book/reference/flex-dev-sect-creating-with-archetype.html
我正在使用 M2E v1.01 但我我面临着许多“生命周期配置未涵盖的插件执行”错误。据我所知 - 没有 m2E 连接器可用于解决此问题，并且我已尝试了我能找到的所有 Maven 建议 - 包括：
- Clean
- Update依赖
- 项 更新项目配置
仅当项目声明为 swc 或 swf 包时才会出现问题 我的下一步行动。要求 Eclipse“将目标永久标记为忽略'-这似乎有点鲁莽。
。
提前感谢您
I am trying to write my pom.xml for a multimodal flex application. I have been using this resource as an example:
http://www.sonatype.com/books/mvnref-book/reference/flex-dev-sect-creating-with-archetype.html
I am using M2E v1.01 but I am faced with a number of 'Plugin execution not covered by lifecycle configuration" errors. As far as I can see - there are no m2E connectors available to resolve this and I have tried all the Maven advice I can find - to include:
- Clean
- Update dependencies
- Update project configuration
The problem only occurs if the project is declared as swc or swf package. My next move to ask Eclipse to 'permanently mark goal as ignored' - which seems a little brash.
Any advice would be appreciated.
Thanks in advance.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
在STS 2.8.0中，我们将m2eclipse升级到1.0版本。然而，这可能会给现有项目带来一些麻烦。几个月前我写了一篇关于此的博客。
http: //blog.springsource.org/2011/10/18/upgrading-maven-integration-for-springsource-tool-suite-2-8-0/
本质上，m2eclipse的新架构需要您使用的每个 Maven 插件都必须映射到一个 Eclipse 插件，以处理该插件在 Eclipse 内的执行。这显然会导致问题，因为并非每个 Maven 插件作者都有知识或时间来创建、创建和维护 Eclipse 插件。
通过将插件标记为忽略，您是在说该插件永远不应在 Eclipse 内部执行（这意味着每当您需要执行它时，您都可以从命令行执行此操作）。一旦标记为
ignored，您就可以将其更改为execute，这意味着只要在 Eclipse 中执行关联的生命周期，它就应该始终执行。这可能会导致性能问题，因此只有在了解风险的情况下才这样做。如果这一切对您来说太多了，那么 STS 提供了一个降级选项来恢复到 m2eclipse 的旧版本。转到仪表板扩展页面。不幸的是，您必须手动恢复对 .project 和 .classpath 文件的所有更改（我们提供自动升级机制，但不提供降级机制......大概所有内容都在版本控制中）。
任何疑问或问题应发送至 STS 论坛：
http://forum.springsource.org/forumdisplay.php?32-SpringSource -工具套件
With STS 2.8.0, we have upgraded m2eclipse to be version 1.0. However, this can cause a bit of trouble with existing projects. I wrote a blog on this a couple of months ago.
http://blog.springsource.org/2011/10/18/upgrading-maven-integration-for-springsource-tool-suite-2-8-0/
Essentially, the new architecture for m2eclipse requires that each maven plugin you use must be mapped to one Eclipse plugin to handle the plugin's execution inside of Eclipse. This obviously causes problems since not every maven plugin author has the knowledge or time to create also create and maintain an Eclipse plugin.
By marking the plugin as ignored, you are saying that the plugin should never be executed inside of Eclipse (implying that whenever you need it to be executed, you will do so from the command line). Once marked as
ignored, you can then change it toexecute, which means that it should always be executed whenever the associated lifecycle is performed in Eclipse. This may cause performance problems, and so only do it if you know the risks.If all this is too much for you, then STS provides a downgrade option to revert to an older version of m2eclipse. Go to the Dashboard extensions page. Unfortunately, you will have to manually revert all changes to your .project and .classpath files (we provide an auto-upgrade mechanism, but not a downgrade mechanism...presumably everything is in version control).
Any questions or problems should be sent to the STS forums:
http://forum.springsource.org/forumdisplay.php?32-SpringSource-Tool-Suite
您可以在 eclipse 市场上查看此 alpha 连接器“Flex Maven Integration for Flash Builder”：http://marketplace。 eclipse.org/node/648556。
You can check this alpha connector "Flex Maven Integration for Flash Builder" on the eclipse marketplace: http://marketplace.eclipse.org/node/648556.