Comments (6)
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
from gwt-maven-plugin.
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 mojogenerate-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 POMgenerate-module
should run incrementally, but has to be updated with staleness checkimport-sources
andimport-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
- importing
compile
,test
andpackage-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
from gwt-maven-plugin.
@branflake2267 Could you remove the configuration from your POM and try with the latest master?
from gwt-maven-plugin.
Wow, good job. I'll do that immediately. :)
from gwt-maven-plugin.
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. :)
from gwt-maven-plugin.
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. :)
from gwt-maven-plugin.
Related Issues (20)
- Version 1.0.0 do not support GWT 2.1.0 HOT 5
- Lombok not working with codeserver HOT 2
- Custom Linkers? HOT 2
- Source path from Inherited GWT.xml files are not being considered HOT 13
- GWT compilation failing with error, tried upgrading guice to 4.0 from 3.0 HOT 3
- Integration with GWT Eclipse Plugin seems partially broken HOT 6
- GWT 2.9.0 HOT 2
- GWT Multimodule modulename specificaiton HOT 1
- Redirected gwt artifacts cause a NPE when generating modules HOT 4
- Cannot compile GWT project using com.google.gwt:2.10.0-new-groupid-2 HOT 4
- API incompatibility issue with version 1.0.1 HOT 2
- Change default structure? HOT 2
- java process doesn't start. HOT 1
- Critical CVEs detected in transitive jar dependencies. HOT 1
- Validation warning, plugin should declare these Maven artifacts in `provided` scope HOT 1
- Upgrade to GWT 2.10.0 HOT 3
- goal codeserver fails when web app dependencies are managed in a BOM pom HOT 3
- [Question] How can i activate the debug logging ? because i keep getting the error: Hint: Check the inheritance chain from your module; it may not be inheriting a required module or a module may not be adding its source path entries properly HOT 5
- Release versión with GWT 2.11.0 support HOT 2
- [Question] Can I hide the devmode gui? HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from gwt-maven-plugin.