gwt-eclipse-plugin Unified the libs folder names.

Renamed all "lib" folders to "libs", to be unique across all plugins.

Dec 09 '22 16:12 keinhaar

I've rebased.

Feb 16 '23 15:02 keinhaar

@keinhaar, I wonder, if we should just remove the binary artifacts from the repository, and go the maven way.

For sure .classpath files and .project files can be recreated correctly by a simple maven import. For artifacts, it is a bit more tricky, but it should be possible.

Managing dependencies the way we're doing now is a bit of a nightmare

Feb 16 '23 16:02 protoism

Maybe, but i did not want to change the way things are done today. Just cleaning up. If you can do it with maven, feel free to do it. I don't use maven very much. So i can't do that.

Feb 17 '23 07:02 keinhaar

Hi @keinhaar, I marked this for 4.1, as this PR is really cosmetic, i.e. no bug fixed, no real improvement... nothing that we "forgot" on 4.0.0. I still wonder if we have to go all in with maven and remove all artifacts, but it requires time and patience... So.. if we fix https://github.com/gwt-plugins/gwt-eclipse-plugin/issues/454 this PR will simply be closed, otherwise it will go in for 4.1. Let me know if my proposal makes sense and if this makes development too complicate on your side

Mar 03 '23 10:03 protoism

if we fix #454 this PR will simply be closed, otherwise it will go in for 4.1.

Makes sense :-)

Mar 03 '23 15:03 keinhaar