If these dependencies are OSS just upload them to central.. Even under your own groupId if you feel uncomfortable pushing under the originating projects gId
On Wednesday, 6 February 2013, Toolforger wrote: > Am 06.02.2013 21:19, schrieb Baptiste MATHUS: > >> 2013/2/6 Toolforger <[email protected]> >> >> >>> Am 06.02.2013 19:03, schrieb Baptiste Mathus: >>> >>> Stop resisting ;). There're not. At least there are no *simpler* >>> >>>> alternative. That's the point. :) >>>> >>>> >>> I don't think you really followed all the messages, else you'd have >>> noticed that do have a simpler alternative running already. >>> >> >> >> Well, I might have missed some, granted, but I actually followed it quite >> well. >> And I'll also keep saying it: using a MRM is the simplest way to go. >> >> When I read things like someone have a snapshot locally and one other >> doesn't, we exactly are on the subject: use a MRM and just don't care >> about >> the local cache. >> Anything else is a hack that will eventually backfire. >> > > If that's what you think: That's okay. > > Just to reiterate the point at which the discussion ended: > I said I can't have a common MRM-managed repository, there's simply no > server and no budget for a server. What I didn't mention yet is that once I > can sell the software, or the services, and (hopefully) open-source the > whole thing, this will change, but that point is months away, and I need to > deal with the situation as it is now, not as it will be. > > Just repeating arguments that others have already given multiple times, ad > nauseam, won't help. > Find new arguments and I'll listen. > > Just to show that I'm not 100% unreasonable: We do have servers at work, > and I will give Nexus a try there. > However, I still need to solve the situation for my free time project, and > reiterating old arguments is not the way to help. > > Thanks for reading. > Jo > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
