[gwt-contrib] Re: 1.3.1 gwt-maven-plugin in 2.1.0 M1 ??
That's fine, I just wanted to ensure changes would be sent back to codehaus Jira to avoid some sort of fork - we allready hardly merged the codehaus googlecode gwt-maven plugins ! I'd be pleased to help if you plan to support some SDK features in an official GWT Maven plugin The codeHaus plugin is complex because it supports all GWT 1.4+ releases from same code base. A maven plugin developped/deployed in sync with the SDK would be far simplier. It also overlap with some features of Google Eclipse plugin (ex: Async interface generation) that may be reused as is. Maybe you could start a poll/moderator to check how many GWT developpers are Maven users and what they think about Maven support in GWT ? Nicolas On 21 mai, 01:26, Ray Cromwell cromwell...@gmail.com wrote: Nicolas, Sorry I didn't give you a heads up, I had to patch some things at the last minute for Google I/O Keynote, and I did not think there was sufficient time to turn around a patch and get it committed, so temporarily, there's a forked maven plugin (the version # 1.3.1.google should give it away that it's s one-off), but in due time, after I decompress from I/O, I'll send you my changes, and you can tell me if they're necessary or not, or if there is an alternative workaround. -Ray On Tue, May 18, 2010 at 3:56 AM, nicolas de loof nicolas.del...@gmail.com wrote: Hi I'm the maintainer of codehaus-mojo gwt-maven-plugin and I wonder the plugin is deployed with a 1.3.1.google version at http://google-web-toolkit.googlecode.com/svn/2.1.0.M1/gwt/maven/ Is it a internal release of the codehaus trunk to get a fixed version, or a custom build with some fixes ? Do you plan to add support for Maven as a standard GWT feature ? I'd be pleased to contribute and deprecate the mojo plugin in such case. Nicolas -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --http://groups.google.com/group/Google-Web-Toolkit-Contributors -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] Re: 1.3.1 gwt-maven-plugin in 2.1.0 M1 ??
Not the best way to help Maven users :-/ install-file goal is designed to setup a local repository, not to create a public shared one. Please consider writing pom.xml files with complete metadatas. NB: providing maven metadata and artifact deployment does NOT require the project itself to be built using Maven On 18 mai, 15:21, Thomas Broyer t.bro...@gmail.com wrote: On 18 mai, 14:14, nicolas de loof nicolas.del...@gmail.com wrote: I also notice the POM used to publish GWT artifacts is limited to required data, but does not include what is expected for a valid artifact to be deployed on maven central (license, SCM url, mailing lists...) and can be used by various tools (including m2eclipse) to help developers. Maybe they have just been generated using a mvn deploy:deploy-file ? I don't know Maven, but I'd say they've been generated using mvn install:install-file from this script:http://code.google.com/p/google-web-toolkit/source/browse/branches/2 --http://groups.google.com/group/Google-Web-Toolkit-Contributors -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] Re: 1.3.1 gwt-maven-plugin in 2.1.0 M1 ??
I understand that adding the maven artifact to the svn repo might not have been to help users. It would be nice to know what the GWTers are thinking about this... Is Maven integration on a roadmap? is it just being proposed/tested? It's okay if there's no promises, and if we shouldn't rely on maven artifacts in the repo; it'd just be nice to know what's going on. On May 20, 4:51 am, nicolas.deloof nicolas.del...@gmail.com wrote: Not the best way to help Maven users :-/ install-file goal is designed to setup a local repository, not to create a public shared one. Please consider writing pom.xml files with complete metadatas. NB: providing maven metadata and artifact deployment does NOT require the project itself to be built using Maven On 18 mai, 15:21, Thomas Broyer t.bro...@gmail.com wrote: On 18 mai, 14:14, nicolas de loof nicolas.del...@gmail.com wrote: I also notice the POM used to publish GWT artifacts is limited to required data, but does not include what is expected for a valid artifact to be deployed on maven central (license, SCM url, mailing lists...) and can be used by various tools (including m2eclipse) to help developers. Maybe they have just been generated using a mvn deploy:deploy-file ? I don't know Maven, but I'd say they've been generated using mvn install:install-file from this script:http://code.google.com/p/google-web-toolkit/source/browse/branches/2 --http://groups.google.com/group/Google-Web-Toolkit-Contributors --http://groups.google.com/group/Google-Web-Toolkit-Contributors -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
Re: [gwt-contrib] Re: 1.3.1 gwt-maven-plugin in 2.1.0 M1 ??
To add a bit of color here, we patched the existing plugin so that gwt:run would work with Roo generated code. We decided to host it in our repo simply because we were short on time leading up to I/O. With that (almost) behind us, our plan is to work with the codehaus-mojo team/project to formerly submit our changes to their source base. Regarding Maven support: Our announced integration with VMware, and more specifically the SpringSource community, will inevitably lead to a tighter integration between GWT and Maven. While we don't have Maven features spec(ed) out as this point, we anticipate that as we move from from 2.1 M1 to 2.1 GA there may be changes within the SDK and/or GPE that are necessary. -- Chris On Thu, May 20, 2010 at 4:25 AM, Nathan Wells nwwe...@gmail.com wrote: I understand that adding the maven artifact to the svn repo might not have been to help users. It would be nice to know what the GWTers are thinking about this... Is Maven integration on a roadmap? is it just being proposed/tested? It's okay if there's no promises, and if we shouldn't rely on maven artifacts in the repo; it'd just be nice to know what's going on. On May 20, 4:51 am, nicolas.deloof nicolas.del...@gmail.com wrote: Not the best way to help Maven users :-/ install-file goal is designed to setup a local repository, not to create a public shared one. Please consider writing pom.xml files with complete metadatas. NB: providing maven metadata and artifact deployment does NOT require the project itself to be built using Maven On 18 mai, 15:21, Thomas Broyer t.bro...@gmail.com wrote: On 18 mai, 14:14, nicolas de loof nicolas.del...@gmail.com wrote: I also notice the POM used to publish GWT artifacts is limited to required data, but does not include what is expected for a valid artifact to be deployed on maven central (license, SCM url, mailing lists...) and can be used by various tools (including m2eclipse) to help developers. Maybe they have just been generated using a mvn deploy:deploy-file ? I don't know Maven, but I'd say they've been generated using mvn install:install-file from this script: http://code.google.com/p/google-web-toolkit/source/browse/branches/2 --http://groups.google.com/group/Google-Web-Toolkit-Contributors --http://groups.google.com/group/Google-Web-Toolkit-Contributors -- http://groups.google.com/group/Google-Web-Toolkit-Contributors -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] Re: 1.3.1 gwt-maven-plugin in 2.1.0 M1 ??
I also notice the POM used to publish GWT artifacts is limited to required data, but does not include what is expected for a valid artifact to be deployed on maven central (license, SCM url, mailing lists...) and can be used by various tools (including m2eclipse) to help developers. Maybe they have just been generated using a mvn deploy:deploy-file ? Cheers, Nicolas 2010/5/18 nicolas de loof nicolas.del...@gmail.com Hi I'm the maintainer of codehaus-mojo gwt-maven-plugin and I wonder the plugin is deployed with a 1.3.1.google version at http://google-web-toolkit.googlecode.com/svn/2.1.0.M1/gwt/maven/ Is it a internal release of the codehaus trunk to get a fixed version, or a custom build with some fixes ? Do you plan to add support for Maven as a standard GWT feature ? I'd be pleased to contribute and deprecate the mojo plugin in such case. Nicolas -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] Re: 1.3.1 gwt-maven-plugin in 2.1.0 M1 ??
On 18 mai, 14:14, nicolas de loof nicolas.del...@gmail.com wrote: I also notice the POM used to publish GWT artifacts is limited to required data, but does not include what is expected for a valid artifact to be deployed on maven central (license, SCM url, mailing lists...) and can be used by various tools (including m2eclipse) to help developers. Maybe they have just been generated using a mvn deploy:deploy-file ? I don't know Maven, but I'd say they've been generated using mvn install:install-file from this script: http://code.google.com/p/google-web-toolkit/source/browse/branches/2.1/bikeshed/scripts/maven_script.sh -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
