Review Ben's issues about gwt-eclipse-plugin HOT 2 CLOSED

• Better way to get Eclipse into a good state
  • A way to install all plugins needed at once?
  • Setting up a correct PDE Eclipse Application launch config
    • Currently fails with "Error: Could not find or load main class Files"
      and no other details
  • .classpath for all plugins was modified upon import, can this break things?
    • Output path changed from "bin" to "target/classes"
  • When exporting "A cycle was detected when generating the classpath"
    • e.g for Google Web Toolkit Plugin project
      • gwt.eclipse.core
      • gcp.eclipse.testing
      • appengine.eclipse.core
      • gdt.eclipse.maven
      • gwt.eclipse.core
    • Fixed by closing all test related projects.
      • No idea what's going on here, quite confused by this
  • Weirdness with plugin dependencies view in Eclipse
    • Listing com.google.gwt.eclipse.libs twice, removing either breaks build
    • Eventually appeared to resolve itself after fiddling a while
      now only one instance of com.google.gwt.eclipse.libs is present
  • Are any plugin projects' build.xml custom?
    • I get prompted to delete them when exporting the GPE feature, are the
      necessary properties set in the appropriate build.xml for those projects
      where this is relevant?
  • Once exported as best I can figure out, actually loading the plugin fails
    • Unable to acquire PluginConverter service during generation for: T:\Programs\eclipse4test-gwt-plugin\dropins\GWT

from gwt-eclipse-plugin.

mvn package or mvn install will build features and stick the im the repo/target/repository
mvn verify will verify the plugins.

Application launch config will originate from the suite plugin. Not sure why that glitching yet.

.classpath, .settings, .project came from GPE originally. I'm hoping they can be removed at some point in replace of importing

Internal Eclipse builds will fail at the moment. I've noticed the cyclic dependency when I tried it. I may have possibly done this without noticing the error in the maven lifecycle or it came that way. I haven't noticed the IDE problems complaining yet. But I've had enormous amount of issues I've already put to sleep to get this far. Looks like some tuning is needed. It works in the tycho builds, so I haven't noticed.

Dependencies could be screwy, I haven't examined that. I've got my own wish list of rip outs.

build.xml came from the internal build system at Google. I've left it for the time being. Something on the todo list.

http://146.148.64.240:8080/ - successful builds can be found in the fork here. It might be of interest to check the build log for the output of how they go down. (mvn verify or mvn install) what I use to package the artifacts.

I tested the release repo today. http://storage.googleapis.com/gwt-eclipse-plugin/release Things are working nicely from here.

I know the feeling about setting up this project's plugins. I've nearly quit this project several times. Although I've been slowly working out the issues.

There are hard coded env vars. If you notice in the readme what those are. I've added two to the maven download process so if they exist in the resources plugin, Eclipse will use those instead of the system properties. The system properties won't load on a mac unless there exported and eclipse is ran from the terminal.

@OneGeek

from gwt-eclipse-plugin.