Remove eclipse configuration in pom.xml

[branflake2267]

Remove Eclipse specifics form pom.xml.

Instead the pom.xml can setup the clipse GWT plugin if done right.

For all the samples move the parent gwt config into the sample it self, as close as it would be as it would stand on its own.

This is what I use for the maps example and its easy to import project. https://github.com/branflake2267/GWT-Maps-V3-Api/blob/master/gwt-maps-showcase/pom.xml

[branflake2267]

Get the samples to stand more on there own, so they could be copied or used for building a project from.

[branflake2267]

The root pom.xml has m2e configuration, which I think is useful for Eclipse development. I think we could keep it and close this. Thoughts?

[christiangoudreau]

It's unused if not under eclipse... But I heard that we can use eclipse without it nowadays, could you confirm before merge?

[branflake2267]

Good point, I'll remove and see what it does. From what I find maven m2e works great for the most part. Although I like using IDEA for getting down in dirty with the pom.xml.

[branflake2267]

Lifecycle mapping is used in m2e. This makes it handy for workspace to automatically handle the maven steps while in workspace.