[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 January 2022 no longer happens with 3.3.0.
> Upgrading to 3.0.0 causes `Could not build dependency tree` with repositories
> some unknown protocol
> ---
>
> Key: MENFORCER-393
> URL: https://issues.apache.org/jira/browse/MENFORCER-393
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: dependencyConvergence, Plugin
>Affects Versions: 3.0.0
>Reporter: johnny willer gasperi goncalves
>Assignee: Slawomir Jaranowski
>Priority: Major
> Attachments: enforcer_output
>
>
> After upgrading to 3.0.0, it's not possible to validate the POM anymore, an
> error like
> {code:java}
> Could not build dependency tree Could not collect dependencies:
> {jarname}{code}
> happens.
>
> I'm attaching the `mvn validate -X` dump (i have omitted some jars from the
> output)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[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 project that uses the shade plugin? I'm wondering whether I should add that exclusion line in our project (pdfbox) too. > Resolver will blindly assume it is deploying a plugin by presence of > META-INF/maven/plugins.xml in JAR > -- > > Key: MNG-8180 > URL: https://issues.apache.org/jira/browse/MNG-8180 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 3.9.0, 3.9.1, 3.9.2, 3.9.3, 3.9.4, 3.9.5, 3.9.6, 3.9.7, > 3.9.8 >Reporter: Tamas Cservenak >Assignee: Tamas Cservenak >Priority: Major > Fix For: 3.9.9, 4.0.0-beta-4 > > > Resolver will generate plugin metadata based on contents of > META-INF/maven/plugins.xml file, that for example in case of shaded JAR may > be totally off. > Circumvention: exclude this file from JAR. > All Maven 3.9.x and 4.x are affected. > Solution: the Artifact (checked for: has no classifier and is backed by JAR, > the requirements for maven-plugin JAR) and the embedded plugin metadata MUST > BE aligned (artifact GA == metadata GA). In this case all is happening as > before, happy path. In case of artifact GA != metadata GA we HARD FAIL the > build, as deploying "formally adhering to maven plugin JAR with rogue > metadata" may be very misleading. Most probably the origin of "rogue" plugin > metadata is by shading (like in case of Tika), or by some other rogue > resource, or even someone "reinventing" the plugin metadata for some other > purposes. Maven should simply prevent install/deploy of artifacts like these, > and users should fix the artifact (in case of shading, exclude that resource, > in other cases figure out from where it comes and eliminate it). > More context: in Maven3 this is most we can do, as repository metadata > generation happens in maven-resolver-provider module that does not and cannot > depend on maven-core (is "pure" resolver), hence notion of packaging, > project, build etc is not available. In Maven4 with new API we MAY do > something more later. The two PRs against 3.9.x and 4.0.0 are currently > identical. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 (Apache PDFBox project build on Windows 10)
> Fail to compile if the "generated-sources/annotations" does not exist
> -
>
> Key: MCOMPILER-567
> URL: https://issues.apache.org/jira/browse/MCOMPILER-567
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.12.0
>Reporter: Jorge Solórzano
>Assignee: Slawomir Jaranowski
>Priority: Critical
> Labels: pull-request-available
> Fix For: 3.12.1
>
>
> On some configurations (like a Kotlin project), the cleanup of the
> generated-soruces/annotations directory returns an error:
> {code:java}
> Caused by: java.lang.IllegalStateException: basedir
> /maven-compiler-plugin/target/it/MCOMPILER-XX/target/generated-sources/annotations
> does not exist
> at org.codehaus.plexus.util.DirectoryScanner.scan
> (DirectoryScanner.java:268)
> at
> org.codehaus.plexus.compiler.AbstractCompiler.getSourceFilesForSourceRoot
> (AbstractCompiler.java:168)
> at org.codehaus.plexus.compiler.AbstractCompiler.getSourceFiles
> (AbstractCompiler.java:194)
> at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile
> (JavacCompiler.java:138)
> at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute
> (AbstractCompilerMojo.java:1187)
> at org.apache.maven.plugin.compiler.CompilerMojo.execute
> (CompilerMojo.java:212)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:53)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:118)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke
> (DirectMethodHandleAccessor.java:103)
> at java.lang.reflect.Method.invoke (Method.java:580)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:283)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:226)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:407)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:348){code}
>
> I didn't catch this earlier since I don't use Kotlin and on a normal project,
> this should not be an issue since the javac documentation mentions that the
> directory, and any necessary subdirectories, will be created if they do not
> already exist.
> But on a somewhat modified project that compiles kotlin source code, this
> triggers an issue on plexus-compiler where the generated-soruces directory
> does not exist.
>
> This might be related to issue MCOMPILER-538, where it claims that generated
> source root is not required for javac, but additional confirmation is
> required.
>
> The fix will be to create the generated sources directory to preserve the
> current behavior.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[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: Dependency upgrade
Components: maven-plugins
Affects Versions: ASF-19
Environment: w7, mvn 3.5.3, jdk-10.0.1
Reporter: Tilman Hausherr
The apache parent pom has this line
{code}
2.20.1
{code}
however in jdk10 maven-surefire-plugin goes NPE. 2.21.0 works.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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
>
>
> Key: MPOM-185
> URL: https://issues.apache.org/jira/browse/MPOM-185
> Project: Maven POMs
> Issue Type: Dependency upgrade
> Components: maven-plugins
>Affects Versions: ASF-19
> Environment: w7, mvn 3.5.3, jdk-10.0.1
>Reporter: Tilman Hausherr
>Priority: Major
> Labels: jdk10
>
> The apache parent pom has this line
> {code}
> 2.20.1
> {code}
> however in jdk10 maven-surefire-plugin goes NPE. 2.21.0 works.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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, although with java 8 using java 6 for compiling, see
PDFBOX-4658.
> Compiler failure but no compiler message on the console
> ---
>
> Key: MCOMPILER-308
> URL: https://issues.apache.org/jira/browse/MCOMPILER-308
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Gary D. Gregory
>Priority: Major
>
> Using:
> Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
> 2017-04-03T13:39:06-06:00)
> Maven home: C:\Java\apache-maven-3.5.0\bin\..
> Java version: 9, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk-9
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> java version "9"
> Java(TM) SE Runtime Environment (build 9+181)
> Java HotSpot(TM) 64-Bit Server VM (build 9+181, mixed mode)
> Steps to reproduce:
> * git clone https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
> * git checkout tags/log4j-2.9.1-rc1
> * mvn -e verify
> Will give you:
> {noformat}
> [INFO] --- maven-compiler-plugin:3.7.0:testCompile (default-testCompile) @
> log4j-core ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 530 source files to
> C:\temp\rc\apache-log4j-2.9.1-src\log4j-core\target\test-classes
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Log4j 2 . SUCCESS [ 3.890
> s]
> [INFO] Apache Log4j API Java 9 support SUCCESS [ 8.330
> s]
> [INFO] Apache Log4j API ... SUCCESS [ 37.451
> s]
> [INFO] Apache Log4j Core .. FAILURE [ 55.364
> s]
> [INFO] Apache Log4j Core Integration Tests SKIPPED
> [INFO] Apache Log4j 1.x Compatibility API . SKIPPED
> [INFO] Apache Log4j SLF4J Binding . SKIPPED
> [INFO] Apache Log4j to SLF4J Adapter .. SKIPPED
> [INFO] Apache Log4j Commons Logging Bridge SKIPPED
> [INFO] Apache Log4j Flume Bridge .. SKIPPED
> [INFO] Apache Log4j Web ... SKIPPED
> [INFO] Apache Log4j Tag Library ... SKIPPED
> [INFO] Apache Log4j JMX GUI ... SKIPPED
> [INFO] Apache Log4j Samples ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Common ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Remote ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Embedded . SKIPPED
> [INFO] Apache Log4j Samples: Configuration SKIPPED
> [INFO] Apache Log4j Samples: LoggerProperties . SKIPPED
> [INFO] Apache Log4j OSGi .. SKIPPED
> [INFO] Apache Log4j BOM ... SKIPPED
> [INFO] Apache Log4j NoSQL . SKIPPED
> [INFO] Apache Log4J Performance Tests . SKIPPED
> [INFO] Apache Log4j Streaming Interface ... SKIPPED
> [INFO] Apache Log4j JUL Adapter ... SKIPPED
> [INFO] Apache Log4j Liquibase Binding . SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 01:47 min
> [INFO] Finished at: 2017-09-18T10:00:51-06:00
> [INFO] Final Memory: 41M/137M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:testCompile
> (default-testCompile) on project log4j-core: Compilation failure -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0:testCompile
> (default-testCompile) on project log4j-core: Compilation failure
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.j
[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:
We have the same problem, although with java 8 using java 6 for compiling, see
PDFBOX-4658. Updating to 3.8.1 (r1867783) did not help.
was (Author: tilman):
We have the same problem, although with java 8 using java 6 for compiling, see
PDFBOX-4658. Updating to 3.8.1. (r1867783) did not help.
> Compiler failure but no compiler message on the console
> ---
>
> Key: MCOMPILER-308
> URL: https://issues.apache.org/jira/browse/MCOMPILER-308
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Gary D. Gregory
>Priority: Major
>
> Using:
> Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
> 2017-04-03T13:39:06-06:00)
> Maven home: C:\Java\apache-maven-3.5.0\bin\..
> Java version: 9, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk-9
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> java version "9"
> Java(TM) SE Runtime Environment (build 9+181)
> Java HotSpot(TM) 64-Bit Server VM (build 9+181, mixed mode)
> Steps to reproduce:
> * git clone https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
> * git checkout tags/log4j-2.9.1-rc1
> * mvn -e verify
> Will give you:
> {noformat}
> [INFO] --- maven-compiler-plugin:3.7.0:testCompile (default-testCompile) @
> log4j-core ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 530 source files to
> C:\temp\rc\apache-log4j-2.9.1-src\log4j-core\target\test-classes
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Log4j 2 . SUCCESS [ 3.890
> s]
> [INFO] Apache Log4j API Java 9 support SUCCESS [ 8.330
> s]
> [INFO] Apache Log4j API ... SUCCESS [ 37.451
> s]
> [INFO] Apache Log4j Core .. FAILURE [ 55.364
> s]
> [INFO] Apache Log4j Core Integration Tests SKIPPED
> [INFO] Apache Log4j 1.x Compatibility API . SKIPPED
> [INFO] Apache Log4j SLF4J Binding . SKIPPED
> [INFO] Apache Log4j to SLF4J Adapter .. SKIPPED
> [INFO] Apache Log4j Commons Logging Bridge SKIPPED
> [INFO] Apache Log4j Flume Bridge .. SKIPPED
> [INFO] Apache Log4j Web ... SKIPPED
> [INFO] Apache Log4j Tag Library ... SKIPPED
> [INFO] Apache Log4j JMX GUI ... SKIPPED
> [INFO] Apache Log4j Samples ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Common ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Remote ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Embedded . SKIPPED
> [INFO] Apache Log4j Samples: Configuration SKIPPED
> [INFO] Apache Log4j Samples: LoggerProperties . SKIPPED
> [INFO] Apache Log4j OSGi .. SKIPPED
> [INFO] Apache Log4j BOM ... SKIPPED
> [INFO] Apache Log4j NoSQL . SKIPPED
> [INFO] Apache Log4J Performance Tests . SKIPPED
> [INFO] Apache Log4j Streaming Interface ... SKIPPED
> [INFO] Apache Log4j JUL Adapter ... SKIPPED
> [INFO] Apache Log4j Liquibase Binding . SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 01:47 min
> [INFO] Finished at: 2017-09-18T10:00:51-06:00
> [INFO] Final Memory: 41M/137M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:testCompile
> (default-testCompile) on project log4j-core: Compilation failure -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0:testCompile
> (default-testCompile) on project log4j-core: Compilation failure
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(Moj
[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:
We have the same problem, although with java 8 using java 6 for compiling, see
PDFBOX-4658. Updating to 3.8.1. (r1867783) did not help.
was (Author: tilman):
We have the same problem, although with java 8 using java 6 for compiling, see
PDFBOX-4658.
> Compiler failure but no compiler message on the console
> ---
>
> Key: MCOMPILER-308
> URL: https://issues.apache.org/jira/browse/MCOMPILER-308
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Gary D. Gregory
>Priority: Major
>
> Using:
> Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
> 2017-04-03T13:39:06-06:00)
> Maven home: C:\Java\apache-maven-3.5.0\bin\..
> Java version: 9, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk-9
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> java version "9"
> Java(TM) SE Runtime Environment (build 9+181)
> Java HotSpot(TM) 64-Bit Server VM (build 9+181, mixed mode)
> Steps to reproduce:
> * git clone https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
> * git checkout tags/log4j-2.9.1-rc1
> * mvn -e verify
> Will give you:
> {noformat}
> [INFO] --- maven-compiler-plugin:3.7.0:testCompile (default-testCompile) @
> log4j-core ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 530 source files to
> C:\temp\rc\apache-log4j-2.9.1-src\log4j-core\target\test-classes
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Log4j 2 . SUCCESS [ 3.890
> s]
> [INFO] Apache Log4j API Java 9 support SUCCESS [ 8.330
> s]
> [INFO] Apache Log4j API ... SUCCESS [ 37.451
> s]
> [INFO] Apache Log4j Core .. FAILURE [ 55.364
> s]
> [INFO] Apache Log4j Core Integration Tests SKIPPED
> [INFO] Apache Log4j 1.x Compatibility API . SKIPPED
> [INFO] Apache Log4j SLF4J Binding . SKIPPED
> [INFO] Apache Log4j to SLF4J Adapter .. SKIPPED
> [INFO] Apache Log4j Commons Logging Bridge SKIPPED
> [INFO] Apache Log4j Flume Bridge .. SKIPPED
> [INFO] Apache Log4j Web ... SKIPPED
> [INFO] Apache Log4j Tag Library ... SKIPPED
> [INFO] Apache Log4j JMX GUI ... SKIPPED
> [INFO] Apache Log4j Samples ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Common ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Remote ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Embedded . SKIPPED
> [INFO] Apache Log4j Samples: Configuration SKIPPED
> [INFO] Apache Log4j Samples: LoggerProperties . SKIPPED
> [INFO] Apache Log4j OSGi .. SKIPPED
> [INFO] Apache Log4j BOM ... SKIPPED
> [INFO] Apache Log4j NoSQL . SKIPPED
> [INFO] Apache Log4J Performance Tests . SKIPPED
> [INFO] Apache Log4j Streaming Interface ... SKIPPED
> [INFO] Apache Log4j JUL Adapter ... SKIPPED
> [INFO] Apache Log4j Liquibase Binding . SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 01:47 min
> [INFO] Finished at: 2017-09-18T10:00:51-06:00
> [INFO] Final Memory: 41M/137M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:testCompile
> (default-testCompile) on project log4j-core: Compilation failure -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0:testCompile
> (default-testCompile) on project log4j-core: Compilation failure
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
> org.apa
[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/SUREFIRE-1868
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Plugin
Affects Versions: 3.0.0-M5
Environment: W10, oracle jdk8.0_202, mvn 3.6.3
Reporter: Tilman Hausherr
I'm getting this text at the end of the tests
"Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in
org.apache.tika.utils.ServiceLoaderUtilsTest
writing to System.outwriting to System.errwriting to System.outwriting to
System.errwriting to System.outwriting to System.errwriting to
System.outwriting to System.errwriting to System.outwriting to System.err"
How to reproduce:
- get the Apache Tika project ("main" branch) from
https://github.com/apache/tika/
- change "3.0.0-M4" to "3.0.0-M5" in the pom.xml of the parent subproject
- build
- it happens with the first subproject (tika-core)
The build doesn't stop, but in my IDE it appears in red so it's probably a
warning or an error.
It does not happen with 3.0.0-M4.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[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 that it runs on jdk6 even if maven runs on
another jdk.
> Compiler failure but no compiler message on the console
> ---
>
> Key: MCOMPILER-308
> URL: https://issues.apache.org/jira/browse/MCOMPILER-308
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Gary D. Gregory
>Priority: Major
>
> Using:
> Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
> 2017-04-03T13:39:06-06:00)
> Maven home: C:\Java\apache-maven-3.5.0\bin\..
> Java version: 9, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk-9
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> java version "9"
> Java(TM) SE Runtime Environment (build 9+181)
> Java HotSpot(TM) 64-Bit Server VM (build 9+181, mixed mode)
> Steps to reproduce:
> * git clone https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
> * git checkout tags/log4j-2.9.1-rc1
> * mvn -e verify
> Will give you:
> {noformat}
> [INFO] --- maven-compiler-plugin:3.7.0:testCompile (default-testCompile) @
> log4j-core ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 530 source files to
> C:\temp\rc\apache-log4j-2.9.1-src\log4j-core\target\test-classes
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Log4j 2 . SUCCESS [ 3.890
> s]
> [INFO] Apache Log4j API Java 9 support SUCCESS [ 8.330
> s]
> [INFO] Apache Log4j API ... SUCCESS [ 37.451
> s]
> [INFO] Apache Log4j Core .. FAILURE [ 55.364
> s]
> [INFO] Apache Log4j Core Integration Tests SKIPPED
> [INFO] Apache Log4j 1.x Compatibility API . SKIPPED
> [INFO] Apache Log4j SLF4J Binding . SKIPPED
> [INFO] Apache Log4j to SLF4J Adapter .. SKIPPED
> [INFO] Apache Log4j Commons Logging Bridge SKIPPED
> [INFO] Apache Log4j Flume Bridge .. SKIPPED
> [INFO] Apache Log4j Web ... SKIPPED
> [INFO] Apache Log4j Tag Library ... SKIPPED
> [INFO] Apache Log4j JMX GUI ... SKIPPED
> [INFO] Apache Log4j Samples ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Common ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Remote ... SKIPPED
> [INFO] Apache Log4j Samples: Flume - Embedded . SKIPPED
> [INFO] Apache Log4j Samples: Configuration SKIPPED
> [INFO] Apache Log4j Samples: LoggerProperties . SKIPPED
> [INFO] Apache Log4j OSGi .. SKIPPED
> [INFO] Apache Log4j BOM ... SKIPPED
> [INFO] Apache Log4j NoSQL . SKIPPED
> [INFO] Apache Log4J Performance Tests . SKIPPED
> [INFO] Apache Log4j Streaming Interface ... SKIPPED
> [INFO] Apache Log4j JUL Adapter ... SKIPPED
> [INFO] Apache Log4j Liquibase Binding . SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 01:47 min
> [INFO] Finished at: 2017-09-18T10:00:51-06:00
> [INFO] Final Memory: 41M/137M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:testCompile
> (default-testCompile) on project log4j-core: Compilation failure -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0:testCompile
> (default-testCompile) on project log4j-core: Compilation failure
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:8
[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 project. I was trying to change version from
3.0.0-M3 to 3.0.0 and one of the subprojects fails.
Old output
{noformat}
--- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven-version) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-java-version) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-output-timestamp-property)
@ tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0-M3:enforce (ban-bad-log4j-versions) @
tika-parser-scientific-module ---
{noformat}
New output
{noformat}
--- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0:enforce (enforce-java-version) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0:enforce (enforce-output-timestamp-property) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0:enforce (enforce-maven) @
tika-parser-scientific-module ---
Rule 0: org.apache.maven.plugins.enforcer.DependencyConvergence failed with
message:
Could not build dependency tree Could not collect dependencies:
org.apache.tika:tika-parser-scientific-module:jar:2.2.2-SNAPSHOT ()
{noformat}
> Upgrading to 3.0.0 causes `Could not build dependency tree` with repositories
> some unknown protocol
> ---
>
> Key: MENFORCER-393
> URL: https://issues.apache.org/jira/browse/MENFORCER-393
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 3.0.0
>Reporter: johnny willer gasperi goncalves
>Priority: Major
> Attachments: enforcer_output
>
>
> After upgrading to 3.0.0, it's not possible to validate the POM anymore, an
> error like
> {code:java}
> Could not build dependency tree Could not collect dependencies:
> {jarname}{code}
> happens.
>
> I'm attaching the `mvn validate -X` dump (i have omitted some jars from the
> output)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[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:
Same problem in the Apache Tika project ( https://github.com/apache/tika/ ). I
was trying to change version from 3.0.0-M3 to 3.0.0 and one of the subprojects
fails.
Old output
{noformat}
--- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven-version) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-java-version) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-output-timestamp-property)
@ tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0-M3:enforce (ban-bad-log4j-versions) @
tika-parser-scientific-module ---
{noformat}
New output
{noformat}
--- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0:enforce (enforce-java-version) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0:enforce (enforce-output-timestamp-property) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0:enforce (enforce-maven) @
tika-parser-scientific-module ---
Rule 0: org.apache.maven.plugins.enforcer.DependencyConvergence failed with
message:
Could not build dependency tree Could not collect dependencies:
org.apache.tika:tika-parser-scientific-module:jar:2.2.2-SNAPSHOT ()
{noformat}
was (Author: tilman):
Same problem in the Apache Tika project. I was trying to change version from
3.0.0-M3 to 3.0.0 and one of the subprojects fails.
Old output
{noformat}
--- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven-version) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-java-version) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-output-timestamp-property)
@ tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0-M3:enforce (ban-bad-log4j-versions) @
tika-parser-scientific-module ---
{noformat}
New output
{noformat}
--- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0:enforce (enforce-java-version) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0:enforce (enforce-output-timestamp-property) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0:enforce (enforce-maven) @
tika-parser-scientific-module ---
Rule 0: org.apache.maven.plugins.enforcer.DependencyConvergence failed with
message:
Could not build dependency tree Could not collect dependencies:
org.apache.tika:tika-parser-scientific-module:jar:2.2.2-SNAPSHOT ()
{noformat}
> Upgrading to 3.0.0 causes `Could not build dependency tree` with repositories
> some unknown protocol
> ---
>
> Key: MENFORCER-393
> URL: https://issues.apache.org/jira/browse/MENFORCER-393
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 3.0.0
>Reporter: johnny willer gasperi goncalves
>Priority: Major
> Attachments: enforcer_output
>
>
> After upgrading to 3.0.0, it's not possible to validate the POM anymore, an
> error like
> {code:java}
> Could not build dependency tree Could not collect dependencies:
> {jarname}{code}
> happens.
>
> I'm attaching the `mvn validate -X` dump (i have omitted some jars from the
> output)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[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:
Same problem in the Apache Tika project ( https://github.com/apache/tika/ ). I
was trying to change version from 3.0.0-M3 to 3.0.0 in the parent pom.xml and
one of the subprojects fails.
Old output
{noformat}
--- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven-version) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-java-version) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-output-timestamp-property)
@ tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0-M3:enforce (ban-bad-log4j-versions) @
tika-parser-scientific-module ---
{noformat}
New output
{noformat}
--- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0:enforce (enforce-java-version) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0:enforce (enforce-output-timestamp-property) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0:enforce (enforce-maven) @
tika-parser-scientific-module ---
Rule 0: org.apache.maven.plugins.enforcer.DependencyConvergence failed with
message:
Could not build dependency tree Could not collect dependencies:
org.apache.tika:tika-parser-scientific-module:jar:2.2.2-SNAPSHOT ()
{noformat}
was (Author: tilman):
Same problem in the Apache Tika project ( https://github.com/apache/tika/ ). I
was trying to change version from 3.0.0-M3 to 3.0.0 and one of the subprojects
fails.
Old output
{noformat}
--- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven-version) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-java-version) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-output-timestamp-property)
@ tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0-M3:enforce (ban-bad-log4j-versions) @
tika-parser-scientific-module ---
{noformat}
New output
{noformat}
--- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0:enforce (enforce-java-version) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0:enforce (enforce-output-timestamp-property) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0:enforce (enforce-maven) @
tika-parser-scientific-module ---
Rule 0: org.apache.maven.plugins.enforcer.DependencyConvergence failed with
message:
Could not build dependency tree Could not collect dependencies:
org.apache.tika:tika-parser-scientific-module:jar:2.2.2-SNAPSHOT ()
{noformat}
> Upgrading to 3.0.0 causes `Could not build dependency tree` with repositories
> some unknown protocol
> ---
>
> Key: MENFORCER-393
> URL: https://issues.apache.org/jira/browse/MENFORCER-393
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 3.0.0
>Reporter: johnny willer gasperi goncalves
>Priority: Major
> Attachments: enforcer_output
>
>
> After upgrading to 3.0.0, it's not possible to validate the POM anymore, an
> error like
> {code:java}
> Could not build dependency tree Could not collect dependencies:
> {jarname}{code}
> happens.
>
> I'm attaching the `mvn validate -X` dump (i have omitted some jars from the
> output)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[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 comment, I had to change two entries in another
subproject due to convergence problems, like this because osgi 6 was used
elsewhere, and log4j has a weak dependency on an earlier version of osgi:
{code}
org.apache.logging.log4j
log4j-core
${log4j2.version}
test
org.osgi
org.osgi.core
{code}
> Upgrading to 3.0.0 causes `Could not build dependency tree` with repositories
> some unknown protocol
> ---
>
> Key: MENFORCER-393
> URL: https://issues.apache.org/jira/browse/MENFORCER-393
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 3.0.0
>Reporter: johnny willer gasperi goncalves
>Priority: Major
> Attachments: enforcer_output
>
>
> After upgrading to 3.0.0, it's not possible to validate the POM anymore, an
> error like
> {code:java}
> Could not build dependency tree Could not collect dependencies:
> {jarname}{code}
> happens.
>
> I'm attaching the `mvn validate -X` dump (i have omitted some jars from the
> output)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[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 Info Reports Plugin Issue Type: Bug Reporter: Tilman Hausherr https://maven.apache.org/plugins/maven-project-info-reports-plugin/ The "Incompatibility Notice" table has "issue-management" twice. I suspect the left one should have been "issue-tracking". -- This message was sent by Atlassian Jira (v8.20.1#820001)
[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.
> Upgrading to 3.0.0 causes `Could not build dependency tree` with repositories
> some unknown protocol
> ---
>
> Key: MENFORCER-393
> URL: https://issues.apache.org/jira/browse/MENFORCER-393
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 3.0.0
>Reporter: johnny willer gasperi goncalves
>Priority: Major
> Attachments: enforcer_output
>
>
> After upgrading to 3.0.0, it's not possible to validate the POM anymore, an
> error like
> {code:java}
> Could not build dependency tree Could not collect dependencies:
> {jarname}{code}
> happens.
>
> I'm attaching the `mvn validate -X` dump (i have omitted some jars from the
> output)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
