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

Alexander Kriegisch commented on SUREFIRE-1788:
-----------------------------------------------

I am not sure if you are aware of the following facts:
  * The artifacts in the RC1 repository change, I sometimes seen them getting 
updated during builds. So it is not a stable version, as the version number 
implies. This is dangerous.
  * The current version makes my Failsafe tests freeze, i.e. the 
`integration-test` phase starts and then the Maven JVM just freezes, I have to 
kill it. The same effect happened with snapshots before. I.e. for now I have to 
revert to M4 because Failsafe wrecks my build.

> Unhandled native logs in SurefireForkChannel
> --------------------------------------------
>
>                 Key: SUREFIRE-1788
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1788
>             Project: Maven Surefire
>          Issue Type: Task
>          Components: Maven Failsafe Plugin, Maven Surefire Plugin, process 
> forking
>            Reporter: Tibor Digana
>            Assignee: Tibor Digana
>            Priority: Major
>             Fix For: 3.0.0-M5
>
>
> This is related only to the internal change of the version 3.0.0-M5 itself.
> The 
> [stdOut|https://github.com/apache/maven-surefire/blob/master/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/extensions/SurefireForkChannel.java#L153]
>  should be printed to INFO on the console.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to