Great, thank you Charlie, it works. Just one note, I think that the sample POM files shouldn't include compile in the goals for running gwt:gwt. It confused me for a while there because it was taking an awfully long time to launch hosted mode (it had to run the GWT compiler on the app for each launch of hosted mode). The compile goal should probably only run when you package the GWT app as a WAR file.
On Aug 28, 10:17 am, Charlie Collins <[EMAIL PROTECTED]> wrote: > I found the problem, the @requiresDependencyResolution in the GWTMojo > was provided. Not sure why (or even if I did it ;)). I changed it to > compile, and made one quick change to the BuildClasspathUtil, and it > works. That might give us too many dependencies in some contexts, > possibly, but it fixes this specific issue, and is arguably what we > will have to do. (I also updated the regular sample application to > use the new plugin and test this - (http://gwt- > maven.googlecode.com/svn/trunk/maven-googlewebtoolkit2-sample). > > Thanks for reporting this. > > ALSO NOTE - I changed the name of the build I just did to 2.0-beta22- > SNAPSHOT and removed the "ccbranch" one. I did this for 2 reasons, > one to avoid the latest version number thing brought up here, and two > to use the conventional SNAPSHOT so I can just overwrite the same one > if and when we find more issues. > > USE 2.0-beta22-SNAPSHOT for testing the branch (but this is NOT an > official GWT-Maven release, yet) > > On Aug 28, 9:22 am, Charlie Collins <[EMAIL PROTECTED]> wrote: > > > Ok, several things here. > > > First, I updated the normal sample app (http://gwt- > > maven.googlecode.com/svn/trunk/maven-googlewebtoolkit2-sample/) to use > > the new ccbranch of the plugin. I did this to test multi-module, > > including a GWT library from one project in another, and so on. I get > > exactly the same problem, the build runtime classpath isn't getting > > the compile scoped dependencies (those that are either scoped compile, > > or have nothing, which means they inherit default scope - compile). > > It should get the compile ones, as they are supposed to be available > > in ALL scopes (the runtime should ADD the runtime stuff, but not have > > just the runtime and above). > > > I will look at this ASAP. > > > On Aug 28, 9:12 am, Arthur Kalmenson <[EMAIL PROTECTED]> wrote: > > > > I tried Mirko's suggestion and it now the jars do include the source > > > files. I think I've also better understood the problem with the > > > classpaths. This seems to be a scoping issue (as you suggested). I > > > have the third party library scoped as provided so the gwt:compile > > > goal runs with it in the classpath: > > > > DEBUG SCRIPT CLASSPATH LIST > > > /home/arthur/.m2/repository/com/google/gwt/gwt-user/1.5.1/gwt- > > > user-1.5.1.jar > > > /home/arthur/.m2/repository/com/google/gwt/gwt-dev/1.5.1/gwt- > > > dev-1.5.1-linux.jar > > > /home/arthur/work/mshab/mshab-demo/src/main/java > > > /home/arthur/work/mshab/mshab-demo/src/main/resources > > > /home/arthur/work/mshab/mshab-demo/classes > > > /home/arthur/work/mshab/mshab-demo/target/classes > > > /home/arthur/.m2/repository/com/sinai/mshab/mshab-format/1.0- > > > SNAPSHOT/mshab-format-1.0-SNAPSHOT.jar > > > > However, when it gets to running gwt:gwt, the classpath changes and > > > doesn't include mshab-format: > > > > DEBUG SCRIPT CLASSPATH LIST > > > /home/arthur/.m2/repository/com/google/gwt/gwt-user/1.5.1/gwt- > > > user-1.5.1.jar > > > /home/arthur/.m2/repository/com/google/gwt/gwt-dev/1.5.1/gwt- > > > dev-1.5.1-linux.jar > > > /home/arthur/work/mshab/mshab-demo/src/main/java > > > /home/arthur/work/mshab/mshab-demo/src/main/resources > > > /home/arthur/work/mshab/mshab-demo/classes > > > /home/arthur/work/mshab/mshab-demo/target/classes > > > > This is why hosted mode says mshab-format.xml isn't in the classpath. > > > I tried to scope it as runtime, but that didn't do anything (except > > > not include it during the compile step). > > > > Regards, > > > Arthur Kalmenson > > > > On Aug 28, 5:27 am, Charlie Collins <[EMAIL PROTECTED]> wrote: > > > > > You can also use a source jar, if that is your preference, just so > > > > long as the source is on the classpath. I will try some third party > > > > lib stuff today to make sure it's not a classpath scope issue with the > > > > branch (which is possible - but I don't think that's it, just need to > > > > check). > > > > > On Aug 27, 4:35 pm, Arthur Kalmenson <[EMAIL PROTECTED]> wrote: > > > > > > Good point, I don't have the source code in my JAR. I created a > > > > > separate source jar using source:jar, placed that in my local repo and > > > > > made a dependency on it. Nevertheless, I'm still getting the same > > > > > errors. Maybe if I could package the class files and source files > > > > > together it might work (which is what I did when I was using Ant). > > > > > However, I looked around and I couldn't figure out how that would be > > > > > done. > > > > > > Regards, > > > > > Arthur Kalmenson > > > > > > On Aug 27, 3:51 pm, Charlie Collins <[EMAIL PROTECTED]> wrote: > > > > > > > I will try some third party modules too - I honestly haven't checked > > > > > > that yet. Just one thing before I look into it though, make sure > > > > > > your > > > > > > modules and dependencies have the SOURCE in them if they are GWT > > > > > > libraries (third party modules usually do, but if they are your own, > > > > > > either make sure the source is in them, or that you include a > > > > > > special > > > > > > source jar as a dependency). > > > > > > > On Aug 27, 3:00 pm, Arthur Kalmenson <[EMAIL PROTECTED]> wrote: > > > > > > > > OK, so while launching hosted mode works for a very small project > > > > > > > that > > > > > > > uses only GWT widgets, I get classpath issues when I start > > > > > > > importing > > > > > > > 3rd party modules in my .xml.gwt file. This third party module > > > > > > > lives > > > > > > > in my local repository and is included as a dependency in the > > > > > > > same way > > > > > > > gwt-user is included. However, when I run gwt:gwt, the hosted > > > > > > > mode log > > > > > > > shows that it was unable to inherit the third party module because > > > > > > > it's not in the classpath. I tried adding the module into the > > > > > > > compile > > > > > > > targets, but to no effect (and it doesn't make sense that it would > > > > > > > since the compilation should pick up the additional modules). I'm > > > > > > > not > > > > > > > sure if this is a problem with the new version or something that > > > > > > > I did > > > > > > > wrong... > > > > > > > > Regards, > > > > > > > Arthur Kalmenson > > > > > > > > On Aug 26, 3:17 pm, Charlie Collins <[EMAIL PROTECTED]> wrote: > > > > > > > > > If anyone can help with testing the branch > > > > > > > > -http://groups.google.com/group/gwt-maven/browse_thread/thread/d2e35d5... > > > > > > > > - it would be greatly appreciated. It does a few things > > > > > > > > differently > > > > > > > > (see the thread for details), and though it's more elegant, I > > > > > > > > am not > > > > > > > > sure it addresses all situations, as it hasn't been extensively > > > > > > > > tested > > > > > > > > - yet. > > > > > > > > > It's been around a few weeks though, and several people are > > > > > > > > using it > > > > > > > > successfully (myself included). > > > > > > > > > If you can, it would be much appreciated if you grab it, build > > > > > > > > it, and > > > > > > > > test it with some existing projects. > > > > > > > > > I want to get all the feedback I can, to address stuff, BEFORE > > > > > > > > it gets > > > > > > > > merged (I will get feedback after, that I am sure of, but > > > > > > > > trying to > > > > > > > > mitigate that if I can ;)). > > > > > > > > > I might try to merge it sometime this weekend if I get time, > > > > > > > > unless I > > > > > > > > have any other feedback about problems. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
