[
https://issues.apache.org/jira/browse/HBASE-4763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153494#comment-13153494
]
nkeywal commented on HBASE-4763:
--------------------------------
@stack: yes, but Gary has actually created a special repo for surefire and
built it from this.
Now we have:
Junit: 4.10-HBASE-1, source code on https://github.com/nkeywal/junit, branch
"hbase"
Surefire: 2.11-TRUNK-HBASE-2, source code on
https://github.com/ghelmling/maven-surefire branch "2.11-TRUNK-HBASE"
Both are in Gary's repo on http://people.apache.org/~garyh/mvn.
In HBASE-4781, I am currently checking that it works well with Jenkins, if yes:
- the patch on pom.xml in HBASE-4781 will be commited.
- we will be able to close the two Jiras.
> 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_793_trunk.v3.patch, 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
