[ https://issues.apache.org/jira/browse/SUREFIRE-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653289#comment-14653289 ]
Bruno Bieth commented on SUREFIRE-703: -------------------------------------- I still can observe this with the following configuration: {code:xml} <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <version>2.18.1</version> <dependencies> <dependency> <groupId>org.apache.maven.surefire</groupId> <artifactId>surefire-junit47</artifactId> <version>2.18.1</version> </dependency> </dependencies> <configuration> <parallel>classes</parallel> <threadCount>1</threadCount> <forkCount>1C</forkCount> <redirectTestOutputToFile>true</redirectTestOutputToFile> <reuseForks>true</reuseForks> <argLine>-Xmx512m</argLine> </configuration> </plugin> {code} But if I remove `parallel` and `threadCount` then it works: {code:xml} <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <version>2.18.1</version> <dependencies> <dependency> <groupId>org.apache.maven.surefire</groupId> <artifactId>surefire-junit47</artifactId> <version>2.18.1</version> </dependency> </dependencies> <configuration> <forkCount>1C</forkCount> <redirectTestOutputToFile>true</redirectTestOutputToFile> <reuseForks>true</reuseForks> <argLine>-Xmx512m</argLine> </configuration> </plugin> {code} > surefire-junit47doesn't work with redirectTestOutputToFile option > ----------------------------------------------------------------- > > Key: SUREFIRE-703 > URL: https://issues.apache.org/jira/browse/SUREFIRE-703 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support > Affects Versions: 2.7.2 > Reporter: Will May > Assignee: Kristian Rosenvold > Fix For: 2.9 > > Attachments: surefire-junit47-it.patch > > > If you have the redirectTestOutputToFile option set and use the > surefire-junit47 provider (through using the parallel test option or through > forcing it), then the output file will just contain a single newline and so > the console logging will be completely lost. > Attached is an integration test showing this issue which was based off of the > fork-consoleOutput integration test. -- This message was sent by Atlassian JIRA (v6.3.4#6332)