[/Apache hat] [CloudBees hat] If you *really* just want to get a Maven repo up and running, just sign up for a CloudBees account. That will give you a WebDAV file share that you can use as a Maven repository. Not as good as a MRM, but it's free and it's not a SCM (ab)used into being a Maven repository... oh and you get a Jenkins with 300 build minutes per month... more if you are doing a FOSS project. [/CloudBees hat] [Apache hat] Best is just to get the artifacts into Central, esp if you intend on others using your project.
-Stephen On 6 February 2013 23:00, Barrie Treloar <baerr...@gmail.com> wrote: > On 7 February 2013 07:11, Toolforger <toolfor...@durchholz.org> wrote: > > 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. > > You could always pony up some of your own money for a server or try > finding a free hosting service and install the MRM there. > You could even leave your home computer on all the time and let your > other resources connect to the MRM you install there. > > You've been given the best advice: Install a MRM. > Your constraints put you in a minority of use cases that no one else > wants to solve. > You have had quite a lot of free advice already on this issue. > I expect there is not much good will left to continue providing advice > for alternative that no one else is interested in. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
