Apologies, for one thing... my repository mirroring was blocking the plugin repository and I didn't have gwt-maven configured as a remote proxy repo in my archiva instance.
I can't find where the jdom:dom-1.1 dependency can be sourced. If you know where this is Charlie then I can add it to the pom. A quick search shows me that people have been asking for the 1.1 dependency in central since April so who knows if this happen anytime soon. As I said, the re-packaging of the zip/tar to a jar eta that jdom needs is something I would rather not complicate the n00b user with. Sorry I don't have more time to devote to this at the moment. Thanks for your responses! On Sep 23, 8:12 pm, Charlie Collins <[EMAIL PROTECTED]> wrote: > I think you might be using old versions of everything. > > If you try the latest samples, the latest version of the plugin, the > archetype, and so on, they work out of the box even to get JDOM (1.1 > is in a few repos, not central, but others, also it's the support JAR > that needs JDOM 1.1, and it has a repo defined for it > -http://gwt-maven.googlecode.com/svn/trunk/maven-googlewebtoolkit-supp... > > I have wiped out my repo multiple times on various platforms to test > things, and it all works for me? > > Please let me know exactly what you think fails out of the box, as far > as I know nothing does. > > As for the open issue, that is for getting GWT-Maven itself into the > central repo, and it is 44KB, it is NOT 20MB, not even close. All the > dependencies, such as GWT itself, are the big part, and they are > already in central. I am waiting to address a few final issues, and > then take off the -beta label, and I will get it in central (I know > how, and I can host a sync server somewhere too). > > See the latest docs and use the latest versions of everything, and > then if there are actual issues please log them and we can address > them. > > On Sep 23, 12:31 am, ahhughes <[EMAIL PROTECTED]> wrote: > > > I tried to show a colleague gwt-maven's sample projects but they fail > > to build out of the box for a number of reasons. Although there are > > several workarounds, the best solution is that we upload the gwt-maven > > plugins and missing dependencies to central. > > > I had considered several options, re-configuring the pom's with a > > pluginRepository or instructions to install the missing jdom:jdom-1.1 > > dependency... but the bottom line is that this is not required. > > Central is there for this purpose and we should use it. > > > They have a guide on how to upload to central > > here:http://maven.apache.org/guides/mini/guide-central-repository-upload.html > > > I'll wait for some feedback before I do anything. My only concern is > > that the 20 odd Mb or whatever the gwt plugin size is will be slow and > > unreliable from the overworked and under resourced central. > > > --Andrew --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
