You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2016/12/31 07:10:58 UTC

[jira] [Commented] (SUREFIRE-1310) ForkClient should handle only one channel-id

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

Hudson commented on SUREFIRE-1310:
----------------------------------

UNSTABLE: Integrated in Jenkins build maven-surefire #1662 (See [https://builds.apache.org/job/maven-surefire/1662/])
[SUREFIRE-1310] ForkClient should handle only one channel-id (tibor17: [http://git-wip-us.apache.org/repos/asf/?p=maven-surefire.git&a=commit&h=27fbe2c190a204e19dc42c86e9769bf384e7ec91])
* (edit) maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/output/ForkClient.java


> ForkClient should handle only one channel-id
> --------------------------------------------
>
>                 Key: SUREFIRE-1310
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1310
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: Maven Failsafe Plugin, Maven Surefire Plugin, process forking
>            Reporter: Tibor Digana
>            Assignee: Tibor Digana
>             Fix For: 2.19.2
>
>
> The class ForkClient was able to map channelId to RunListener.
> The old Surefire project designed ForkClient with multiple channels.
> The use of this class requires us to handle only one channelId.



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