[jira] (MRELEASE-156) Prompt for customizing commit comment during release preparation
[ https://jira.codehaus.org/browse/MRELEASE-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=301649#comment-301649 ] Przemyslaw Wojnowski commented on MRELEASE-156: --- Could you add an example to the FAQ? I've such configuration: org.apache.maven.plugins maven-release-plugin 2.3.2 ABCD-1234 ALT 10 And when I issue "mvn release:prepare -DdryRun=true" it doesn't show any new line: [INFO] Full run would be commit 4 files with message: 'ABCD-1234 ALT 10prepare release my-project-1.0.1' > Prompt for customizing commit comment during release preparation > > > Key: MRELEASE-156 > URL: https://jira.codehaus.org/browse/MRELEASE-156 > Project: Maven 2.x Release Plugin > Issue Type: Improvement > Components: prepare >Affects Versions: 2.0-beta-4 >Reporter: Dário Oliveros >Assignee: Robert Scholte > > Hi there, > I've been trying to use maven-release-plugin to prepare a release, but > whenever I do that, it fails since I have a SVN precommit hook that > integrates with an issue tracking system which in turn waits for a comment > containing an issue number. Since release plugin adds its own comment, such > as "[maven-release-plugin] prepare release ...", this integration fails. So > I was wondering if this could be prompted in the same way for the release and > next development iteration versions. > Thanks, > Dário -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-817) JUnit 4.7 test output is always buffered, lost if forked process exits abnormally
[ https://jira.codehaus.org/browse/SUREFIRE-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=303512#comment-303512 ] Przemyslaw Wojnowski commented on SUREFIRE-817: --- I'm also for enabling buffering layer only when running in parallel. > JUnit 4.7 test output is always buffered, lost if forked process exits > abnormally > - > > Key: SUREFIRE-817 > URL: https://jira.codehaus.org/browse/SUREFIRE-817 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support >Affects Versions: 2.11 >Reporter: Todd Lipcon > > The junit47 provider and above support multi-threaded test execution, and > thus interpose a buffering layer (ConcurrentReporterManager) in between the > test output and the actual stderr/stdout. This is ostensibly to allow the > multiple threads' stderr and stdout to be demuxed nicely when the suite > completes. But, if the JVM exits abnormally (eg due to a segfault or a > System.exit() call), no output is generated. This is problematic since it's > very hard to debug the test failure! > In my opinion, the buffering layer should only be interposed _when parallel > running is enabled_. For the non-parallel case, there's no need to buffer the > output. A simple test case is to write a JUnit test which prints a line of > output to stderr and then calls System.exit(1). The output doesn't show up > anywhere. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
