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?
