[
https://issues.apache.org/jira/browse/HBASE-4763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13151677#comment-13151677
]
Gary Helmling commented on HBASE-4763:
--------------------------------------
You should be able to use my repo builds now, by adding the following
repository to the HBase pom.xml:
{code}
<repository>
<id>ghelmling.testing</id>
<name>Gary Helmling test repo</name>
<url>http://people.apache.org/~garyh/mvn/</url>
<snapshots>
<enabled>true</enabled>
</snapshots>
<releases>
<enabled>true</enabled>
</releases>
</repository>
{code}
Then change the junit and maven-surefire versions to be:
junit: 4.10\-HBASE\-1
surefire: 2.11\-TRUNK\-HBASE\-1
> Integrate surefire and junit for category management
> ----------------------------------------------------
>
> Key: HBASE-4763
> URL: https://issues.apache.org/jira/browse/HBASE-4763
> Project: HBase
> Issue Type: Improvement
> Components: test
> Affects Versions: 0.94.0
> Reporter: nkeywal
> Assignee: nkeywal
> Priority: Minor
> Attachments: surefire_hbase.v2.patch, surefire_hbase.v3.patch
>
>
> As of today, Surefire integrates category on the trunk of 2.11 version:
> http://jira.codehaus.org/browse/SUREFIRE-329 . It may requires private
> patches as well.
> It may impact JUnit: https://github.com/KentBeck/junit/issues/359
> This jira is about this integration. We will need a repo for this.
> For the naming of the versions to be created, I don't know if there is a
> convention. If not I would propose: 2.10-patched-HBASE
>
> Obviously, it's important to get our changes integrated in the main release:
> we're not forking surefire & junit!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
