I didn't know about the <param> vs <value> thing, I will look into that.
As for the unpacking phase, yes, it should be compile (I originally had it unpack, and ran into errors myself) - I will update the documentation ASAP. I will also update the other doc inconsistency you noted. On Sep 8, 8:05 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > hi guys, > > first of all great work!! :) > > today i switched from 2.0-beta-20 to beta-22, but have some strange > issues... but now anyhing works - especially the GwtTestCase (thats > really great) > > i found some little mistakes in the new documentation > > on the page: > > http://gwt-maven.googlecode.com/svn/docs/maven-googlewebtoolkit2-plug... > > you write "<gwtVersion>1.5.1</gwtVersion>" on any other page it is > <gwtVersion>${gwtVersion}</gwtVersion> > > i know you spend a lot of time to create the, really nice, new > documentation.... but i think a migration-guide from version to > version would also be a nice thing - i have searched hours to find a > failure in my pom > > in beta-20 the compileTarget option is named > > <compileTargets> > <param>_module_path_</param> > </compileTargets> > > and in beta-22 it is names > > <compileTargets> > <value>_module_path_</value> > </compileTargets> > > the strange thing is, if i start the simplesample application with > "mvn gwt:gwt" and then start my own app with "mvn gwt:gwt" anything > works, but if i clean up my local repository and start my own app i > get an NullPointerException > > and on the same page in the automatic setup section you write > > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-dependency-plugin</artifactId> > <executions> > <execution> > <id>unpack</id> > <phase>package</phase> > ........ > </plugin> > > but in the simplesample it is > > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-dependency-plugin</artifactId> > <executions> > <execution> > <id>unpack</id> > <phase>compile</phase> > ........ > </plugin> > > if i use the <phase>package</phase> option i also get an nullpointer > exception :/ > > but how i mentioned before now anythings works and am going on to use > the beta-22 - with GwtTestCases - WOHOO!!! :D > > jens > > On 8 Sep., 02:00, Charlie Collins <[EMAIL PROTECTED]> wrote: > > > Yep, let's put this one through the paces. After some time of using > > this one I am hoping we will find out it's pretty stable, and then we > > will make a non beta release (hopefully). Once that happens, I will > > then push to get GWT-Maven itself in the central repo. > > > As usual, please report any issues - and patches are welcome ;). > > > (One last thing I should have noted before, 2.0-beta22 is NOT backward > > compatible, you will have to update your POMs to use it - I know Mirko > > know this, I am just adding it for general info for everyone else.) > > > On Sep 7, 10:04 am, "Mirko Nasato" <[EMAIL PROTECTED]> wrote: > > > > Great news! So tomorrow I can switch our projects back to use an official > > > gwt-maven release, rather than the snapshot I deployed internally as a > > > temporary measure. ;-) > > > > 2008/9/7 Charlie Collins <[EMAIL PROTECTED]> > > > > > New version, with a lot of refactoring, and fixes for many issues, is > > > > now available in the repo: > > > > >http://gwt-maven.googlecode.com/svn/trunk/mavenrepo/com/totsp/gwt/mav... > > > > > This version > > > > 1. Works with GWT 1.5.2 from central repo > > > > 2. Does the "automatic" mode processing differently, using the > > > > dependency plugin > > > > 3. Has rewritten GWTTestCase support (which does script writing like > > > > other mojos) > > > > 4. Has I18N support > > > > 5. Was refactored to remove a lot of duplicated code and use a few > > > > interfaces and abstract classes and such so it is easier to understand > > > > and work with when you are looking at the source > > > > 6. Addresses about 15 or so issues from the tracker > > > > 7. Does NOT supoort the bean generation stuff anymore (there were too > > > > many issues, and we no longer have a maintainer for that - so it is > > > > gone until further notice - if the maintainer comes back, or someone > > > > else wants to volunteer - and we address all the issues [see tracker] > > > > then it will be back). > > > > > This version was based on all the work and input done in the recent > > > > refactoring branch: > > > >http://groups.google.com/group/gwt-maven/browse_thread/thread/83664ca... > > > > . > > > > Thanks to Mirko and Arthur, and others for help and testing, etc. > > > > > Check out the docs: > > > >http://gwt-maven.googlecode.com/svn/docs/maven-googlewebtoolkit2-plug... > > > > . > > > > (I am pretty proud of the docs ;) - we now have some that use the > > > > Maven standard, with all goals and properties, source xref, javadocs, > > > > and from there we expand on what it provides a bit.) > > > > > Also the samples are updated to use the new version: > > > > >http://gwt-maven.googlecode.com/svn/trunk/maven-googlewebtoolkit2-plu... > > > >http://gwt-maven.googlecode.com/svn/trunk/maven-googlewebtoolkit2-sam... > > > > > If you find issues, please note them here and via the tracker. > > > > > thanks --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "gwt-maven" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/gwt-maven?hl=en -~----------~----~----~----~------~----~------~--~---
