[
https://issues.apache.org/jira/browse/SUREFIRE-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15029258#comment-15029258
]
Tibor Digana commented on SUREFIRE-1198:
----------------------------------------
[~azgard]
Started the build of your project on WinXP and there really seems to be a
problem.
The test started and timed out after 200 seconds. No idea why.
But another thing is interesteing to me. I printed std/out but I do not see
anything in the console.
Most probably Stringboot overrides std/out when the test starts and the
Surefire does not receive command TESTSET_FINISHED from std/in and therefore
expects a new test class but there's only one. We are using std/in and out as
communication channel between Maven process and Surefire forked JVM.
I don't see these logs:
{code}
@Before
public void check() {
System.out.println("################# B:TIBOR ##############");
assertNotNull(ctrl);
}
@After
public void after() {
System.out.println("################# A:TIBOR ##############");
}
{code}
> Failsafe does not allow to use target/classes anymore
> -----------------------------------------------------
>
> Key: SUREFIRE-1198
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1198
> Project: Maven Surefire
> Issue Type: Bug
> Reporter: Stephane Nicoll
>
> See [this Spring Boot
> issue|https://github.com/spring-projects/spring-boot/issues/4510#issuecomment-159448634]
> It seems that SUREFIRE-855 does not allow {{target/classes}} to be used
> anymore. Is there a reason why this behaviour was completely removed in
> favour of only the jar file?
> It would be nice if we had an option to chose between the two (defaulting to
> the jar)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
