Update, GPE seems to be working, so I'm going to run more tests to verify.
On Friday, October 17, 2014 3:35:33 PM UTC-7, Brandon Donnelson wrote: > > Just a note, I'm digging into the GPE m2e project configurator. It looks > like I've got to add a way to ready the dependency management (BOM). I'll > have a test case setup shortly so I can start getting it to read the > pom.xml configuration. Do you think anything is going to change upstream > yet? From the way it looks so far its a maven bug and not an issue in the > gwt configuration. > > On Friday, October 17, 2014 3:26:36 PM UTC-7, Thomas Broyer wrote: >> >> >> >> On Friday, October 17, 2014 10:58:49 AM UTC+2, Thomas Broyer wrote: >>> >>> >>> This is really really strange, as I'd swear that everything was working >>> for me with Maven 3.0.5 (before sending the patch to update the samples in >>> GWT, I ran "mvn clean verify" and then "mvn gwt:run"). I never "mvn >>> install" (or exceptionally once or twice a year) anything on my machine so >>> the snapshots were all coming from the remote repositories. >>> >> >> OK, problem reproduced/acknowledged. I know what in the plugin causes the >> error, but it's code a copy/pasted from another module without really >> understanding it (and using an API with absolutely zero documentation) so >> it might not be that easy to fix. >> I think we'll really require everyone to explicitly declare >> gwt-codeserver as a project dependency. >> Let's see how it goes in 2.7 beta1, without snapshots in the equation. >> > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
