That's precisely the problem. You force devs to use jbehave's settings.xml so thus skipping their existing settings.xml in that proper proxy settings reside mostly.
As quoted from the maven guide settings.xml should not be boundled with any source tree. It is meant for workstation specific settings. All the declarations in jbehave-core/settings.xml belong to jbehave-core/pom.xml imho. 2013.08.12. 16:27, "Cristiano Gavião" <cvgav...@gmail.com> ezt írta: > not all dependencies of JBehave are in maven central repository. maven > provides us two ways to work with multiple repositories. > > we decided not to put the needed repositories inside the pom so it is the > reason we use the settings.xml. and add it to the git just to provide the > developers an easy way to set the build. > > so to build JBehave you just need do: > > mvn install -s settings.xml > > > > 2013/8/12 Gabor Czigola <gabor.czig...@gmail.com> > >> Started working on jbehave-core codebase and wonder why there is a >> settings.xml boundled in the source tree? >> >> The purpose of settings.xml is to specify workspace specific mvn >> settings, according to maven.jbehave.org/settings.html it "should not be >> boundled to any specific project" for a good reason: people specify for >> example local proxy and repo settings. By forcing this particular >> settings.xml you doom everyone requiring specific settings. >> >> I don't see any reason why the definitions in settings.xml are not in >> pom.xml actually? They do belong there, don't they? >> > > > > -- > "Tudo vale a pena se a alma não é pequena..." >
