I've Changed our pom.xml to use the new repository

[clebert.suconic]

The title tells everything...

I just changed our pom.xml to use the new repository...

It will be using the public repository, if you want to use our exclusive developer's repository (which is supposedly faster), you should refer to this:

http://community.jboss.org/wiki/MavenGettingStarted-Developers

By changing your /m2/settings.xml you will be ignoring the settings at the pom.xml

[clebert.suconic]

BTW: thanks for Paul Gier! :-)

[timfox]

IMO it's unnaceptable that  developers have to jump through hoops and create a settings.xml just to build our project.

Yesterday I svn up'd and for the next couple of hours I was unable to build while I worked out what to do next.

All information about repositories should already be encoded in our build scripts so the developer simply has to execute ./build.sh

[jmesnil]

clebert fixed this: you can again build hornetq from a simple svn checkout without having to deal with maven settings.

now, if other projects were doing that too, it'd make my life a bit easier...

[clebert.suconic]

Tim Fox wrote:

IMO it's unnaceptable that  developers have to jump through hoops and create a settings.xml just to build our project.

Yesterday I svn up'd and for the next couple of hours I was unable to build while I worked out what to do next.

All information about repositories should already be encoded in our build scripts so the developer simply has to execute ./build.sh

I agree with you hence I have fixed it...

However.. that's not what mavenists think. They think that every one would want to use a different repository so the location for the repository on the main settings under the user home.

As they say.. you have to choose the battles you are going to make.. and I don't want to spend energy on changing what maven guys think ;-)

[timfox]

Mavenists can do what they want in other projects.

But in this project, we're not going to destroy usability for the sake of 0.0000005% of users who might want to point the build at a different repo.