--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Is Google's 1.3.2.google version working for anyone? I get
[ERROR] Failed to execute goal
org.codehaus.mojo:gwt-maven-plugin:1.3.2.google:run (default-cli) on
project front-end: Execution default-cli of goal
org.codehaus.mojo:gwt-maven-plugin:1.3.2.google:run failed: Unable to
load the mojo 'run' in the plugin
'org.codehaus.mojo:gwt-maven-plugin:1.3.2.google'. A required class is
missing: org/codehaus/plexus/util/xml/XmlStreamReader
when I use it (1.3.1.google was working fine). I'm trying to upgrade to GWT-2.1.
Looking at 1.3.1.google's POM and the 1.3.2.google version I can see
that the 1.3.2.google POM is almost empty, while the 1.3.1.google one
lists lots of dependencies and such.
Adding Plexus Utils doesn't help either (I just get a different error message).
What happens if you delete org/codehaus/plexus from your local maven
repo and rebuild?
> --
> You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
> To post to this group, send email to google-we...@googlegroups.com.
> To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
>
>
--
David Chandler
Developer Programs Engineer, Google Web Toolkit
http://googlewebtoolkit.blogspot.com/
Maven downloads 8(!) different versions of Plexus Utils, including 1.1
apparently for gwt-maven-plugin. Then I get the error I listed before.
It doesn't matter whether I use GWT 2.1-SNAPSHOT or GWT 2.1.
HTH,
On 28 October 2010 15:09, David Chandler <drfib...@google.com> wrote:
> Thanks, Hilco. If you haven't already, have a look at the sample POM
> here for reference:
> http://code.google.com/p/google-web-toolkit/source/browse/trunk/samples/expenses/pom.xml.
This is unusable. It references datanucleus.org which simply hangs. So
each JAR/POM takes several minutes before datanucleus.org times out
and Maven tries another repo. At this rate it will take days.
I did notice that the expenses POM downloaded the same gwt-maven-plugin I did.
> If that doesn't help, your best bet is to try it with a fresh local
> maven repo. Users on another thread previously reported that wiping
> their local repo resolved plexus issues.
Well, I kinda doubt it but I'll give it a try. :-)
Thanks,
Hilco
Nope, that didn't change anything.
I take it, it's working for you? So as far as you're concerned, that
small POM for 1.3.2.google is correct? No dependencies, nothing?
There is one issue with the Expenses POM, but I don't think it's the
one you're seeing on your project:
http://code.google.com/p/google-web-toolkit/issues/detail?id=5497
Try workaround #1 in the issue, after which you should be able to
remove the datanucleus.org repo from the Expenses POM in order to
speed things up.
And yes, this is working for me and many others once
jdo2-api-2.3-ec.jar is installed in local repo. Are you using App
Engine and JDO in your project? If not, you can remove all the repos,
maven-gae-plugin, and appengine deps.
HTH,
On Thu, Oct 28, 2010 at 9:43 PM, Hilco Wijbenga
On 29 October 2010 08:38, David Chandler <drfib...@google.com> wrote:
> And yes, this is working for me and many others once
> jdo2-api-2.3-ec.jar is installed in local repo. Are you using App
> Engine and JDO in your project? If not, you can remove all the repos,
> maven-gae-plugin, and appengine deps.
Okay, datanucleus.org is up again so I could try out the Expenses app.
After cleaning my local repo again, it does indeed work.
So I had to go into my Nexus setup and remove all existing repos and
re-add them as needed to get the build to work with my Nexus. After
that (and the addition of a few more repos in Nexus) my own build
worked too. Now we'll see what happens to the other developers...
I hope Google will soon have a single repository for all this stuff or
simply publishes in Central. All these changing repositories is just
painful and apparently fragile. :-)
Anyway, thanks for your help!
Cheers,
Hilco
--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.