On 7 February 2013 20:20, Joachim Durchholz <[email protected]> wrote: > Am 07.02.2013 00:00, schrieb Barrie Treloar: > >> 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. > > > Managing your own server is eating more time than most people can imagine. > Setting up a server just to inject a jar from a stable external source is a > ridiculously overpowered solution anyway. > > So, no, this isn't an option, and I'm not going to argue that again (and > again and again - why do you guys insist on repeating advice that has > already been rejected, with arguments?)
Because that is what we all do and it works for us. If it is a stable source and open source, put it on Central. Otherwise you have do something yourself and we all use a MRM. You have describe that your collaborators are distributed need to share those artifacts. You have been given a number of alternatives to a MRM, but they all require the developers to do some work each time things change. You are trading time for money. I still think running a MRM yourself and just "wasting your time" is your best option. You will not be wasting much time; once to install, once per artifact to load it into your MRM, and maybe occasionally to maintain it but it really is fire and forget. All the alternative options, to me, look like a larger waste of time in both aggregate and per developer, including maintaining scripts and documenting your development process. You are welcome to disagree. Normally at this point in a project the Technical Lead would attempt multiple solutions and compare them objectively. If you do that your results would be welcome on this list. At this stage the conversation is degenerating into a flamewar or hear say opinions and there is little left of value in it. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
