hi i found another two verry simple issues :) i think there should be a space between "gwt-dev-1.5.2-windows- libs.zip" and "to" in this message:
[INFO] Unpacking .../com/google/gwt/gwt-dev/1.5.2/gwt-dev-1.5.2- windows-libs.zipto ..../com/google/gwt/gwt-dev/1.5.2 and is it really needed that the gwt-dev-windows files are <activeByDefault>true</activeByDefault> ?? or is this just another mistake in the documentation?? :) i found this on the setup page, in the "Automatic Mode Setup" section, where you describe the profile configuration http://gwt-maven.googlecode.com/svn/docs/maven-googlewebtoolkit2-plugin/setup.html jens On 9 Sep., 01:51, Charlie Collins <[EMAIL PROTECTED]> wrote: > I found my missing dependency issue, and it was my own stupidity - too > bad Maven isn't smart enough to just tell me HOW I am being > stupid ;). > > The deal is thus, if you get strange NPEs, make sure your gwtVersion > in the maven-googlewebtoolkit2-plugin configuration MATCHES what your > dependencies are. In the sample project gwtVersion was NOT SET AT > ALL, and the DEFAULT is 1.5.1. The deps were set to 1.5.2. This > caused the injection mechanism to find the 1.5.2,s but somehow cause > an NPE deep inside of Maven during the resolve phase (I am checking > all sorts of ways to determine if dep is not there and send a useful > error message, etc, dep IS there, long story). > > So, for now, I am updating the site docs and so on (along with the > other fixes to docs noted in this thread). MAKE SURE your gwtVersion > that you pass to plugin config matches the version you use for the > deps, or bad things happen. In this case all I had to do was add a > gwtVersion section to the plugin config for 1.5.2, and it worked. > > In the future I will try to make the error handling more robust (tell > you what's missing), but I think this one is more on the Maven side > than the GWT-Maven side. > > The good news is, nothing is really broken with the plugin itself > (and, I also updated the default version to 1.5.2 in source, so next > rev will have that). > > I will be publishing new docs later tonight. > > On Sep 8, 7:17 pm, Charlie Collins <[EMAIL PROTECTED]> wrote: > > > Ok, after clearing out my local repo (renaming it) on a few machines > > and trying from scratch I ran into a few serious issues. > > > I get a NullPointerException from the merge web xml stuff in the maven- > > googlewebtoolkit2-sample project (the one with inheritance, not the > > simplesample, actually the war sub-project specifically). > > > If I switch back my repo things work again, so something is missing > > from a clean slate for the non simple sample - bad news. I tried to > > troubleshoot it, but as usual with Maven, it's a nightmare. With the - > > e and -X and so on I can see that the problem is ultimately this: > > > Caused by: java.lang.NullPointerException > > at > > org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java: > > 296) > > at > > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java: > > 194) > > at > > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java: > > 73) > > at > > com.totsp.mavenplugin.gwt.util.BuildClasspathUtil.injectGwtDepsFromRepo(BuildClasspathUtil.java: > > 173) > > at > > com.totsp.mavenplugin.gwt.util.BuildClasspathUtil.buildClasspathList(BuildClasspathUtil.java: > > 75) > > at > > com.totsp.mavenplugin.gwt.AbstractGWTMojo.fixThreadClasspath(AbstractGWTMojo.java: > > 321) > > > But, I changed out the behavior of injectGwtDepsFromRepo a few times, > > and verified in it that gwtDev and gwtUser are NOT null, and neither > > is localRepository or resolver, and I still get the NPE from other > > areas, back to DefaultWagonManager. Then if I look carefully at my X > > output I see that I am using maven-artifact-plugin 2.0 - NOT 2.0.9 or > > 2.0.4 or whatever. Yet, I can't find a src xref for plain 2.0. All I > > can get to is > > this:http://maven.apache.org/ref/current/maven-artifact-manager/xref/org/a.... > > It says "// TODO [BP]: The exception handling here needs some work" in > > the neighborhood, but I can't really tell exactly what the error is, > > yet. Don't get me wrong, I am sure it's something stupid I AM DOING, > > somewhere, but I Maven just makes me want to stab a pencil in my eye > > sometimes when it comes to chasing things down. > > > When I get a chance I will compare what's different between the repos > > and try to figure it out more - and run Maven in a debugger. For now, > > FYI - the new version does have some issues in some scenarios. > > > On Sep 8, 3:21 pm, Charlie Collins <[EMAIL PROTECTED]> wrote: > > > > AS to plugin repositories, yes, we probably do. I haven't cleared out > > > (or moved) my entire repo in a while, I will do that on a few > > > platforms to test. > > > > I will also check if the java.net one is still needed. At one time it > > > was, due to some transitive dependency from the support jar or > > > something - but that may no longer be the case. On the other hand we > > > may need to ADD one for JDOM 1.1, last I checked (which was a few > > > weeks back), it still wasn't in central. > > > > I am adding an issue for this, and will handle it when I can. > > > > On Sep 8, 10:43 am, "Mirko Nasato" <[EMAIL PROTECTED]> wrote: > > > > > Hi Charlie, > > > > > In the sample configuration > > > > >http://gwt-maven.googlecode.com/svn/docs/maven-googlewebtoolkit2-plug... > > > > > don't we need a <pluginRepositories> in addition to <repositories>? I > > > > had to > > > > add it to my pom.xml. > > > > > Also is the java.net repository really needed? At least gwt:compile > > > > works > > > > fine without it. > > > > > Thanks > > > > > Mirko > > > > > 2008/9/8 Charlie Collins <[EMAIL PROTECTED]> > > > > > > Docs updated in source, will get them republished later today (the big > > > > > one there is the "compile" phase for the dependency plugin, that's > > > > > essential). > > > > > > On Sep 8, 9:49 am, Charlie Collins <[EMAIL PROTECTED]> wrote: > > > > > > 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]> > > ... > > Erfahren Sie mehr » --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
