Hi Tamás, Thanks for the info. That's most likely the best solution so far. I think I'll go with this one.
Regards, Dário -----Original Message----- From: Tamás Cservenák [mailto:[EMAIL PROTECTED] Sent: quarta-feira, 30 de maio de 2007 10:38 To: Maven Users List Subject: Re: [m2] best way to have an offline internal repository Hi, proximity holds it's cache in UNMODIFIED "M2 remote repository format". So, you can use proximity to "grab" remote reposes with needed artifacts and metadatas (as I described before) and M2 can use it's cache directly. Simply redirect M2 to use local FS with proximity cache content as remote repo. Proximity is needed for preparation only (made by you), a good settings.xml is needed for this to work on client side (others doing offline compile). Altough, i'm not sure is this the "right way to go" from M2 aspect, but it could solve the problem :) ~t~ On 5/30/07, Dário Luís Coneglian Oliveros <[EMAIL PROTECTED]> wrote: > > Hi Tamás, > > That would definitely be an option. But still you have to ask a final user > to fire up the proximity server in order to build a simple project, unless > proximixity does not need to be up and running. > Basically I'd expect to have something similiar with ant where you could > package an ant project and its dependencies and let a final user unpacks and > builds the project without doing anything else. > So I thought that creating a remote repo from a local one would help solve > this issue since the target repo could be used and accessed via file > protocol and be sitting on the client side. > I will most likely follow your suggestions unless there's any plugin or > tool that does the repo conversion. > > Dário > > -----Original Message----- > From: Tamás Cservenák [mailto:[EMAIL PROTECTED] > Sent: quarta-feira, 30 de maio de 2007 09:15 > To: Maven Users List > Subject: Re: [m2] best way to have an offline internal repository > > > Ha Dario, > > Proximity is able to work in "offline" mode, and offer only it's cache > content. So: > > 0. prepare "remote" repo content for proximity (collect artifacts you > need for your build) > 1. place proximity into "offline" mode and give it the prepared remote > repo content > 2. fire it up locally > 3. redirect all reposes from m2 to local proximity (m2 settings.xml) > > These steps could be handled by your local package... > > The step 0. is easily implemted: erase local repo and erase proximity > content and build agains proximity ONLINE. At the end of the build, > you will end up with remote repo with the needed content, ready to > package and redistribute. > > ~t~ > > On 5/29/07, Dário Luís Coneglian Oliveros <[EMAIL PROTECTED]> wrote: > > Hi there, > > > > I've been reading several threads about having an offline internal > repository and I wonder if there's any maven plugin or tool that can help on > this matter as of now. I've heard of a repository builder, but could not > find much information about it.FYI I use Proximity as my proxy/proactive > mirror. > > Basically I want to create a package that encompasses a maven project > and its repo so any user who uses it can build this project offline. Any > suggestions ? > > > > Any help is appreciated. > > > > Dário Oliveros > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > >
