To avoid pulling that to the user builds, we could just move it from the parent pom to the integrationtest pom - no user would add that dependency anyway ;-).

On the question whether it is a good idea or not, [in this article](http://blog.sonatype.com/people/2009/02/why-putting-repositories-in-your-poms-is-a-bad-idea/) the Summary says:
 > If you are exposing your source and want to make it easy for others to build, then consider adding a repository entry to your POM, but don’t pick a URL lightly, think long-term, and use a URL that will always be under your control.

Ok, we not quite meet that.
I guess the best way would be to avoid the dependency to something outside central completely. Is there any way around using weld?

Maven Central would accept the pom, they do not reject it - it's just discouraged. I don't see too much harm for an alpha-2 if we moved it to integrationtests/pom.xml and keep an eye on alternatives to weld.

WDYT?