You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2014/12/01 23:32:13 UTC

[jira] [Comment Edited] (HBASE-12383) Move 0.98 build to surefire 2.18

    [ https://issues.apache.org/jira/browse/HBASE-12383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14230576#comment-14230576 ] 

Andrew Purtell edited comment on HBASE-12383 at 12/1/14 10:31 PM:
------------------------------------------------------------------

Just a note. Upgrading to 2.18, we get this:
{noformat}
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test
(secondPartTestsExecution) on project hbase-annotations: Execution
secondPartTestsExecution of goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test
failed: Fork mode perThread is not a legal value -> [Help 1]
{noformat}
Looking at what the valid fork modes are for this release...


was (Author: apurtell):
Just a note. Upgrading to 2.18, we get this:
{noformat}
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test (secondPartTestsExecution) on project hbase-annotations: Execution secondPartTestsExecution of goal org.apache.maven.plugins:maven-surefire-plugin:2.18:test failed: Fork mode perThread is not a legal value -> [Help 1]
{noformat}
Looking at what the valid fork modes are for this release...

> Move 0.98 build to surefire 2.18
> --------------------------------
>
>                 Key: HBASE-12383
>                 URL: https://issues.apache.org/jira/browse/HBASE-12383
>             Project: HBase
>          Issue Type: Task
>          Components: build
>            Reporter: stack
>            Assignee: Andrew Purtell
>            Priority: Minor
>             Fix For: 0.98.9
>
>
> Move 0.98 build off the garyh hosted surefire and up on to 2.18 surefire (may have to be a 2.18-SNAPSHOT like master branch -- see HBASE-12379).
> It does not look like 0.98 is suffering the master and branch-1 issues that the 2.18-SNAPSHOT seems to fix but can't hurt upgrading.
> Filing this issue at [~apurtell] suggestion.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)