OK, I'm starting to get it. And you cannot a copy of your local repository as a "remote repository" by defining it with <repositories><repository> since the metadata is different?
I could still take the copy of local repository and just copy it to the place where local repository should be in the offline computer, and it should work, no? It just fails because dependency:go.offline has a bug and does not fully do what you described. It misses maven-surefire-plugin. I guess most won't notice this since they already have the surefire plugin in their local repository before dependecy:go-offline. stephenconnolly wrote: > > To make sure that everything you need is in your local repository before > you > unplug your network cable and step on a plane > > On 19 March 2010 16:01, napple fabble <[email protected]> wrote: > >> >> >> Wendy Smoak wrote: >> > >> > On Fri, Mar 19, 2010 at 10:54 AM, jimmi4664 <[email protected]> >> > wrote: >> >> My Maven project needs to be built in an offline computer. I am trying >> to >> >> create a snapshot of my repository using an online machine and mvn >> >> dependency:go-offline, and then move this snapshot repository to the >> >> offline >> >> machine and build there. >> > >> > A local repository does not have the same metadata as a remote >> > repository. Plugins especially are very picky about metadata. >> > >> > Check the list archives, there was some discussion in times past about >> > a script to modify the metadata of a local repo so it would work as a >> > remote one. >> > >> > The easier solution by far will be to run a repository manager locally >> > and let it proxy everything you need, then move *that* repository >> > (which will have the correct format) off to the other machine. >> > >> > -- >> > Wendy >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [email protected] >> > For additional commands, e-mail: [email protected] >> > >> > >> > >> >> >> I am sure you know your stuff, but this does not make sense to me. Why >> does >> dependency:go-offline exist if you cannot use it for this purpose? Isn't >> it >> there to make offline builds possible? What is it used for if it does not >> work in this scenario? >> >> Is >> >> http://stubbisms.wordpress.com/2008/08/28/maven-is-to-ant-as-a-nail-gun-is-to-hammer-and-nails-you-need-to-move-on/ >> wrong ("Taking Maven completely Off-Line")? >> >> >> -- >> View this message in context: >> http://n2.nabble.com/Creating-repository-for-offline-building-with-dependency-go-offline-fails-tp4763428p4763867.html >> Sent from the maven users mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > -- View this message in context: http://n2.nabble.com/Creating-repository-for-offline-building-with-dependency-go-offline-fails-tp4763428p4776734.html Sent from the maven users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
