[jira] (SUREFIRE-1077) NPE problem will happen if you set testng status to fail at afterInvocation method

[ https://jira.codehaus.org/browse/SUREFIRE-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=346084#comment-346084 ] tim wu commented on SUREFIRE-1077: -- I want to know if anyone could reply this question. > NPE

[jira] (MNG-5630) improve display of forked executions

[ https://jira.codehaus.org/browse/MNG-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=346083#comment-346083 ] Michael Osipov commented on MNG-5630: - I do not like the line length it introduced now. Now we ha

[jira] (MSHARED-266) run aggregator reports only when current projet is pom packaging and has modules

[ https://jira.codehaus.org/browse/MSHARED-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=346082#comment-346082 ] Anthony Whitford commented on MSHARED-266: -- Please accept my sincere appreciation for inv

[jira] (MCHANGES-335) announcement-mail broken when NOT using the announcementFile parameter

[ https://jira.codehaus.org/browse/MCHANGES-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=345919#comment-345919 ] Guillaume Husta edited comment on MCHANGES-335 at 5/7/14 10:11 AM:

[jira] (MSHARED-334) add goal name to MavenReportExecution

Herve Boutemy created MSHARED-334: - Summary: add goal name to MavenReportExecution Key: MSHARED-334 URL: https://jira.codehaus.org/browse/MSHARED-334 Project: Maven Shared Components Issue Ty

[jira] (SUREFIRE-905) Surefore report plugin only executed tests once.Junit Categorization is not possibel

[ https://jira.codehaus.org/browse/SUREFIRE-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=346077#comment-346077 ] Herve Boutemy commented on SUREFIRE-905: if you use maven-reporting-exec 1.2-SNAPSHOT wit

[jira] (SUREFIRE-905) Surefire report plugin only executed tests once. Junit Categorization is not possible

[ https://jira.codehaus.org/browse/SUREFIRE-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=346078#comment-346078 ] Herve Boutemy commented on SUREFIRE-905: is it a duplicate of MSHARED-271? did you try wi

[jira] (SUREFIRE-905) Surefire report plugin only executed tests once. Junit Categorization is not possible

[ https://jira.codehaus.org/browse/SUREFIRE-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated SUREFIRE-905: --- Summary: Surefire report plugin only executed tests once. Junit Categorization is not possible

[jira] (MSHADE-168) ManifestResourceTransformer manifestEntries map declares wrong generic type

[ https://jira.codehaus.org/browse/MSHADE-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=345924#comment-345924 ] Stuart McCulloch commented on MSHADE-168: - Opened https://github.com/apache/maven-plugins/p

[jira] (MNG-5613) NPE error when building a reactor with duplicated artifacts

[ https://jira.codehaus.org/browse/MNG-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=346075#comment-346075 ] Sébastian Le Merdy commented on MNG-5613: - I've followed [this guide|http://maven.apache.org

[jira] (SCM-749) remove "[INFO] Working directory:" from svnexe output on Linux

Herve Boutemy created SCM-749: - Summary: remove "[INFO] Working directory:" from svnexe output on Linux Key: SCM-749 URL: https://jira.codehaus.org/browse/SCM-749 Project: Maven SCM Issue Type:

[jira] (MNG-5613) NPE error when building a reactor with duplicated artifacts

[ https://jira.codehaus.org/browse/MNG-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=346074#comment-346074 ] Jason van Zyl commented on MNG-5613: Thanks for the test, if you haven't run the integration test

[jira] (SCM-497) Please improve documentation on http://maven.apache.org/scm/guide/usage.html

[ https://jira.codehaus.org/browse/SCM-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=346067#comment-346067 ] Herve Boutemy commented on SCM-497: --- instead of using directly the embedder, you should extend [Ple

[jira] (MNG-5630) improve display of forked executions

Herve Boutemy created MNG-5630: -- Summary: improve display of forked executions Key: MNG-5630 URL: https://jira.codehaus.org/browse/MNG-5630 Project: Maven 2 & 3 Issue Type: Improvement

[jira] (SCM-69) Improve error message when commit over https fails

[ https://jira.codehaus.org/browse/SCM-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed SCM-69. Resolution: Cannot Reproduce Fix Version/s: (was: future) > Improve error message when commit over https

[jira] (SCM-549) mvn deploy to an svn repository makes a separate checkin for every file deployed

[ https://jira.codehaus.org/browse/SCM-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated SCM-549: -- Description: I have the below code in my build/extensions section. When I do "mvn deploy -N" on a single pom.x

[jira] (SCM-274) Support tagging with non-standard svn repository layout

[ https://jira.codehaus.org/browse/SCM-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated SCM-274: -- Description: There is a non-standard, but common svn repository layout & tagging/branching convention: The rep

[jira] (SCM-392) SCM SVN plugin does not cope with a flat structure

[ https://jira.codehaus.org/browse/SCM-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated SCM-392: -- Description: All of this is when using a flat (eclipse based) directory structure. When performing a release,

[jira] (SCM-549) mvn deploy to an svn repository makes a separate checkin for every file deployed

[ https://jira.codehaus.org/browse/SCM-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed SCM-549. - Resolution: Fixed Assignee: Herve Boutemy [maven-scm-publish-plugin|http://maven.apache.org/plugins/maven-s

[jira] (SCM-497) Please improve documentation on http://maven.apache.org/scm/guide/usage.html

[ https://jira.codehaus.org/browse/SCM-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated SCM-497: -- Environment: dependencies: org.apache.maven:maven-embedder:2.0.4 and org.apache.maven.scm:maven-scm-api:1.2

[jira] (SCM-482) SvnInfoConsumer not I18N aware

[ https://jira.codehaus.org/browse/SCM-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated SCM-482: -- Fix Version/s: (was: 1.x) > SvnInfoConsumer not I18N aware > -- > >

[jira] (SCM-497) Please improve documentation on http://maven.apache.org/scm/guide/usage.html

[ https://jira.codehaus.org/browse/SCM-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated SCM-497: -- Description: Trying to use Maven-SCM in my application I have selected the "With Plexus IOC" method as provid

[jira] (SCM-741) scm:validate for svn should offer a way to check the current directory actually matches what's declared in the pom

[ https://jira.codehaus.org/browse/SCM-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed SCM-741. - Resolution: Fixed Assignee: Herve Boutemy IT fixed in: - [36cdd169|http://git-wip-us.apache.org/repos/asf/m

[jira] (SCM-740) Maven Release Plugin releases SNAPSHOT instead of STABLE version

[ https://jira.codehaus.org/browse/SCM-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=346066#comment-346066 ] Herve Boutemy commented on SCM-740: --- for the record, here is the commit [b4aee509|http://git-wip-us

[jira] (MNG-5613) NPE error when building a reactor with duplicated artifacts

[ https://jira.codehaus.org/browse/MNG-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=346065#comment-346065 ] Sébastian Le Merdy commented on MNG-5613: - I've created a [new pull request|https://github.co

[jira] (SCM-741) scm:validate for svn should offer a way to check the current directory actually matches what's declared in the pom

[ https://jira.codehaus.org/browse/SCM-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=346063#comment-346063 ] Herve Boutemy edited comment on SCM-741 at 5/11/14 12:01 PM: - IT fixed in:

[jira] (MNGSITE-152) Maven websites don't follow ASF rules on License

[ https://jira.codehaus.org/browse/MNGSITE-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise reopened MNGSITE-152: - > Maven websites don't follow ASF rules on License >

[jira] (MNGSITE-152) Maven websites don't follow ASF rules on License

[ https://jira.codehaus.org/browse/MNGSITE-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=346062#comment-346062 ] Herve Boutemy commented on MNGSITE-152: --- misunderstanding, r1593809 is not sufficient: - dow

[jira] (MNGSITE-152) Maven websites don't follow ASF rules on License

[ https://jira.codehaus.org/browse/MNGSITE-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MNGSITE-152. --- Resolution: Fixed Assignee: Karl-Heinz Marbaise Fixed in [r1593809|http://svn.apach

[jira] (MJAVADOC-171) Modules in multi-module projects are "built" too often

[ https://jira.codehaus.org/browse/MJAVADOC-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MJAVADOC-171. -- Resolution: Fixed Assignee: Herve Boutemy part of the problem is fixed in MSHARED-266 (will

[jira] (MJAVADOC-171) Modules in multi-module projects are "built" too often

[ https://jira.codehaus.org/browse/MJAVADOC-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MJAVADOC-171: --- Attachment: mjavadoc-171-fixed-M3.zip > Modules in multi-module projects are "built" too often >

[jira] (MSITE-454) Don't use aggregator mojos for default report set

[ https://jira.codehaus.org/browse/MSITE-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MSITE-454. --- Resolution: Fixed Fix Version/s: 3.4 Assignee: Herve Boutemy fixed with MSHARED-266: see th

[jira] (MSHARED-266) run aggregator reports only when current projet is pom packaging and has modules

[ https://jira.codehaus.org/browse/MSHARED-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MSHARED-266. - Resolution: Fixed Fix Version/s: maven-reporting-exec-1.2 Assignee: Herve Boutemy fix

[jira] (MSHARED-333) display what phase or goal is forked by a report

[ https://jira.codehaus.org/browse/MSHARED-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=346025#comment-346025 ] Herve Boutemy commented on MSHARED-333: --- done in [r1593705|http://svn.apache.org/r1593705]

[jira] (MNG-5629) ClosedChannelException from DefaultUpdateCheckManager.read

[ https://jira.codehaus.org/browse/MNG-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=345905#comment-345905 ] Jason van Zyl commented on MNG-5629: Do you have a little sample project you provide or what you

[jira] (MASSEMBLY-699) Ability to create empty directories in assembly

[ https://jira.codehaus.org/browse/MASSEMBLY-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=345992#comment-345992 ] Karl-Heinz Marbaise commented on MASSEMBLY-699: --- You don't need to use maven-antru

[jira] (MNG-5630) improve display of forked executions

[ https://jira.codehaus.org/browse/MNG-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-5630: --- Description: actually, we have {noformat}[INFO] [INFO] >>> maven-javadoc-plugin:2.9.1:aggregate (report:agg

[jira] (MPMD-187) Report is generated even when skip is true

[ https://jira.codehaus.org/browse/MPMD-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=345887#comment-345887 ] Ryan Heinen commented on MPMD-187: -- Pull request for possible fix here: https://github.com/apache/m

[jira] (MNG-5625) Provide a terse informatoin about the used thread builder

[ https://jira.codehaus.org/browse/MNG-5625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=345907#comment-345907 ] Jason van Zyl commented on MNG-5625: +1 > Provide a terse informatoin about the used thread buil