Maven 3 requires that the artifact have originated from a valid repository, so putting it in a profile will mean that it will only build with the profile active. far better to just mandate a mirrorOf>*< to internal nexus/artifactory/archiva server
On 22 October 2012 22:37, Laird Nelson <ljnel...@gmail.com> wrote: > I know that it is a Bad Thing to add a repository to your pom.xml. > > Is it regarded by the Great Maven Hivemind :-) to be a Bad Thing if you put > a repository in your pom.xml as an (unactivated by default) profile? > > I'm sick and tired of having to tell users to put repository X or > repository Y in their .m2/settings.xml file; the whole point of the pom.xml > is: download the stuff, tell Maven to build it. :-) > > Best, > Laird > > -- > http://about.me/lairdnelson >
