Not really fussed as long as you can build offline (or effectively offline behind a corp firewall or limited connectivity on a plane). I've had problems with mvn dependency:go-offline/ mvn -o install before (example: http://code.google.com/p/thoughtsite/); basically if you want to rely on the local cache you have to actually build the project and then zip your .m2/repository up and take it along with you, and hope it all works when you unpack it all...
If the project only depended on a single google code maven repo you could pull that repository as well as the source tree and be absolutely certain you had all the required plugins and libraries. *shrug* ~ D. On Jul 30, 4:42 am, Steve Baker <[email protected]> wrote: > On 30 July 2010 02:46, 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). > > Maven artifacts are cached in a local repository, so you only need the > internet the first time you run maven, and whenever dependencies > change. This is essentially no different to fetching the dependencies > from a source control server. > > cheers -- 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.
