Question, Eclipse Lifecycle configuration using this plugin...

[tbroyer]

Question, Eclipse Lifecycle configuration using this plugin...

[branflake2267]

https://github.com/ArcBees/ArcBees-tools/tree/master/archetypes/gwtp-plugin2-basic - Generated the archetype from the project... I think I may need to work on it some more, but I've been working on them all day so I'll tidy this up more as I get my feet more wet with the new stuff. I'm thinking I should try to get the GPE plugin forked so I can work on the auto setup for your plugin.

mvn archetype:generate -DarchetypeGroupId=com.arcbees.archetypes \
-DarchetypeRepository=https://oss.sonatype.org/content/repositories/snapshots/ \
-DarchetypeArtifactId=gwtp-plugin2-basic-archetype \
-DarchetypeVersion=1.0-SNAPSHOT \
-DgroupId=com.projectname.project \
-DartifactId=new-project-name \
-Dmodule=Project

[tbroyer]

Ah, that's a good question. I hadn't yet thought about Eclipse integration.

• enforce-encoding should IMO be enabled, but no need to run it incrementally, it's a configuration-only mojo
• generate-module-metadata is similar, I don't think it has to run incrementally as I expect M2E to run configuration-only mojos when you modify the POM
• generate-module should run incrementally, but has to be updated with staleness check
• import-sources and import-test-sources will have to be split:
  • importing java-source dependencies can be disabled, the GPE would have to include the artifacts/projects in the classpath, or run the new mojos, when needed.
  • adding src/main/super as a resource has to run when configuring the project
  • I'm not sure what's best for the other sources: the GPE could do it just like for java-source dependencies
• compile, test and package-app shouldn't need anything special as they shouldn't generally be run from the IDE.

In addition, generate-module-metadata and generate-module will have to make use of org.sonatype.plexus.build.incremental.BuildContext.

Reference: http://wiki.eclipse.org/M2E_compatible_maven_plugins

As for the GPE, I don't it think it needs to be updated for this plugin, it should just wait (a bit) to work with the upcoming official plugin.
There's no need to fork the GPE too, one can simply make an Eclipse plugin that acts as a configurator for this plugin. See http://wiki.eclipse.org/M2E_Extension_Development

[tbroyer]

@branflake2267 Could you remove the configuration from your POM and try with the latest master?

[branflake2267]

Wow, good job. I'll do that immediately. :)

[branflake2267]

https://github.com/ArcBees/ArcBees-tools/pull/78 - I just deployed the archetype with out the eclipse config

I have a forking conflict with your repo, so I've got to figure out how to fork on github. I think I'll remove my other fork. Take me a few more moments to try against master. ... Nevermind, seems I'm confused, already have it. :)

[branflake2267]

I've got your code setup and fork management setup in my Eclipse. I've run out of time, so I'll take another look tonight. I need to start working with Sencha now, but more of this later sounds like fun. :) I'm assuming it works and I have the new config deployed too. :)