[jira] [Commented] (MNG-8180) Resolver will blindly assume it is deploying a plugin by presence of META-INF/maven/plugins.xml in JAR

[ https://issues.apache.org/jira/browse/MNG-8180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17865293#comment-17865293 ] Tilman Hausherr commented on MNG-8180: -- Is this a problem that applies to every projec

[jira] [Commented] (MCOMPILER-567) Fail to compile if the "generated-sources/annotations" does not exist

[ https://issues.apache.org/jira/browse/MCOMPILER-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799426#comment-17799426 ] Tilman Hausherr commented on MCOMPILER-567: --- Works with 3.12.1-SNAPSHOT (Apa

[jira] [Commented] (MENFORCER-393) Upgrading to 3.0.0 causes `Could not build dependency tree` with repositories some unknown protocol

[ https://issues.apache.org/jira/browse/MENFORCER-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724638#comment-17724638 ] Tilman Hausherr commented on MENFORCER-393: --- The problem I mentioned in Janu

[jira] [Commented] (MENFORCER-393) Upgrading to 3.0.0 causes `Could not build dependency tree` with repositories some unknown protocol

[ https://issues.apache.org/jira/browse/MENFORCER-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17554206#comment-17554206 ] Tilman Hausherr commented on MENFORCER-393: --- Still happens with 3.1.0. > Up

[jira] [Created] (MPIR-415) Wrong old goal name in "Incompatibility Notice" table in website

Tilman Hausherr created MPIR-415: Summary: Wrong old goal name in "Incompatibility Notice" table in website Key: MPIR-415 URL: https://issues.apache.org/jira/browse/MPIR-415 Project: Maven Project Inf

[jira] [Commented] (MENFORCER-393) Upgrading to 3.0.0 causes `Could not build dependency tree` with repositories some unknown protocol

[ https://issues.apache.org/jira/browse/MENFORCER-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471279#comment-17471279 ] Tilman Hausherr commented on MENFORCER-393: --- Maybe related: before the above

[jira] [Comment Edited] (MENFORCER-393) Upgrading to 3.0.0 causes `Could not build dependency tree` with repositories some unknown protocol

[ https://issues.apache.org/jira/browse/MENFORCER-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471170#comment-17471170 ] Tilman Hausherr edited comment on MENFORCER-393 at 1/8/22, 4:31 PM:

[jira] [Comment Edited] (MENFORCER-393) Upgrading to 3.0.0 causes `Could not build dependency tree` with repositories some unknown protocol

[ https://issues.apache.org/jira/browse/MENFORCER-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471170#comment-17471170 ] Tilman Hausherr edited comment on MENFORCER-393 at 1/8/22, 4:31 PM:

[jira] [Commented] (MENFORCER-393) Upgrading to 3.0.0 causes `Could not build dependency tree` with repositories some unknown protocol

[ https://issues.apache.org/jira/browse/MENFORCER-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471170#comment-17471170 ] Tilman Hausherr commented on MENFORCER-393: --- Same problem in the Apache Tika

[jira] [Commented] (MCOMPILER-308) Compiler failure but no compiler message on the console

[ https://issues.apache.org/jira/browse/MCOMPILER-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17356604#comment-17356604 ] Tilman Hausherr commented on MCOMPILER-308: --- IIRC the fork was to make sure

[jira] [Created] (SUREFIRE-1868) writing to System.outwriting to System.errwriting to System.outwriting to System.errwriting

Tilman Hausherr created SUREFIRE-1868: - Summary: writing to System.outwriting to System.errwriting to System.outwriting to System.errwriting Key: SUREFIRE-1868 URL: https://issues.apache.org/jira/browse/SUREFI

[jira] [Comment Edited] (MCOMPILER-308) Compiler failure but no compiler message on the console

[ https://issues.apache.org/jira/browse/MCOMPILER-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123341#comment-17123341 ] Tilman Hausherr edited comment on MCOMPILER-308 at 6/2/20, 4:44 AM:

[jira] [Comment Edited] (MCOMPILER-308) Compiler failure but no compiler message on the console

[ https://issues.apache.org/jira/browse/MCOMPILER-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123341#comment-17123341 ] Tilman Hausherr edited comment on MCOMPILER-308 at 6/2/20, 4:44 AM:

[jira] [Commented] (MCOMPILER-308) Compiler failure but no compiler message on the console

[ https://issues.apache.org/jira/browse/MCOMPILER-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123341#comment-17123341 ] Tilman Hausherr commented on MCOMPILER-308: --- We have the same problem, altho

[jira] [Created] (MPOM-185) jdk10 needs maven-surefire-plugin version 2.21.0

Tilman Hausherr created MPOM-185: Summary: jdk10 needs maven-surefire-plugin version 2.21.0 Key: MPOM-185 URL: https://issues.apache.org/jira/browse/MPOM-185 Project: Maven POMs Issue Type: D

[jira] [Updated] (MPOM-185) jdk10 needs maven-surefire-plugin version 2.21.0

[ https://issues.apache.org/jira/browse/MPOM-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tilman Hausherr updated MPOM-185: - Labels: jdk10 (was: ) > jdk10 needs maven-surefire-plugin version 2.21.0 > ---