问题描述
我只想在Eclipse中设置一个新的GWT项目，并使用Maven来处理所有的jar丛林。我使用了说明的gwt-maven-plugin，但我无法让项目在Eclipse中工作。
实际完成的工作：
gwt-maven-plugin：2.3.0- 1：generateAsync - 没有找到可处理的市场条目
gwt-maven-plugin：2.3.0-1：i18n - 没有找到可处理的市场条目
gwt-maven-plugin：2.3。 0-1：爆炸 - 没有找到处理市场的条目
即使我忽略了这些错误，这些错误也不会消失导入。
如何让这些项目能够正常工作？我跳过了流程资源设置的问题吗？ （最新版本的m2e中没有这样的设置。）
我应该使用gwt-maven-plugin吗？有没有其他方法可以让GWT项目使用Maven？或者 - ndash;有没有其他方式与罐丛林战斗？ GWT人使用什么？
我使用Eclipse Indigo和m2e插件1.0.0和Google套件插件2.3.3。
最终我放弃了Maven。正如另外一位开发人员所说，，我还记得我在所有项目中使用Maven的经验：开始时非常有希望，但最终你会遇到一些问题，最终配置Maven的工作比实际处理自己的代码更多。
我决定手动将所需的.jar-s复制到/ lib文件夹中。我花了一些时间，由于传递性依赖，但是LESS不及处理Maven，现在我已经掌握了一些东西。如果将来某个时候与图书馆合作会变成开销，我会考虑使用。
如果有人希望坚持使用Maven，我最近发现了Google团队非常有用的链接：
他们推荐使用他们的示例项目，而不是gwt- maven-plugin原型（由于问题）。我同意。他们还为Eclipse Indigo提供了所需的pom生命周期更改。
I would just like to setup a new GWT project in Eclipse and use Maven for dealing with all the jar jungle. I used gwt-maven-plugin with this instructions, but I can't get the project to work in Eclipse.
What I've actually done:
- Created a maven project using the archetype gwt in command line.
- Imported the projet in eclipse using import > existing maven project
- While doing that I had errors saying:
gwt-maven-plugin:2.3.0-1:generateAsync - "No marketplace entries found to handle" gwt-maven-plugin:2.3.0-1:i18n - "No marketplace entries found to handle" gwt-maven-plugin:2.3.0-1:exploded - "No marketplace entries found to handle"
These errors don't go away even if I ignore them on the import.
How can I make these projects working? Is the problem that I skipped the "process-resources" setting? (There is no such setting in the latest version of m2e.)
Should I even use gwt-maven-plugin? Is there any other way of making a GWT project to use Maven? Or – is there any other way to fight with the jar jungle? What does GWT guys use?
I use Eclipse Indigo with m2e plugin 1.0.0 and Google suite plugin version 2.3.3.
Eventually I gave up Maven. As one other developer said "good ideas and bad code build communities faster" , I also remember my experience with Maven on all the projects: very promising on the beginning, but eventually you get to some problems and end up working more with configuring Maven than actually dealing with your own code.
I decided to manually copy needed .jar-s into /lib folder. I spent some time due to transitive dependencies, but LESS than dealing with Maven and now I have things under control. If sometime in the future working with libraries will become an overhead, I will consider using Ivy.
If someone wishes to stick with Maven, I lately found a very useful link by Google team:http://code.google.com/p/google-web-toolkit/wiki/WorkingWithMaven
They recommend using their sample projects and not gwt-maven-plugin archetypes (due to issues). I agree. They also provide needed pom lifecycle changes for Eclipse Indigo.
这篇关于Eclipse Indigo的gwt-maven插件的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！