[jira] [Commented] (MNG-7485) Failed To Load JANSI Native Library

[ https://issues.apache.org/jira/browse/MNG-7485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17557895#comment-17557895 ] Mark commented on MNG-7485: --- Yeah this was a no go for us to. I will raise a change request with JANSI. > Failed

[jira] [Commented] (MNG-7485) Failed To Load JANSI Native Library

[ https://issues.apache.org/jira/browse/MNG-7485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550470#comment-17550470 ] Mark commented on MNG-7485: --- I can confirm that this has solved our issue. > Failed To Load JANSI Native Library

[jira] [Commented] (MNG-7485) Failed To Load JANSI Native Library

[ https://issues.apache.org/jira/browse/MNG-7485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17550358#comment-17550358 ] Mark commented on MNG-7485: --- Hi Michael - apologies for the late response, been on leave for the last week.

[jira] [Created] (MNG-7485) Failed To Load JANSI Native Library

Mark created MNG-7485: - Summary: Failed To Load JANSI Native Library Key: MNG-7485 URL: https://issues.apache.org/jira/browse/MNG-7485 Project: Maven Issue Type: Bug Components: Errors

[jira] [Updated] (MNG-6908) how to debug maven source code

[ https://issues.apache.org/jira/browse/MNG-6908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mark updated MNG-6908: -- Description: how to debug maven source code > how to debug maven source code > --- > >

[jira] [Created] (MNG-6908) how to debug maven source code

mark created MNG-6908: - Summary: how to debug maven source code Key: MNG-6908 URL: https://issues.apache.org/jira/browse/MNG-6908 Project: Maven Issue Type: Wish Components: core, Embedding

[jira] [Commented] (MNG-3655) Allow multiple local repositories

[ https://issues.apache.org/jira/browse/MNG-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762790#comment-16762790 ] Mark commented on MNG-3655: --- How about appending the branch name to the version? > Allow multiple local

[jira] [Updated] (MANTRUN-216) CLONE - Use of AntRun during clean phase fails multiproject with intermodule dependencies

[ https://issues.apache.org/jira/browse/MANTRUN-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark updated MANTRUN-216: - Description: Can't re-open the original issue. The blocking issue MNG-3283 is said to be fixed. Does the

[jira] [Updated] (MANTRUN-216) CLONE - Use of AntRun during clean phase fails multiproject with intermodule dependencies

[ https://issues.apache.org/jira/browse/MANTRUN-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark updated MANTRUN-216: - Description: Can't re-open the original issue. The blocking issue is said to be fixed. Attaching the antrun

[jira] [Updated] (MANTRUN-216) CLONE - Use of AntRun during clean phase fails multiproject with intermodule dependencies

[ https://issues.apache.org/jira/browse/MANTRUN-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark updated MANTRUN-216: - Description: Can't re-open the original issue. Attaching the antrun plugin to the clean phase causes it to

[jira] [Updated] (MANTRUN-216) CLONE - Use of AntRun during clean phase fails multiproject with intermodule dependencies

[ https://issues.apache.org/jira/browse/MANTRUN-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark updated MANTRUN-216: - Description: Attaching the antrun plugin to the clean phase causes it to interfere with local dependency

[jira] [Updated] (MANTRUN-216) CLONE - Use of AntRun during clean phase fails multiproject with intermodule dependencies

[ https://issues.apache.org/jira/browse/MANTRUN-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark updated MANTRUN-216: - Affects Version/s: (was: 1.2) (was: 1.1) 1.8 > CLONE -

[jira] [Updated] (MANTRUN-216) CLONE - Use of AntRun during clean phase fails multiproject with intermodule dependencies

[ https://issues.apache.org/jira/browse/MANTRUN-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark updated MANTRUN-216: - Environment: Maven version: 3.6.0 Java version: 11.0.2-open OS name: ubuntu 18 x86-64 was: Maven version:

[jira] [Created] (MANTRUN-216) CLONE - Use of AntRun during clean phase fails multiproject with intermodule dependencies

Mark created MANTRUN-216: Summary: CLONE - Use of AntRun during clean phase fails multiproject with intermodule dependencies Key: MANTRUN-216 URL: https://issues.apache.org/jira/browse/MANTRUN-216 Project:

[jira] [Commented] (MANTRUN-78) Use of AntRun during clean phase fails multiproject with intermodule dependencies

[ https://issues.apache.org/jira/browse/MANTRUN-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16761718#comment-16761718 ] Mark commented on MANTRUN-78: - Issue still exists with maven 3.6.0 and antrun plugin 1.8 in pre-clean phase.

[jira] [Created] (MCOMPILER-371) RFE: support new javac option "-h"

Mark created MCOMPILER-371: -- Summary: RFE: support new javac option "-h" Key: MCOMPILER-371 URL: https://issues.apache.org/jira/browse/MCOMPILER-371 Project: Maven Compiler Plugin Issue Type:

[jira] [Updated] (SUREFIRE-1534) Surefire 2.21.0 ClassNotFoundException: org.apache.maven.plugin.surefire.StartupReportConfiguration using reuseForks set to false

[ https://issues.apache.org/jira/browse/SUREFIRE-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark updated SUREFIRE-1534: --- Summary: Surefire 2.21.0 ClassNotFoundException:

[jira] [Created] (SUREFIRE-1534) Surefire 2.21.0 ClassNotFoundException: org.apache.maven.plugin.surefire.StartupReportConfiguration

Mark created SUREFIRE-1534: -- Summary: Surefire 2.21.0 ClassNotFoundException: org.apache.maven.plugin.surefire.StartupReportConfiguration Key: SUREFIRE-1534 URL: https://issues.apache.org/jira/browse/SUREFIRE-1534

[jira] [Comment Edited] (SUREFIRE-951) Better handling of file.encoding system property

[ https://issues.apache.org/jira/browse/SUREFIRE-951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15333559#comment-15333559 ] Mark edited comment on SUREFIRE-951 at 6/16/16 10:53 AM: - still not working

[jira] [Commented] (SUREFIRE-951) Better handling of file.encoding system property

[ https://issues.apache.org/jira/browse/SUREFIRE-951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15333559#comment-15333559 ] Mark commented on SUREFIRE-951: --- still not working reliably as of surefire 2.19.1. > Better handling of

[jira] [Updated] (SUREFIRE-1235) generic/consolidated rapid test execution support needed

[ https://issues.apache.org/jira/browse/SUREFIRE-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark updated SUREFIRE-1235: --- Issue Type: Wish (was: Improvement) > generic/consolidated rapid test execution support needed >

[jira] [Updated] (SUREFIRE-1235) generic/consolidated rapid test execution support needed

[ https://issues.apache.org/jira/browse/SUREFIRE-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark updated SUREFIRE-1235: --- Description: Many IDEs have seemingly implemented their own rapid test unit execution infrastracture.

[jira] [Updated] (SUREFIRE-1235) generic/consolidated rapid test execution support needed

[ https://issues.apache.org/jira/browse/SUREFIRE-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark updated SUREFIRE-1235: --- Summary: generic/consolidated rapid test execution support needed (was: rapid test execution support

[jira] [Created] (SUREFIRE-1235) rapid test execution support needed

Mark created SUREFIRE-1235: -- Summary: rapid test execution support needed Key: SUREFIRE-1235 URL: https://issues.apache.org/jira/browse/SUREFIRE-1235 Project: Maven Surefire Issue Type: Improvement

[jira] [Created] (MCOMPILER-263) basedir system property is wrong when executing annotation processor in non-forked mode

Mark created MCOMPILER-263: -- Summary: basedir system property is wrong when executing annotation processor in non-forked mode Key: MCOMPILER-263 URL: https://issues.apache.org/jira/browse/MCOMPILER-263

[jira] [Created] (MCHECKSTYLE-317) Checkstyle plugin causing maven site generation to fail

John Mark created MCHECKSTYLE-317: - Summary: Checkstyle plugin causing maven site generation to fail Key: MCHECKSTYLE-317 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-317 Project: Maven

[jira] (MSHARED-4) DefaultDependencyTreeBuilder ignores artifact filter

[ https://jira.codehaus.org/browse/MSHARED-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=356781#comment-356781 ] Mark commented on MSHARED-4: Probably related: I need a mechanism to detect cyclic dependencies outside

[jira] (MENFORCER-215) Extra Enforcer Rules : banCircularDependencies for transitive test scope

Mark created MENFORCER-215: -- Summary: Extra Enforcer Rules : banCircularDependencies for transitive test scope Key: MENFORCER-215 URL: https://jira.codehaus.org/browse/MENFORCER-215 Project: Maven Enforcer

[jira] (MENFORCER-215) Extra Enforcer Rules : banCircularDependencies for transitive test scope

[ https://jira.codehaus.org/browse/MENFORCER-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark updated MENFORCER-215: --- Description: I want to use the banCircularDependencies extra enforcer rule to avoid jenkins build loops. The

[jira] (MJAVADOC-419) nooverview configuration parameter cannot be used because of non-null overview config param default

Mark created MJAVADOC-419: - Summary: nooverview configuration parameter cannot be used because of non-null overview config param default Key: MJAVADOC-419 URL: https://jira.codehaus.org/browse/MJAVADOC-419

[jira] (MJAVADOC-419) nooverview configuration parameter cannot be used because of non-null overview config param default

[ https://jira.codehaus.org/browse/MJAVADOC-419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=355050#comment-355050 ] Mark commented on MJAVADOC-419: --- [ERROR] Failed to execute goal

[jira] (MCLEAN-55) maven clean seems to use old java.io API to clean the target directory

[ https://jira.codehaus.org/browse/MCLEAN-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=350044#comment-350044 ] Mark commented on MCLEAN-55: Done. maven clean seems to use old java.io API to clean the target

[jira] (MCLEAN-55) maven clean seems to use old java.io API to clean the target directory

Mark created MCLEAN-55: -- Summary: maven clean seems to use old java.io API to clean the target directory Key: MCLEAN-55 URL: https://jira.codehaus.org/browse/MCLEAN-55 Project: Maven Clean Plugin

[jira] (MCLEAN-55) maven clean seems to use old java.io API to clean the target directory

[ https://jira.codehaus.org/browse/MCLEAN-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark updated MCLEAN-55: --- Description: Problem: the old java.io API cannot handle filenames that have a bad encoding, ie. iso-8859-1 encoded

[jira] (MNG-3655) Allow multiple local repositories

[ https://jira.codehaus.org/browse/MNG-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=299052#comment-299052 ] Mark commented on MNG-3655: --- Yes, that would be great. Would improve repeatability of builds and eliminate

[jira] (MDEP-82) go-offline / resolve-plugins does not resolve all plugin dependencies

[ https://jira.codehaus.org/browse/MDEP-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=292446#comment-292446 ] Mark commented on MDEP-82: -- This issue is even more annoying for proper two-phase deployments where packages

[jira] Commented: (MSHADE-30) duplicate entry error

[ http://jira.codehaus.org/browse/MSHADE-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=145757#action_145757 ] Mark commented on MSHADE-30: Thanks for the patch Henrik! as this is still not fixed in 1.1 or