Both URL tags in the example settings of the maven repository points to ER4 build: <url>file:///path/to/repo/jboss-dv-6.2.0.ER4-redhat-1-maven-repository/maven-repository</url>
I can confirm that sample path does not contain any build-specific mark. However, it still does not point to valid maven repo: Sample path: file:///path/to/repo/jboss-dv-6.2.0.redhat-2-maven-repository/maven-repository Expected path: file:///path/to/repo/jboss-dv-6.2.0-maven-repository/maven-repository I think that this is not big deal. If you agree, I can set this BZ to verified. Or you can simply change the file manually.
Assuming CR2 becomes GA, fixing the file manually within the existing zip is probably the best option, to guarantee the rest stays the same. However, it's still a bit awkward to change one of the files post-announcement. Do you want to tell me when you're done testing the maven repo, and then I can update the example settings, and you can check everything else in the zip is identical?
I think that the example is clear, no matter if there is a little error or not. I probably will not be able to check the fix, so do not change the file. I am setting this BZ to VERIFIED.