In some sense, Maven appears mature enough to set your project up all by itself. Just install it, set up a path so that console commands find it, then invoke it against a pom file and it does all the rest.
I don't think it was always like that; I still recall it having great difficulty finding appropriate versions of some jar file, but in the most recent builds I have done on various projects downloaded here and there, it seems to work flawlessly, at least for me. The secret sauce, perhaps, is in careful layout and testing of the pom files, making sure there are online repositories that include everything needed. Jack On Thu, Jul 29, 2010 at 7:46 AM, dougx <[email protected]> wrote: > Just my $0.02: Call me old fashioned but when I download a code > repository I expect it to compile, not try to download additional > artifacts and then compile (yes, sad to say not the entire world is > connected to the internet 24/7). > > If you decide to go down the maven path, please make it easy for us to > setup our own local maven repositories with all the artifacts the > project depends on. > > ~ > Doug. > > On Jul 28, 11:04 pm, Steve Baker <[email protected]> wrote: >> On Jul 29, 12:03 pm, Alex North <[email protected]> wrote: >> >> > Thus I'd like to announce a new repository in the wave protocol project: >> >> That is great news. It would be great if this was also used as an >> opportunity to get binary jar files out of the source control. Also >> since you're prepared to work through this disruptive process it would >> be a shame if you got to the end of it and still didn't fully cater >> for an ecosystem as large as >> Maven:http://jarvana.com/jarvana/info/repository_statistics >> >> To this end I've put together a pom.xml to provide maven builds for >> wave-protocol-libraries. I'm more than happy to do what it takes to >> make this a supported build system for wave-protocol-libraries. >> >> The only things missing to get a full build appears to be these packages: >> org.waveprotocol.wave.client.editor.constants >> org.waveprotocol.wave.client.editor.content.paragraph.constants >> >> Could you please consider not including the following packages in >> wave-protocol-libraries? >> org.waveprotocol.wave.crypto >> org.waveprotocol.wave.federation.Proto >> org.waveprotocol.wave.federation >> org.waveprotocol.wave.federation.xmpp >> >> The reasoning would be as follows: >> - these are self-contained packages concerned with server<->server >> transport and federation >> - org.waveprotocol.wave.federation.xmpp adds many jar dependencies, >> including a custom-patched jar that exists in no public repository and >> is no longer maintained by upstream (whack/xmpp) >> - the bulk of wave-protocol-libraries has minimal dependencies and >> compiles to GWT >> >> These packages could stay in fedone-server for now, or go into their >> own wave-protocol-federation project. (Likewise, a >> wave-protocol-websockets project could be created for client<->server >> transport) >> >> The pom.xml I've created assumes that the federation packages are left >> out. This leaves a project with 5 dependencies (plus 5 test >> dependencies). >> >> If you want to try the pom, put it in the root project dir, install a >> recent maven and try the following >> >> # write a .project and .classpath for importing into Eclipse IDE >> mvn eclipse:eclipse -DdownloadSources=true >> >> # run unit tests (currently fails with build errors) >> mvn clean test >> >> I would be interested to hear if anyone has issues getting the >> dependency gwt-user-2.1.0.M2.jar. We have our own private repo for >> unreleased jars, so I haven't tested the svn repo at the bottom of the >> pom.xml. >> >> cheers >> >> pom.xml >> 5KViewDownload > > -- > You received this message because you are subscribed to the Google Groups > "Wave Protocol" 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/wave-protocol?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Wave Protocol" 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/wave-protocol?hl=en.
