On Sep 11, 2012, at 2:54 PM, Ron Wheeler <[email protected]> wrote:
> Using Maven without your own Repo is a horrible waste of time. > Get one of the repos (We use Nexus) installed and configured and you life > will get a lot simpler. Really? It's that bad? Why doesn't it say this in the Maven documentation then? A lack of understanding of repositories will just kick the can upstream to where repositories and groups now need to be configured. If the OP still doesn't the nuances of repositories, now he has to learn them in the context of how to configure Nexus. Knowledge that might help him solve this problem without a repository in the first place. I'm not advocating that one runs a build for a team without a copy of Nexus, I agree it is worth the investment to learn, but Maven is not a "waste of time" without it. Please don't take this the wrong way, Ron, but these kinds of statements are sensationalistic and false. We all got by for years without repositories and Maven hasn't substantially changed anything such that they are a requirement now. To the original poster: You need to study more about repositories and understand which artifacts need to come from where. If a repository has the wrong version of an artifact, do not include it in your list of repositories or it will be downloaded. Further, there is a difference between <repository> and <pluginRepository>, and you should not need the latter unless there is a Maven plugin that is not being found. When you have artifact dependencies that are *not* a part of your build *and not* a part of any repository, *then* you cannot get by without a repository of some sort. It *is* possible to host a repository on a plain HTTP server and "deploy" to file: URLs, but it is a bit masochistic to do so. In that case, it is easiest to bite the bullet and just deploy Nexus to start with. I hope this helps without being incendiary. I care about you guys more than that. :-) Brian --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
