[jira] [Commented] (MJAVADOC-793) java.lang.NullPointerException: Cannot invoke "String.length()" because "text" is null

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MJAVADOC-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848313#comment-17848313
 ] 

Gary D. Gregory commented on MJAVADOC-793:
--

Another wrinkle is that modern Javadoc tool versions no longer let you point to 
Java 8 and instead issue a warning and replace the link to Java 22 Javadoc (if 
you're on Java 22 for example).


> java.lang.NullPointerException: Cannot invoke "String.length()" because 
> "text" is null
> --
>
> Key: MJAVADOC-793
> URL: https://issues.apache.org/jira/browse/MJAVADOC-793
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.6.3
>Reporter: Gary D. Gregory
>Priority: Blocker
> Fix For: 3.6.4
>
>
> Plugin throws {{NullPointerException}} when running {{{}javadoc:javadoc{}}}.
> See:
>  * Failing PR: https://github.com/apache/commons-compress/pull/528
>  * Build log: 
> [https://github.com/apache/commons-compress/actions/runs/9113449616/job/25054982405?pr=528]
> Or:
>  # git clone [https://gitbox.apache.org/repos/asf/commons-compress.git]
>  # git checkout 542cc5a602a9128932e3fb75503383e481141e7e
>  # Edit pom.xml and set the parent POM to version 70
>  # Run 'mvn javadoc:javadoc' causes:
> {noformat}
> [INFO] --- javadoc:3.6.3:javadoc (default-cli) @ commons-compress ---
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  8.434 s
> [INFO] Finished at: 2024-05-16T09:36:02-04:00
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:3.6.3:javadoc (default-cli) on 
> project commons-compress: Execution default-cli of goal 
> org.apache.maven.plugins:maven-javadoc-plugin:3.6.3:javadoc failed: Cannot 
> invoke "String.length()" because "text" is null -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-javadoc-plugin:3.6.3:javadoc 
> (default-cli) on project commons-compress: Execution default-cli of goal 
> org.apache.maven.plugins:maven-javadoc-plugin:3.6.3:javadoc failed: Cannot 
> invoke "String.length()" because "text" is null
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:333)
> 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.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke 
> (NativeMethodAccessorImpl.java:77)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke 
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:568)
> 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)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
> 

[jira] [Commented] (MJAVADOC-793) java.lang.NullPointerException: Cannot invoke "String.length()" because "text" is null

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MJAVADOC-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848012#comment-17848012
 ] 

Gary D. Gregory commented on MJAVADOC-793:
--

I would expect a missing value in an XML document to map to an empty string or 
no-op at worst, not an NPE which is completely undecipherable to a user.

> java.lang.NullPointerException: Cannot invoke "String.length()" because 
> "text" is null
> --
>
> Key: MJAVADOC-793
> URL: https://issues.apache.org/jira/browse/MJAVADOC-793
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.6.3
>Reporter: Gary D. Gregory
>Priority: Blocker
> Fix For: 3.6.4
>
>
> Plugin throws {{NullPointerException}} when running {{{}javadoc:javadoc{}}}.
> See:
>  * Failing PR: https://github.com/apache/commons-compress/pull/528
>  * Build log: 
> [https://github.com/apache/commons-compress/actions/runs/9113449616/job/25054982405?pr=528]
> Or:
>  # git clone [https://gitbox.apache.org/repos/asf/commons-compress.git]
>  # git checkout 542cc5a602a9128932e3fb75503383e481141e7e
>  # Edit pom.xml and set the parent POM to version 70
>  # Run 'mvn javadoc:javadoc' causes:
> {noformat}
> [INFO] --- javadoc:3.6.3:javadoc (default-cli) @ commons-compress ---
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  8.434 s
> [INFO] Finished at: 2024-05-16T09:36:02-04:00
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:3.6.3:javadoc (default-cli) on 
> project commons-compress: Execution default-cli of goal 
> org.apache.maven.plugins:maven-javadoc-plugin:3.6.3:javadoc failed: Cannot 
> invoke "String.length()" because "text" is null -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-javadoc-plugin:3.6.3:javadoc 
> (default-cli) on project commons-compress: Execution default-cli of goal 
> org.apache.maven.plugins:maven-javadoc-plugin:3.6.3:javadoc failed: Cannot 
> invoke "String.length()" because "text" is null
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:333)
> 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.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke 
> (NativeMethodAccessorImpl.java:77)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke 
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:568)
> 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)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
> default-cli of goal 
> 

[jira] [Commented] (MJAVADOC-793) java.lang.NullPointerException: Cannot invoke "String.length()" because "text" is null

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MJAVADOC-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847878#comment-17847878
 ] 

Gary D. Gregory commented on MJAVADOC-793:
--

A possible low-level fix: https://github.com/codehaus-plexus/plexus-xml/pull/29


> java.lang.NullPointerException: Cannot invoke "String.length()" because 
> "text" is null
> --
>
> Key: MJAVADOC-793
> URL: https://issues.apache.org/jira/browse/MJAVADOC-793
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.6.3
>Reporter: Gary D. Gregory
>Priority: Blocker
> Fix For: 3.6.4
>
>
> Plugin throws {{NullPointerException}} when running {{{}javadoc:javadoc{}}}.
> See:
>  * Failing PR: https://github.com/apache/commons-compress/pull/528
>  * Build log: 
> [https://github.com/apache/commons-compress/actions/runs/9113449616/job/25054982405?pr=528]
> Or:
>  # git clone [https://gitbox.apache.org/repos/asf/commons-compress.git]
>  # git checkout 542cc5a602a9128932e3fb75503383e481141e7e
>  # Edit pom.xml and set the parent POM to version 70
>  # Run 'mvn javadoc:javadoc' causes:
> {noformat}
> [INFO] --- javadoc:3.6.3:javadoc (default-cli) @ commons-compress ---
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  8.434 s
> [INFO] Finished at: 2024-05-16T09:36:02-04:00
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:3.6.3:javadoc (default-cli) on 
> project commons-compress: Execution default-cli of goal 
> org.apache.maven.plugins:maven-javadoc-plugin:3.6.3:javadoc failed: Cannot 
> invoke "String.length()" because "text" is null -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-javadoc-plugin:3.6.3:javadoc 
> (default-cli) on project commons-compress: Execution default-cli of goal 
> org.apache.maven.plugins:maven-javadoc-plugin:3.6.3:javadoc failed: Cannot 
> invoke "String.length()" because "text" is null
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:333)
> 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.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke 
> (NativeMethodAccessorImpl.java:77)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke 
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:568)
> 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)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
> default-cli of goal 
> org.apache.maven.plugins:maven-javadoc-plugin:3.6.3:javadoc failed: Cannot 
> invoke 

[jira] [Commented] (MJAVADOC-793) java.lang.NullPointerException: Cannot invoke "String.length()" because "text" is null

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MJAVADOC-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847680#comment-17847680
 ] 

Gary D. Gregory commented on MJAVADOC-793:
--

Hi,

Any thoughts on pushing out a release sooner rather than later?

 

> java.lang.NullPointerException: Cannot invoke "String.length()" because 
> "text" is null
> --
>
> Key: MJAVADOC-793
> URL: https://issues.apache.org/jira/browse/MJAVADOC-793
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.6.3
>Reporter: Gary D. Gregory
>Priority: Blocker
> Fix For: 3.6.4
>
>
> Plugin throws {{NullPointerException}} when running {{{}javadoc:javadoc{}}}.
> See:
>  * Failing PR: https://github.com/apache/commons-compress/pull/528
>  * Build log: 
> [https://github.com/apache/commons-compress/actions/runs/9113449616/job/25054982405?pr=528]
> Or:
>  # git clone [https://gitbox.apache.org/repos/asf/commons-compress.git]
>  # git checkout 542cc5a602a9128932e3fb75503383e481141e7e
>  # Edit pom.xml and set the parent POM to version 70
>  # Run 'mvn javadoc:javadoc' causes:
> {noformat}
> [INFO] --- javadoc:3.6.3:javadoc (default-cli) @ commons-compress ---
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  8.434 s
> [INFO] Finished at: 2024-05-16T09:36:02-04:00
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:3.6.3:javadoc (default-cli) on 
> project commons-compress: Execution default-cli of goal 
> org.apache.maven.plugins:maven-javadoc-plugin:3.6.3:javadoc failed: Cannot 
> invoke "String.length()" because "text" is null -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-javadoc-plugin:3.6.3:javadoc 
> (default-cli) on project commons-compress: Execution default-cli of goal 
> org.apache.maven.plugins:maven-javadoc-plugin:3.6.3:javadoc failed: Cannot 
> invoke "String.length()" because "text" is null
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:333)
> 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.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke 
> (NativeMethodAccessorImpl.java:77)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke 
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:568)
> 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)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
> default-cli of goal 
> org.apache.maven.plugins:maven-javadoc-plugin:3.6.3:javadoc failed: Cannot 
> invoke "String.length()" 

[jira] [Updated] (MJAVADOC-793) java.lang.NullPointerException: Cannot invoke "String.length()" because "text" is null

[Gary D. Gregory (Jira)]

 [ 
https://issues.apache.org/jira/browse/MJAVADOC-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gary D. Gregory updated MJAVADOC-793:
-
Description: 
Plugin throws {{NullPointerException}} when running {{{}javadoc:javadoc{}}}.

See:
 * Failing PR: https://github.com/apache/commons-compress/pull/528
 * Build log: 
[https://github.com/apache/commons-compress/actions/runs/9113449616/job/25054982405?pr=528]

Or:
 # git clone [https://gitbox.apache.org/repos/asf/commons-compress.git]
 # git checkout 542cc5a602a9128932e3fb75503383e481141e7e
 # Edit pom.xml and set the parent POM to version 70
 # Run 'mvn javadoc:javadoc' causes:

{noformat}
[INFO] --- javadoc:3.6.3:javadoc (default-cli) @ commons-compress ---
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  8.434 s
[INFO] Finished at: 2024-05-16T09:36:02-04:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.6.3:javadoc (default-cli) on 
project commons-compress: Execution default-cli of goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.6.3:javadoc failed: Cannot 
invoke "String.length()" because "text" is null -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.6.3:javadoc (default-cli) on 
project commons-compress: Execution default-cli of goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.6.3:javadoc failed: Cannot 
invoke "String.length()" because "text" is null
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
(MojoExecutor.java:333)
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.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke 
(NativeMethodAccessorImpl.java:77)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke 
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:568)
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)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
default-cli of goal org.apache.maven.plugins:maven-javadoc-plugin:3.6.3:javadoc 
failed: Cannot invoke "String.length()" because "text" is null
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
(DefaultBuildPluginManager.java:133)
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 

[jira] [Created] (MJAVADOC-793) java.lang.NullPointerException: Cannot invoke "String.length()" because "text" is null

[Gary D. Gregory (Jira)]

Gary D. Gregory created MJAVADOC-793:


 Summary: java.lang.NullPointerException: Cannot invoke 
"String.length()" because "text" is null
 Key: MJAVADOC-793
 URL: https://issues.apache.org/jira/browse/MJAVADOC-793
 Project: Maven Javadoc Plugin
  Issue Type: Bug
Affects Versions: 3.6.3
Reporter: Gary D. Gregory


Plugin throws {{NullPointerException}} when running {{{}javadoc:javadoc{}}}.

See:
 * Failing PR: https://github.com/apache/commons-compress/pull/528
 * Build log: 
[https://github.com/apache/commons-compress/actions/runs/9113449616/job/25054982405?pr=528]

Or:
 # git clone [https://gitbox.apache.org/repos/asf/commons-compress.git]
 # git checkout 542cc5a602a9128932e3fb75503383e481141e7e
 # Edit pom.xml and set the parent POM to version 70
 # Run 'mvn javadoc:javadoc' causes:

{noformat}
[INFO] --- javadoc:3.6.3:javadoc (default-cli) @ commons-compress ---
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  8.434 s
[INFO] Finished at: 2024-05-16T09:36:02-04:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.6.3:javadoc (default-cli) on 
project commons-compress: Execution default-cli of goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.6.3:javadoc failed: Cannot 
invoke "String.length()" because "text" is null -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.6.3:javadoc (default-cli) on 
project commons-compress: Execution default-cli of goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.6.3:javadoc failed: Cannot 
invoke "String.length()" because "text" is null
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
(MojoExecutor.java:333)
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.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke 
(NativeMethodAccessorImpl.java:77)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke 
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:568)
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)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
default-cli of goal org.apache.maven.plugins:maven-javadoc-plugin:3.6.3:javadoc 
failed: Cannot invoke "String.length()" because "text" is null
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
(DefaultBuildPluginManager.java:133)
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 

[jira] [Commented] (MARTIFACT-60) artifact:3.5.0:check-buildplan is too chatty by default

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MARTIFACT-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836847#comment-17836847
 ] 

Gary D. Gregory commented on MARTIFACT-60:
--

YW & TY as well  

> artifact:3.5.0:check-buildplan is too chatty by default
> ---
>
> Key: MARTIFACT-60
> URL: https://issues.apache.org/jira/browse/MARTIFACT-60
> Project: Maven Artifact Plugin
>  Issue Type: Improvement
>  Components: artifact:check-buildplan
>Affects Versions: 3.5.0, 3.5.1
> Environment: Apache Maven 3.9.6 
> (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
> Maven home: C:\java\apache-maven-3.9.6
> Java version: 17.0.8, vendor: Eclipse Adoptium, runtime: C:\Program 
> Files\Eclipse Adoptium\jdk-17.0.8.7-hotspot
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: Gary D. Gregory
>Assignee: Herve Boutemy
>Priority: Major
>  Labels: pull-request-available
> Fix For: 3.5.2
>
>
> Running the plugin is too chatty by default, for example, I don't need 
> everything that's NOT wrong. Just tell me what's wrong or nothing:
> {noformat}
> [INFO] — artifact:3.5.0:check-buildplan (check-buildplan) @ commons-io —
> [INFO] no known issue with 
> org.apache.maven.plugins:maven-enforcer-plugin:3.4.1
> [INFO] no known issue with org.apache.rat:apache-rat-plugin:0.16.1
> [INFO] no known issue with 
> org.apache.maven.plugins:maven-artifact-plugin:3.5.0
> [INFO] no known issue with org.codehaus.mojo:build-helper-maven-plugin:3.5.0
> [INFO] no known issue with org.apache.maven.plugins:maven-antrun-plugin:3.1.0
> [INFO] no known issue with 
> org.apache.maven.plugins:maven-remote-resources-plugin:3.1.0 (>= 1.7.0)
> [INFO] no known issue with org.codehaus.mojo:buildnumber-maven-plugin:3.2.0
> [INFO] no known issue with 
> org.apache.maven.plugins:maven-resources-plugin:3.3.1
> [INFO] no known issue with 
> org.apache.maven.plugins:maven-compiler-plugin:3.13.0
> [INFO] no known issue with org.apache.felix:maven-bundle-plugin:5.1.9 (>= 
> 5.1.9)
> [INFO] no known issue with org.jacoco:jacoco-maven-plugin:0.8.11
> [INFO] no known issue with 
> org.apache.maven.plugins:maven-surefire-plugin:3.2.5
> [INFO] no known issue with org.apache.maven.plugins:maven-jar-plugin:3.3.0 
> (>= 3.2.0)
> [INFO] no known issue with org.apache.maven.plugins:maven-site-plugin:3.12.1
> [INFO] no known issue with org.apache.maven.plugins:maven-source-plugin:3.2.1 
> (>= 3.2.1)
> [INFO] no known issue with org.cyclonedx:cyclonedx-maven-plugin:2.8.0
> [INFO] no known issue with org.spdx:spdx-maven-plugin:0.7.3
> [INFO] no known issue with org.moditect:moditect-maven-plugin:1.2.1.Final (>= 
> 1.0.0.Final)
> [INFO] no known issue with org.apache.maven.plugins:maven-install-plugin:3.1.1
> [INFO] no known issue with org.apache.maven.plugins:maven-deploy-plugin:3.1.1
> {noformat}
> Either say nothing or, if you must, perhaps a single log event:
> "No issues found in 16 plugins." Note that sentences should start with a 
> capital letter.
> The current info would be fine at the debug logging level IMO.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MARTIFACT-60) artifact:3.5.0:check-buildplan is too chatty by default

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MARTIFACT-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836367#comment-17836367
 ] 

Gary D. Gregory commented on MARTIFACT-60:
--

Hi All,

I propose https://github.com/apache/maven-artifact-plugin/pull/32


> artifact:3.5.0:check-buildplan is too chatty by default
> ---
>
> Key: MARTIFACT-60
> URL: https://issues.apache.org/jira/browse/MARTIFACT-60
> Project: Maven Artifact Plugin
>  Issue Type: Improvement
>  Components: artifact:check-buildplan
>Affects Versions: 3.5.0, 3.5.1
> Environment: Apache Maven 3.9.6 
> (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
> Maven home: C:\java\apache-maven-3.9.6
> Java version: 17.0.8, vendor: Eclipse Adoptium, runtime: C:\Program 
> Files\Eclipse Adoptium\jdk-17.0.8.7-hotspot
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: Gary D. Gregory
>Priority: Major
>  Labels: pull-request-available
>
> Running the plugin is too chatty by default, for example, I don't need 
> everything that's NOT wrong. Just tell me what's wrong or nothing:
> {noformat}
> [INFO] — artifact:3.5.0:check-buildplan (check-buildplan) @ commons-io —
> [INFO] no known issue with 
> org.apache.maven.plugins:maven-enforcer-plugin:3.4.1
> [INFO] no known issue with org.apache.rat:apache-rat-plugin:0.16.1
> [INFO] no known issue with 
> org.apache.maven.plugins:maven-artifact-plugin:3.5.0
> [INFO] no known issue with org.codehaus.mojo:build-helper-maven-plugin:3.5.0
> [INFO] no known issue with org.apache.maven.plugins:maven-antrun-plugin:3.1.0
> [INFO] no known issue with 
> org.apache.maven.plugins:maven-remote-resources-plugin:3.1.0 (>= 1.7.0)
> [INFO] no known issue with org.codehaus.mojo:buildnumber-maven-plugin:3.2.0
> [INFO] no known issue with 
> org.apache.maven.plugins:maven-resources-plugin:3.3.1
> [INFO] no known issue with 
> org.apache.maven.plugins:maven-compiler-plugin:3.13.0
> [INFO] no known issue with org.apache.felix:maven-bundle-plugin:5.1.9 (>= 
> 5.1.9)
> [INFO] no known issue with org.jacoco:jacoco-maven-plugin:0.8.11
> [INFO] no known issue with 
> org.apache.maven.plugins:maven-surefire-plugin:3.2.5
> [INFO] no known issue with org.apache.maven.plugins:maven-jar-plugin:3.3.0 
> (>= 3.2.0)
> [INFO] no known issue with org.apache.maven.plugins:maven-site-plugin:3.12.1
> [INFO] no known issue with org.apache.maven.plugins:maven-source-plugin:3.2.1 
> (>= 3.2.1)
> [INFO] no known issue with org.cyclonedx:cyclonedx-maven-plugin:2.8.0
> [INFO] no known issue with org.spdx:spdx-maven-plugin:0.7.3
> [INFO] no known issue with org.moditect:moditect-maven-plugin:1.2.1.Final (>= 
> 1.0.0.Final)
> [INFO] no known issue with org.apache.maven.plugins:maven-install-plugin:3.1.1
> [INFO] no known issue with org.apache.maven.plugins:maven-deploy-plugin:3.1.1
> {noformat}
> Either say nothing or, if you must, perhaps a single log event:
> "No issues found in 16 plugins." Note that sentences should start with a 
> capital letter.
> The current info would be fine at the debug logging level IMO.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MARTIFACT-60) artifact:3.5.0:check-buildplan is too chatty by default

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MARTIFACT-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833881#comment-17833881
 ] 

Gary D. Gregory commented on MARTIFACT-60:
--

For a bit of context, I think that once a project opens itself up to patches 
and PRs from the world at large, a CI should check everything, especially when 
it is inexpensive.

> artifact:3.5.0:check-buildplan is too chatty by default
> ---
>
> Key: MARTIFACT-60
> URL: https://issues.apache.org/jira/browse/MARTIFACT-60
> Project: Maven Artifact Plugin
>  Issue Type: Improvement
>  Components: artifact:check-buildplan
>Affects Versions: 3.5.0, 3.5.1
> Environment: Apache Maven 3.9.6 
> (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
> Maven home: C:\java\apache-maven-3.9.6
> Java version: 17.0.8, vendor: Eclipse Adoptium, runtime: C:\Program 
> Files\Eclipse Adoptium\jdk-17.0.8.7-hotspot
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: Gary D. Gregory
>Priority: Major
>
> Running the plugin is too chatty by default, for example, I don't need 
> everything that's NOT wrong. Just tell me what's wrong or nothing:
> {noformat}
> [INFO] — artifact:3.5.0:check-buildplan (check-buildplan) @ commons-io —
> [INFO] no known issue with 
> org.apache.maven.plugins:maven-enforcer-plugin:3.4.1
> [INFO] no known issue with org.apache.rat:apache-rat-plugin:0.16.1
> [INFO] no known issue with 
> org.apache.maven.plugins:maven-artifact-plugin:3.5.0
> [INFO] no known issue with org.codehaus.mojo:build-helper-maven-plugin:3.5.0
> [INFO] no known issue with org.apache.maven.plugins:maven-antrun-plugin:3.1.0
> [INFO] no known issue with 
> org.apache.maven.plugins:maven-remote-resources-plugin:3.1.0 (>= 1.7.0)
> [INFO] no known issue with org.codehaus.mojo:buildnumber-maven-plugin:3.2.0
> [INFO] no known issue with 
> org.apache.maven.plugins:maven-resources-plugin:3.3.1
> [INFO] no known issue with 
> org.apache.maven.plugins:maven-compiler-plugin:3.13.0
> [INFO] no known issue with org.apache.felix:maven-bundle-plugin:5.1.9 (>= 
> 5.1.9)
> [INFO] no known issue with org.jacoco:jacoco-maven-plugin:0.8.11
> [INFO] no known issue with 
> org.apache.maven.plugins:maven-surefire-plugin:3.2.5
> [INFO] no known issue with org.apache.maven.plugins:maven-jar-plugin:3.3.0 
> (>= 3.2.0)
> [INFO] no known issue with org.apache.maven.plugins:maven-site-plugin:3.12.1
> [INFO] no known issue with org.apache.maven.plugins:maven-source-plugin:3.2.1 
> (>= 3.2.1)
> [INFO] no known issue with org.cyclonedx:cyclonedx-maven-plugin:2.8.0
> [INFO] no known issue with org.spdx:spdx-maven-plugin:0.7.3
> [INFO] no known issue with org.moditect:moditect-maven-plugin:1.2.1.Final (>= 
> 1.0.0.Final)
> [INFO] no known issue with org.apache.maven.plugins:maven-install-plugin:3.1.1
> [INFO] no known issue with org.apache.maven.plugins:maven-deploy-plugin:3.1.1
> {noformat}
> Either say nothing or, if you must, perhaps a single log event:
> "No issues found in 16 plugins." Note that sentences should start with a 
> capital letter.
> The current info would be fine at the debug logging level IMO.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MPMD-379) Support PMD 7.0.0

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MPMD-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833601#comment-17833601
 ] 

Gary D. Gregory commented on MPMD-379:
--

Any release plans you can share?

 

> Support PMD 7.0.0
> -
>
> Key: MPMD-379
> URL: https://issues.apache.org/jira/browse/MPMD-379
> Project: Maven PMD Plugin
>  Issue Type: Improvement
>  Components: CPD, PMD
>Reporter: Andreas Dangel
>Assignee: Andreas Dangel
>Priority: Major
>
> Add support for the new major version of PMD.
> This has some non-backward compatible changes. Upgrading m-pmd-p to PMD 7 
> most likely means, that only PMD 7 will be supported onwards (no backwards 
> compatibility supported).
> wip branch: [https://github.com/apache/maven-pmd-plugin/compare/master...pmd7]
>  
> A snapshot version that is compatible with the current 7.0.0 release 
> candidates is available here as version {*}3.21.1-pmd-7-SNAPSHOT{*}:
> {code:java}
> 
> apache.snapshots
> Apache Snapshot Repository
> https://repository.apache.org/snapshots
> 
> false
> 
> 
> true
> 
>  {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (MARTIFACT-60) artifact:3.5.0:check-buildplan is too chatty by default

[Gary D. Gregory (Jira)]

 [ 
https://issues.apache.org/jira/browse/MARTIFACT-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gary D. Gregory updated MARTIFACT-60:
-
Description: 
Running the plugin is too chatty by default, for example, I don't need 
everything that's NOT wrong. Just tell me what's wrong or nothing:
{noformat}
[INFO] — artifact:3.5.0:check-buildplan (check-buildplan) @ commons-io —
[INFO] no known issue with org.apache.maven.plugins:maven-enforcer-plugin:3.4.1
[INFO] no known issue with org.apache.rat:apache-rat-plugin:0.16.1
[INFO] no known issue with org.apache.maven.plugins:maven-artifact-plugin:3.5.0
[INFO] no known issue with org.codehaus.mojo:build-helper-maven-plugin:3.5.0
[INFO] no known issue with org.apache.maven.plugins:maven-antrun-plugin:3.1.0
[INFO] no known issue with 
org.apache.maven.plugins:maven-remote-resources-plugin:3.1.0 (>= 1.7.0)
[INFO] no known issue with org.codehaus.mojo:buildnumber-maven-plugin:3.2.0
[INFO] no known issue with org.apache.maven.plugins:maven-resources-plugin:3.3.1
[INFO] no known issue with org.apache.maven.plugins:maven-compiler-plugin:3.13.0
[INFO] no known issue with org.apache.felix:maven-bundle-plugin:5.1.9 (>= 5.1.9)
[INFO] no known issue with org.jacoco:jacoco-maven-plugin:0.8.11
[INFO] no known issue with org.apache.maven.plugins:maven-surefire-plugin:3.2.5
[INFO] no known issue with org.apache.maven.plugins:maven-jar-plugin:3.3.0 (>= 
3.2.0)
[INFO] no known issue with org.apache.maven.plugins:maven-site-plugin:3.12.1
[INFO] no known issue with org.apache.maven.plugins:maven-source-plugin:3.2.1 
(>= 3.2.1)
[INFO] no known issue with org.cyclonedx:cyclonedx-maven-plugin:2.8.0
[INFO] no known issue with org.spdx:spdx-maven-plugin:0.7.3
[INFO] no known issue with org.moditect:moditect-maven-plugin:1.2.1.Final (>= 
1.0.0.Final)
[INFO] no known issue with org.apache.maven.plugins:maven-install-plugin:3.1.1
[INFO] no known issue with org.apache.maven.plugins:maven-deploy-plugin:3.1.1
{noformat}
Either say nothing or, if you must, perhaps a single log event:
"No issues found in 16 plugins." Note that sentences should start with a 
capital letter.

The current info would be fine at the debug logging level IMO.

  was:
Running the plugin is too chatty by default, for example, I don't need 
everything that's NOT wrong. Just tell me what's wrong or nothing:
{noformat}
[INFO] — artifact:3.5.0:check-buildplan (check-buildplan) @ commons-io —
[INFO] no known issue with org.apache.maven.plugins:maven-enforcer-plugin:3.4.1
[INFO] no known issue with org.apache.rat:apache-rat-plugin:0.16.1
[INFO] no known issue with org.apache.maven.plugins:maven-artifact-plugin:3.5.0
[INFO] no known issue with org.codehaus.mojo:build-helper-maven-plugin:3.5.0
[INFO] no known issue with org.apache.maven.plugins:maven-antrun-plugin:3.1.0
[INFO] no known issue with 
org.apache.maven.plugins:maven-remote-resources-plugin:3.1.0 (>= 1.7.0)
[INFO] no known issue with org.codehaus.mojo:buildnumber-maven-plugin:3.2.0
[INFO] no known issue with org.apache.maven.plugins:maven-resources-plugin:3.3.1
[INFO] no known issue with org.apache.maven.plugins:maven-compiler-plugin:3.13.0
[INFO] no known issue with org.apache.felix:maven-bundle-plugin:5.1.9 (>= 5.1.9)
[INFO] no known issue with org.jacoco:jacoco-maven-plugin:0.8.11
[INFO] no known issue with org.apache.maven.plugins:maven-surefire-plugin:3.2.5
[INFO] no known issue with org.apache.maven.plugins:maven-jar-plugin:3.3.0 (>= 
3.2.0)
[INFO] no known issue with org.apache.maven.plugins:maven-site-plugin:3.12.1
[INFO] no known issue with org.apache.maven.plugins:maven-source-plugin:3.2.1 
(>= 3.2.1)
[INFO] no known issue with org.cyclonedx:cyclonedx-maven-plugin:2.8.0
[INFO] no known issue with org.spdx:spdx-maven-plugin:0.7.3
[INFO] no known issue with org.moditect:moditect-maven-plugin:1.2.1.Final (>= 
1.0.0.Final)
[INFO] no known issue with org.apache.maven.plugins:maven-install-plugin:3.1.1
[INFO] no known issue with org.apache.maven.plugins:maven-deploy-plugin:3.1.1
{noformat}
Either say nothing or, if you must, perhaps a single log event:
"No issues found in 16 plugins." Note that sentences should start with a 
capital letter

The current info would be fine at the debug logging level IMO.


> artifact:3.5.0:check-buildplan is too chatty by default
> ---
>
> Key: MARTIFACT-60
> URL: https://issues.apache.org/jira/browse/MARTIFACT-60
> Project: Maven Artifact Plugin
>  Issue Type: Improvement
>  Components: artifact:check-buildplan
>Affects Versions: 3.5.0
> Environment: Apache Maven 3.9.6 
> (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
> Maven home: C:\java\apache-maven-3.9.6
> Java version: 17.0.8, vendor: Eclipse Adoptium, runtime: C:\Program 
> Files\Eclipse Adoptium\jdk-17.0.8.7-hotspot
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 

[jira] [Created] (MARTIFACT-60) artifact:3.5.0:check-buildplan is too chatty by default

[Gary D. Gregory (Jira)]

Gary D. Gregory created MARTIFACT-60:


 Summary: artifact:3.5.0:check-buildplan is too chatty by default
 Key: MARTIFACT-60
 URL: https://issues.apache.org/jira/browse/MARTIFACT-60
 Project: Maven Artifact Plugin
  Issue Type: Improvement
  Components: artifact:check-buildplan
Affects Versions: 3.5.0
 Environment: Apache Maven 3.9.6 
(bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Maven home: C:\java\apache-maven-3.9.6
Java version: 17.0.8, vendor: Eclipse Adoptium, runtime: C:\Program 
Files\Eclipse Adoptium\jdk-17.0.8.7-hotspot
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

Reporter: Gary D. Gregory


Running the plugin is too chatty by default, for example, I don't need 
everything that's NOT wrong. Just tell me what's wrong or nothing:
{noformat}
[INFO] — artifact:3.5.0:check-buildplan (check-buildplan) @ commons-io —
[INFO] no known issue with org.apache.maven.plugins:maven-enforcer-plugin:3.4.1
[INFO] no known issue with org.apache.rat:apache-rat-plugin:0.16.1
[INFO] no known issue with org.apache.maven.plugins:maven-artifact-plugin:3.5.0
[INFO] no known issue with org.codehaus.mojo:build-helper-maven-plugin:3.5.0
[INFO] no known issue with org.apache.maven.plugins:maven-antrun-plugin:3.1.0
[INFO] no known issue with 
org.apache.maven.plugins:maven-remote-resources-plugin:3.1.0 (>= 1.7.0)
[INFO] no known issue with org.codehaus.mojo:buildnumber-maven-plugin:3.2.0
[INFO] no known issue with org.apache.maven.plugins:maven-resources-plugin:3.3.1
[INFO] no known issue with org.apache.maven.plugins:maven-compiler-plugin:3.13.0
[INFO] no known issue with org.apache.felix:maven-bundle-plugin:5.1.9 (>= 5.1.9)
[INFO] no known issue with org.jacoco:jacoco-maven-plugin:0.8.11
[INFO] no known issue with org.apache.maven.plugins:maven-surefire-plugin:3.2.5
[INFO] no known issue with org.apache.maven.plugins:maven-jar-plugin:3.3.0 (>= 
3.2.0)
[INFO] no known issue with org.apache.maven.plugins:maven-site-plugin:3.12.1
[INFO] no known issue with org.apache.maven.plugins:maven-source-plugin:3.2.1 
(>= 3.2.1)
[INFO] no known issue with org.cyclonedx:cyclonedx-maven-plugin:2.8.0
[INFO] no known issue with org.spdx:spdx-maven-plugin:0.7.3
[INFO] no known issue with org.moditect:moditect-maven-plugin:1.2.1.Final (>= 
1.0.0.Final)
[INFO] no known issue with org.apache.maven.plugins:maven-install-plugin:3.1.1
[INFO] no known issue with org.apache.maven.plugins:maven-deploy-plugin:3.1.1
{noformat}
Either say nothing or, if you must, perhaps a single log event:
"No issues found in 16 plugins." Note that sentences should start with a 
capital letter

The current info would be fine at the debug logging level IMO.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MSOURCES-143) Can't create a source and test jar in Commons using commons-parent

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MSOURCES-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17804739#comment-17804739
 ] 

Gary D. Gregory commented on MSOURCES-143:
--

Hi [~romain.manni-bucau] 

I gave up on debugging this (as noted above) and set the plug in version to 
3.2.1.

I suppose one day we'll be forced to upgrade or someone will figure it out.

> Can't create a source and test jar in Commons using commons-parent
> --
>
> Key: MSOURCES-143
> URL: https://issues.apache.org/jira/browse/MSOURCES-143
> Project: Maven Source Plugin
>  Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Gary D. Gregory
>Priority: Major
>
> Steps to reproduce:
> # git clone https://gitbox.apache.org/repos/asf/commons-parent.git
> # cd commons-parent
> # git checkout 8d886ce8382f7a79f06d51a3afc386b8a37d0473
> # mvn clean install
> # cd ..
> # git clone https://gitbox.apache.org/repos/asf/commons-cli.git
> # cd commons-cli
> # git checkout 08f8c5034a8492be6db65b2086341c292489ee53
> # mvn clean package
> [INFO] --- source:3.3.0:jar-no-fork (create-source-jar) @ commons-cli ---
> [ERROR] We have duplicated artifacts attached.
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  15.233 s
> [INFO] Finished at: 2023-08-15T15:39:45-04:00
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-source-plugin:3.3.0:jar-no-fork 
> (create-source-jar) on project commons-cli: Presumably you have configured 
> maven-source-plugn to execute twice times in your build. You have to 
> configure a classifier for at least on of them. -> [Help 1]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MSOURCES-143) Can't create a source and test jar in Commons using commons-parent

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MSOURCES-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17804705#comment-17804705
 ] 

Gary D. Gregory commented on MSOURCES-143:
--

But my (poor) understanding of this in the commons-parent case is that this is 
NOT a bug in MY project, but a bug in the SPDX plug in? Or am I reading this 
wrong? The bottom line is that it's near impossible to figure out and much less 
clear to fix.

> Can't create a source and test jar in Commons using commons-parent
> --
>
> Key: MSOURCES-143
> URL: https://issues.apache.org/jira/browse/MSOURCES-143
> Project: Maven Source Plugin
>  Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Gary D. Gregory
>Priority: Major
>
> Steps to reproduce:
> # git clone https://gitbox.apache.org/repos/asf/commons-parent.git
> # cd commons-parent
> # git checkout 8d886ce8382f7a79f06d51a3afc386b8a37d0473
> # mvn clean install
> # cd ..
> # git clone https://gitbox.apache.org/repos/asf/commons-cli.git
> # cd commons-cli
> # git checkout 08f8c5034a8492be6db65b2086341c292489ee53
> # mvn clean package
> [INFO] --- source:3.3.0:jar-no-fork (create-source-jar) @ commons-cli ---
> [ERROR] We have duplicated artifacts attached.
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  15.233 s
> [INFO] Finished at: 2023-08-15T15:39:45-04:00
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-source-plugin:3.3.0:jar-no-fork 
> (create-source-jar) on project commons-cli: Presumably you have configured 
> maven-source-plugn to execute twice times in your build. You have to 
> configure a classifier for at least on of them. -> [Help 1]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MSHADE-462) 3.5.1 not compatible with 3.4.1: The version cannot be empty

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MSHADE-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17803820#comment-17803820
 ] 

Gary D. Gregory commented on MSHADE-462:


TY [~crazyhzm] !

Would someone on the MSHADE team please take a look SVP?

> 3.5.1 not compatible with 3.4.1: The version cannot be empty
> 
>
> Key: MSHADE-462
> URL: https://issues.apache.org/jira/browse/MSHADE-462
> Project: Maven Shade Plugin
>  Issue Type: Bug
>Affects Versions: 3.5.1
> Environment:  Apache Maven 3.8.8 
> (4c87b05d9aedce574290d1acc98575ed5eb6cd39)
> Maven home: /usr/share/apache-maven-3.8.8
> Java version: 17.0.9, vendor: Eclipse Adoptium, runtime: 
> /usr/lib/jvm/temurin-17-jdk-amd64
> Default locale: en, platform encoding: UTF-8
> OS name: "linux", version: "6.2.0-1018-azure", arch: "amd64", family: "unix"
>Reporter: Gary D. Gregory
>Priority: Major
>
> When updating Apache Juneau git master from 3.4.1 to 3.5.1, we get:
> {noformat}
> Error:  Failed to execute goal 
> org.apache.maven.plugins:maven-shade-plugin:3.5.1:shade (source-jar) on 
> project juneau-all: Execution source-jar of goal 
> org.apache.maven.plugins:maven-shade-plugin:3.5.1:shade failed: For artifact 
> {org.apache.juneau:juneau-marshall:null:jar}: The version cannot be empty. -> 
> [Help 1]
> {noformat}
> See the build failure in the PR https://github.com/apache/juneau/pull/125
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (MCHANGES-420) Don't dump a stack trace for a simple warning like "Couldn't find any issues for the version '1.25.1' among the supplied issues: []"

[Gary D. Gregory (Jira)]

Gary D. Gregory created MCHANGES-420:


 Summary: Don't dump a stack trace for a simple warning like 
"Couldn't find any issues for the version '1.25.1' among the supplied issues: 
[]"
 Key: MCHANGES-420
 URL: https://issues.apache.org/jira/browse/MCHANGES-420
 Project: Maven Changes Plugin
  Issue Type: Bug
 Environment: Apache Maven 3.9.6 
(bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Maven home: /usr/local/Cellar/maven/3.9.6/libexec
Java version: 21.0.1, vendor: Homebrew, runtime: 
/usr/local/Cellar/openjdk/21.0.1/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "14.2", arch: "x86_64", family: "mac"
Darwin  23.2.0 Darwin Kernel Version 23.2.0: Wed Nov 15 21:54:10 PST 2023; 
root:xnu-10002.61.3~2/RELEASE_X86_64 x86_64
Reporter: Gary D. Gregory


It feels totally over the top to dump a stack trace for a simple normal warning 
like "Couldn't find any issues for the version '1.25.1' among the supplied 
issues: []"
Currently, there a no issues stamped with that version in Apache Commons 
Compress, which is fine.
{noformat}
[INFO] Generating "JIRA Report" report   --- 
maven-changes-plugin:2.12.1:jira-report
[WARNING]
org.apache.maven.plugin.MojoExecutionException: Couldn't find any issues for 
the version '1.25.1' among the supplied issues: []
at org.apache.maven.plugin.issues.IssueUtils.getIssuesForVersion 
(IssueUtils.java:116)
at org.apache.maven.plugin.jira.JiraMojo.executeReport (JiraMojo.java:361)
at org.apache.maven.reporting.AbstractMavenReport.generate 
(AbstractMavenReport.java:255)
at 
org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument 
(ReportDocumentRenderer.java:226)
at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render 
(DefaultSiteRenderer.java:348)
at org.apache.maven.plugins.site.render.SiteMojo.renderLocale 
(SiteMojo.java:194)
at org.apache.maven.plugins.site.render.SiteMojo.execute (SiteMojo.java:143)
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)
{noformat}




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (MSHADE-462) 3.5.1 not compatible with 3.4.1: The version cannot be empty

[Gary D. Gregory (Jira)]

Gary D. Gregory created MSHADE-462:
--

 Summary: 3.5.1 not compatible with 3.4.1: The version cannot be 
empty
 Key: MSHADE-462
 URL: https://issues.apache.org/jira/browse/MSHADE-462
 Project: Maven Shade Plugin
  Issue Type: Bug
Affects Versions: 3.5.1
 Environment:  Apache Maven 3.8.8 
(4c87b05d9aedce574290d1acc98575ed5eb6cd39)
Maven home: /usr/share/apache-maven-3.8.8
Java version: 17.0.9, vendor: Eclipse Adoptium, runtime: 
/usr/lib/jvm/temurin-17-jdk-amd64
Default locale: en, platform encoding: UTF-8
OS name: "linux", version: "6.2.0-1018-azure", arch: "amd64", family: "unix"

Reporter: Gary D. Gregory


When updating Apache Juneau git master from 3.4.1 to 3.5.1, we get:
{noformat}
Error:  Failed to execute goal 
org.apache.maven.plugins:maven-shade-plugin:3.5.1:shade (source-jar) on project 
juneau-all: Execution source-jar of goal 
org.apache.maven.plugins:maven-shade-plugin:3.5.1:shade failed: For artifact 
{org.apache.juneau:juneau-marshall:null:jar}: The version cannot be empty. -> 
[Help 1]
{noformat}
See the build failure in the PR https://github.com/apache/juneau/pull/125


 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Comment Edited] (MSOURCES-143) Can't create a source and test jar in Commons using commons-parent

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MSOURCES-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755948#comment-17755948
 ] 

Gary D. Gregory edited comment on MSOURCES-143 at 9/6/23 11:15 AM:
---

I've decided to save time today so am I forcing {{commons-parent}} to use 
{{version.maven-source-plugin}} 3.2.1 -on Java 8-.

Thank you all for your time.

 


was (Author: garydgregory):
I've decided to save time today so am I forcing {{commons-parent}} to use 
{{version.maven-source-plugin}} 3.2.1 on Java 8.

Thank you all for your time.

 

> Can't create a source and test jar in Commons using commons-parent
> --
>
> Key: MSOURCES-143
> URL: https://issues.apache.org/jira/browse/MSOURCES-143
> Project: Maven Source Plugin
>  Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Gary D. Gregory
>Priority: Major
>
> Steps to reproduce:
> # git clone https://gitbox.apache.org/repos/asf/commons-parent.git
> # cd commons-parent
> # git checkout 8d886ce8382f7a79f06d51a3afc386b8a37d0473
> # mvn clean install
> # cd ..
> # git clone https://gitbox.apache.org/repos/asf/commons-cli.git
> # cd commons-cli
> # git checkout 08f8c5034a8492be6db65b2086341c292489ee53
> # mvn clean package
> [INFO] --- source:3.3.0:jar-no-fork (create-source-jar) @ commons-cli ---
> [ERROR] We have duplicated artifacts attached.
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  15.233 s
> [INFO] Finished at: 2023-08-15T15:39:45-04:00
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-source-plugin:3.3.0:jar-no-fork 
> (create-source-jar) on project commons-cli: Presumably you have configured 
> maven-source-plugn to execute twice times in your build. You have to 
> configure a classifier for at least on of them. -> [Help 1]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MSOURCES-143) Can't create a source and test jar in Commons using commons-parent

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MSOURCES-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17762347#comment-17762347
 ] 

Gary D. Gregory commented on MSOURCES-143:
--

I except we'll see the above over and over :-( 
https://lists.apache.org/thread/3yb9cnq84nl94q2j3fqmdrzslc01g1zw

> Can't create a source and test jar in Commons using commons-parent
> --
>
> Key: MSOURCES-143
> URL: https://issues.apache.org/jira/browse/MSOURCES-143
> Project: Maven Source Plugin
>  Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Gary D. Gregory
>Priority: Major
>
> Steps to reproduce:
> # git clone https://gitbox.apache.org/repos/asf/commons-parent.git
> # cd commons-parent
> # git checkout 8d886ce8382f7a79f06d51a3afc386b8a37d0473
> # mvn clean install
> # cd ..
> # git clone https://gitbox.apache.org/repos/asf/commons-cli.git
> # cd commons-cli
> # git checkout 08f8c5034a8492be6db65b2086341c292489ee53
> # mvn clean package
> [INFO] --- source:3.3.0:jar-no-fork (create-source-jar) @ commons-cli ---
> [ERROR] We have duplicated artifacts attached.
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  15.233 s
> [INFO] Finished at: 2023-08-15T15:39:45-04:00
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-source-plugin:3.3.0:jar-no-fork 
> (create-source-jar) on project commons-cli: Presumably you have configured 
> maven-source-plugn to execute twice times in your build. You have to 
> configure a classifier for at least on of them. -> [Help 1]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MSOURCES-143) Can't create a source and test jar in Commons using commons-parent

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MSOURCES-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755948#comment-17755948
 ] 

Gary D. Gregory commented on MSOURCES-143:
--

I've decided to save time today so am I forcing {{commons-parent}} to use 
{{version.maven-source-plugin}} 3.2.1 on Java 8.

Thank you all for your time.

 

> Can't create a source and test jar in Commons using commons-parent
> --
>
> Key: MSOURCES-143
> URL: https://issues.apache.org/jira/browse/MSOURCES-143
> Project: Maven Source Plugin
>  Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Gary D. Gregory
>Priority: Major
>
> Steps to reproduce:
> # git clone https://gitbox.apache.org/repos/asf/commons-parent.git
> # cd commons-parent
> # git checkout 8d886ce8382f7a79f06d51a3afc386b8a37d0473
> # mvn clean install
> # cd ..
> # git clone https://gitbox.apache.org/repos/asf/commons-cli.git
> # cd commons-cli
> # git checkout 08f8c5034a8492be6db65b2086341c292489ee53
> # mvn clean package
> [INFO] --- source:3.3.0:jar-no-fork (create-source-jar) @ commons-cli ---
> [ERROR] We have duplicated artifacts attached.
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  15.233 s
> [INFO] Finished at: 2023-08-15T15:39:45-04:00
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-source-plugin:3.3.0:jar-no-fork 
> (create-source-jar) on project commons-cli: Presumably you have configured 
> maven-source-plugn to execute twice times in your build. You have to 
> configure a classifier for at least on of them. -> [Help 1]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MSOURCES-143) Can't create a source and test jar in Commons using commons-parent

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MSOURCES-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755661#comment-17755661
 ] 

Gary D. Gregory commented on MSOURCES-143:
--

Hi [~sjaranowski] 

I am sorry but I still don't get it. What does the SPDX plugin's PR (removing 
something that happens at verify?) have to do with creating source and test 
source jars? I just want to build source jars and I don't need to understand 
what SPDX does beyond creating it's own custom files. Are you saying that SPDX, 
as part of it's own execution, causes the source and test source jars to be 
generated, and that's indeed the issue?

Hi [~romain.manni-bucau] 

"whatever will make the error case no more hit avoiding rebuild of the same mvn 
mojo execution"

So do whatever fixes the problem? Great advice. Sorry for being sarcastic but 
this is the level of Maven Magic that I find frustrating.

I not sure if what I am trying to do is unusual or a stretch or what, but I'm 
looking for specific help on what to do here.

> Can't create a source and test jar in Commons using commons-parent
> --
>
> Key: MSOURCES-143
> URL: https://issues.apache.org/jira/browse/MSOURCES-143
> Project: Maven Source Plugin
>  Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Gary D. Gregory
>Priority: Major
>
> Steps to reproduce:
> # git clone https://gitbox.apache.org/repos/asf/commons-parent.git
> # cd commons-parent
> # git checkout 8d886ce8382f7a79f06d51a3afc386b8a37d0473
> # mvn clean install
> # cd ..
> # git clone https://gitbox.apache.org/repos/asf/commons-cli.git
> # cd commons-cli
> # git checkout 08f8c5034a8492be6db65b2086341c292489ee53
> # mvn clean package
> [INFO] --- source:3.3.0:jar-no-fork (create-source-jar) @ commons-cli ---
> [ERROR] We have duplicated artifacts attached.
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  15.233 s
> [INFO] Finished at: 2023-08-15T15:39:45-04:00
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-source-plugin:3.3.0:jar-no-fork 
> (create-source-jar) on project commons-cli: Presumably you have configured 
> maven-source-plugn to execute twice times in your build. You have to 
> configure a classifier for at least on of them. -> [Help 1]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MSOURCES-143) Can't create a source and test jar in Commons using commons-parent

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MSOURCES-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755616#comment-17755616
 ] 

Gary D. Gregory commented on MSOURCES-143:
--

I'm not sure what you are asking me or telling me. Where should this be 
addressed?

> Can't create a source and test jar in Commons using commons-parent
> --
>
> Key: MSOURCES-143
> URL: https://issues.apache.org/jira/browse/MSOURCES-143
> Project: Maven Source Plugin
>  Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Gary D. Gregory
>Priority: Major
>
> Steps to reproduce:
> # git clone https://gitbox.apache.org/repos/asf/commons-parent.git
> # cd commons-parent
> # git checkout 8d886ce8382f7a79f06d51a3afc386b8a37d0473
> # mvn clean install
> # cd ..
> # git clone https://gitbox.apache.org/repos/asf/commons-cli.git
> # cd commons-cli
> # git checkout 08f8c5034a8492be6db65b2086341c292489ee53
> # mvn clean package
> [INFO] --- source:3.3.0:jar-no-fork (create-source-jar) @ commons-cli ---
> [ERROR] We have duplicated artifacts attached.
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  15.233 s
> [INFO] Finished at: 2023-08-15T15:39:45-04:00
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-source-plugin:3.3.0:jar-no-fork 
> (create-source-jar) on project commons-cli: Presumably you have configured 
> maven-source-plugn to execute twice times in your build. You have to 
> configure a classifier for at least on of them. -> [Help 1]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Comment Edited] (MSOURCES-143) Can't create a source and test jar in Commons using commons-parent

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MSOURCES-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755330#comment-17755330
 ] 

Gary D. Gregory edited comment on MSOURCES-143 at 8/17/23 2:45 AM:
---

Here is my console output (using MAVEN_ARGS=-V) BUT
 * I tried Java 17, it worked, then
 * I tried Java 11, it worked, then
 * I tried Java 8, it failed:

{noformat}
mvn clean package
Apache Maven 3.9.3 (21122926829f1ead511c958d89bd2f672198ae9f)
Maven home: C:\java\apache-maven-3.9.3
Java version: 1.8.0_382, vendor: Temurin, runtime: C:\Program Files\Eclipse 
Adoptium\jdk-8.0.382.5-hotspot\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
[INFO] Scanning for projects...
[INFO]
[INFO] --< commons-cli:commons-cli >---
[INFO] Building Apache Commons CLI 1.6.0-SNAPSHOT
[INFO]   from pom.xml
[INFO] [ jar ]-
[INFO]
[INFO] --- clean:3.2.0:clean (default-clean) @ commons-cli ---
[INFO] Deleting C:\Users\ggregory\git\a\commons-cli\target
[INFO]
[INFO] --- enforcer:3.3.0:enforce (enforce-maven-version) @ commons-cli ---
[INFO] Rule 0: org.apache.maven.enforcer.rules.version.RequireMavenVersion 
passed
[INFO] Rule 1: org.apache.maven.enforcer.rules.version.RequireJavaVersion passed
[INFO]
[INFO] --- enforcer:3.3.0:enforce (enforce-java-version) @ commons-cli ---
[INFO]
[INFO] --- enforcer:3.3.0:enforce (enforce-maven-3) @ commons-cli ---
[INFO]
[INFO] --- apache-rat:0.15:check (rat-check) @ commons-cli ---
[INFO] Enabled default license matchers.
[INFO] Will parse SCM ignores for exclusions...
[INFO] Parsing exclusions from C:\Users\ggregory\git\a\commons-cli\.gitignore
[INFO] Finished adding exclusions from SCM ignore files.
[INFO] 76 implicit excludes.
[INFO] 13 explicit excludes.
[INFO] 100 resources included
[INFO] Rat check: Summary over all files. Unapproved: 0, unknown: 0, generated: 
0, approved: 93 licenses.
[INFO]
[INFO] --- build-helper:3.4.0:parse-version (parse-version) @ commons-cli ---
[INFO]
[INFO] --- antrun:3.1.0:run (javadoc.resources) @ commons-cli ---
[INFO] Executing tasks
[INFO]  [copy] Copying 2 files to 
C:\Users\ggregory\git\a\commons-cli\target\apidocs\META-INF
[INFO] Executed tasks
[INFO]
[INFO] --- remote-resources:3.1.0:process (process-resource-bundles) @ 
commons-cli ---
[INFO] Skipping remote resources execution.
[INFO]
[INFO] --- buildnumber:3.2.0:create (default) @ commons-cli ---
[INFO] Executing: cmd.exe /X /C "git rev-parse --verify HEAD"
[INFO] Working directory: C:\Users\ggregory\git\a\commons-cli
[INFO] Storing buildNumber: null at timestamp: 1692239650046
[INFO] Executing: cmd.exe /X /C "git symbolic-ref HEAD"
[INFO] Working directory: C:\Users\ggregory\git\a\commons-cli
[INFO] Storing scmBranch: master
[INFO]
[INFO] --- resources:3.3.1:resources (default-resources) @ commons-cli ---
[INFO] skip non existing resourceDirectory 
C:\Users\ggregory\git\a\commons-cli\src\main\resources
[INFO] Copying 2 resources from  to target\classes\META-INF
[INFO]
[INFO] --- compiler:3.11.0:compile (default-compile) @ commons-cli ---
[INFO] Changes detected - recompiling the module! :source
[INFO] Compiling 23 source files with javac [debug target 1.8] to target\classes
[INFO] 
/C:/Users/ggregory/git/a/commons-cli/src/main/java/org/apache/commons/cli/Parser.java:
 Some input files use unchecked or unsafe operations.
[INFO] 
/C:/Users/ggregory/git/a/commons-cli/src/main/java/org/apache/commons/cli/Parser.java:
 Recompile with -Xlint:unchecked for details.
[INFO]
[INFO] --- bundle:5.1.9:manifest (bundle-manifest) @ commons-cli ---
[INFO] No MANIFEST.MF file found, generating manifest.
[INFO] Writing manifest: 
C:\Users\ggregory\git\a\commons-cli\target\osgi\MANIFEST.MF
[INFO]
[INFO] --- resources:3.3.1:testResources (default-testResources) @ commons-cli 
---
[INFO] Copying 1 resource from src\test\resources to target\test-classes
[INFO] Copying 2 resources from  to target\test-classes\META-INF
[INFO]
[INFO] --- compiler:3.11.0:testCompile (default-testCompile) @ commons-cli ---
[INFO] Changes detected - recompiling the module! :dependency
[INFO] Compiling 29 source files with javac [debug target 1.8] to 
target\test-classes
[INFO] 
/C:/Users/ggregory/git/a/commons-cli/src/test/java/org/apache/commons/cli/bug/BugCLI148Test.java:
 Some input files use or override a deprecated API.
[INFO] 
/C:/Users/ggregory/git/a/commons-cli/src/test/java/org/apache/commons/cli/bug/BugCLI148Test.java:
 Recompile with -Xlint:deprecation for details.
[INFO]
[INFO] --- animal-sniffer:1.23:check (checkAPIcompatibility) @ commons-cli ---
[INFO] Checking unresolved references to org.codehaus.mojo.signature:java18:1.0
[INFO]
[INFO] --- jacoco:0.8.10:prepare-agent (prepare-agent) @ commons-cli ---
[INFO] argLine set to 

[jira] [Comment Edited] (MSOURCES-143) Can't create a source and test jar in Commons using commons-parent

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MSOURCES-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755330#comment-17755330
 ] 

Gary D. Gregory edited comment on MSOURCES-143 at 8/17/23 2:45 AM:
---

Here is my console output (using MAVEN_ARGS=-V) BUT
 * I tried Java 17, it worked, then
 * I tried Java 11, it worked, then
 * I tried Java 8, it failed:

{noformat}
mvn clean package
Apache Maven 3.9.3 (21122926829f1ead511c958d89bd2f672198ae9f)
Maven home: C:\java\apache-maven-3.9.3
Java version: 1.8.0_382, vendor: Temurin, runtime: C:\Program Files\Eclipse 
Adoptium\jdk-8.0.382.5-hotspot\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
[INFO] Scanning for projects...
[INFO]
[INFO] --< commons-cli:commons-cli >---
[INFO] Building Apache Commons CLI 1.6.0-SNAPSHOT
[INFO]   from pom.xml
[INFO] [ jar ]-
[INFO]
[INFO] --- clean:3.2.0:clean (default-clean) @ commons-cli ---
[INFO] Deleting C:\Users\ggregory\git\a\commons-cli\target
[INFO]
[INFO] --- enforcer:3.3.0:enforce (enforce-maven-version) @ commons-cli ---
[INFO] Rule 0: org.apache.maven.enforcer.rules.version.RequireMavenVersion 
passed
[INFO] Rule 1: org.apache.maven.enforcer.rules.version.RequireJavaVersion passed
[INFO]
[INFO] --- enforcer:3.3.0:enforce (enforce-java-version) @ commons-cli ---
[INFO]
[INFO] --- enforcer:3.3.0:enforce (enforce-maven-3) @ commons-cli ---
[INFO]
[INFO] --- apache-rat:0.15:check (rat-check) @ commons-cli ---
[INFO] Enabled default license matchers.
[INFO] Will parse SCM ignores for exclusions...
[INFO] Parsing exclusions from C:\Users\ggregory\git\a\commons-cli\.gitignore
[INFO] Finished adding exclusions from SCM ignore files.
[INFO] 76 implicit excludes.
[INFO] 13 explicit excludes.
[INFO] 100 resources included
[INFO] Rat check: Summary over all files. Unapproved: 0, unknown: 0, generated: 
0, approved: 93 licenses.
[INFO]
[INFO] --- build-helper:3.4.0:parse-version (parse-version) @ commons-cli ---
[INFO]
[INFO] --- antrun:3.1.0:run (javadoc.resources) @ commons-cli ---
[INFO] Executing tasks
[INFO]  [copy] Copying 2 files to 
C:\Users\ggregory\git\a\commons-cli\target\apidocs\META-INF
[INFO] Executed tasks
[INFO]
[INFO] --- remote-resources:3.1.0:process (process-resource-bundles) @ 
commons-cli ---
[INFO] Skipping remote resources execution.
[INFO]
[INFO] --- buildnumber:3.2.0:create (default) @ commons-cli ---
[INFO] Executing: cmd.exe /X /C "git rev-parse --verify HEAD"
[INFO] Working directory: C:\Users\ggregory\git\a\commons-cli
[INFO] Storing buildNumber: null at timestamp: 1692239650046
[INFO] Executing: cmd.exe /X /C "git symbolic-ref HEAD"
[INFO] Working directory: C:\Users\ggregory\git\a\commons-cli
[INFO] Storing scmBranch: master
[INFO]
[INFO] --- resources:3.3.1:resources (default-resources) @ commons-cli ---
[INFO] skip non existing resourceDirectory 
C:\Users\ggregory\git\a\commons-cli\src\main\resources
[INFO] Copying 2 resources from  to target\classes\META-INF
[INFO]
[INFO] --- compiler:3.11.0:compile (default-compile) @ commons-cli ---
[INFO] Changes detected - recompiling the module! :source
[INFO] Compiling 23 source files with javac [debug target 1.8] to target\classes
[INFO] 
/C:/Users/ggregory/git/a/commons-cli/src/main/java/org/apache/commons/cli/Parser.java:
 Some input files use unchecked or unsafe operations.
[INFO] 
/C:/Users/ggregory/git/a/commons-cli/src/main/java/org/apache/commons/cli/Parser.java:
 Recompile with -Xlint:unchecked for details.
[INFO]
[INFO] --- bundle:5.1.9:manifest (bundle-manifest) @ commons-cli ---
[INFO] No MANIFEST.MF file found, generating manifest.
[INFO] Writing manifest: 
C:\Users\ggregory\git\a\commons-cli\target\osgi\MANIFEST.MF
[INFO]
[INFO] --- resources:3.3.1:testResources (default-testResources) @ commons-cli 
---
[INFO] Copying 1 resource from src\test\resources to target\test-classes
[INFO] Copying 2 resources from  to target\test-classes\META-INF
[INFO]
[INFO] --- compiler:3.11.0:testCompile (default-testCompile) @ commons-cli ---
[INFO] Changes detected - recompiling the module! :dependency
[INFO] Compiling 29 source files with javac [debug target 1.8] to 
target\test-classes
[INFO] 
/C:/Users/ggregory/git/a/commons-cli/src/test/java/org/apache/commons/cli/bug/BugCLI148Test.java:
 Some input files use or override a deprecated API.
[INFO] 
/C:/Users/ggregory/git/a/commons-cli/src/test/java/org/apache/commons/cli/bug/BugCLI148Test.java:
 Recompile with -Xlint:deprecation for details.
[INFO]
[INFO] --- animal-sniffer:1.23:check (checkAPIcompatibility) @ commons-cli ---
[INFO] Checking unresolved references to org.codehaus.mojo.signature:java18:1.0
[INFO]
[INFO] --- jacoco:0.8.10:prepare-agent (prepare-agent) @ commons-cli ---
[INFO] argLine set to 

[jira] [Comment Edited] (MSOURCES-143) Can't create a source and test jar in Commons using commons-parent

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MSOURCES-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755330#comment-17755330
 ] 

Gary D. Gregory edited comment on MSOURCES-143 at 8/17/23 2:43 AM:
---

Here is my console output (using MAVEN_ARGS=-V) BUT
 * I tried Java 17, it worked, then
 * I tried Java 11, it worked, then
 * I tried Java 8, it failed:

{noformat}
mvn clean package
Apache Maven 3.9.3 (21122926829f1ead511c958d89bd2f672198ae9f)
Maven home: C:\java\apache-maven-3.9.3
Java version: 1.8.0_382, vendor: Temurin, runtime: C:\Program Files\Eclipse 
Adoptium\jdk-8.0.382.5-hotspot\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
[INFO] Scanning for projects...
[INFO]
[INFO] --< commons-cli:commons-cli >---
[INFO] Building Apache Commons CLI 1.6.0-SNAPSHOT
[INFO]   from pom.xml
[INFO] [ jar ]-
[INFO]
[INFO] --- clean:3.2.0:clean (default-clean) @ commons-cli ---
[INFO] Deleting C:\Users\ggregory\git\a\commons-cli\target
[INFO]
[INFO] --- enforcer:3.3.0:enforce (enforce-maven-version) @ commons-cli ---
[INFO] Rule 0: org.apache.maven.enforcer.rules.version.RequireMavenVersion 
passed
[INFO] Rule 1: org.apache.maven.enforcer.rules.version.RequireJavaVersion passed
[INFO]
[INFO] --- enforcer:3.3.0:enforce (enforce-java-version) @ commons-cli ---
[INFO]
[INFO] --- enforcer:3.3.0:enforce (enforce-maven-3) @ commons-cli ---
[INFO]
[INFO] --- apache-rat:0.15:check (rat-check) @ commons-cli ---
[INFO] Enabled default license matchers.
[INFO] Will parse SCM ignores for exclusions...
[INFO] Parsing exclusions from C:\Users\ggregory\git\a\commons-cli\.gitignore
[INFO] Finished adding exclusions from SCM ignore files.
[INFO] 76 implicit excludes.
[INFO] 13 explicit excludes.
[INFO] 100 resources included
[INFO] Rat check: Summary over all files. Unapproved: 0, unknown: 0, generated: 
0, approved: 93 licenses.
[INFO]
[INFO] --- build-helper:3.4.0:parse-version (parse-version) @ commons-cli ---
[INFO]
[INFO] --- antrun:3.1.0:run (javadoc.resources) @ commons-cli ---
[INFO] Executing tasks
[INFO]  [copy] Copying 2 files to 
C:\Users\ggregory\git\a\commons-cli\target\apidocs\META-INF
[INFO] Executed tasks
[INFO]
[INFO] --- remote-resources:3.1.0:process (process-resource-bundles) @ 
commons-cli ---
[INFO] Skipping remote resources execution.
[INFO]
[INFO] --- buildnumber:3.2.0:create (default) @ commons-cli ---
[INFO] Executing: cmd.exe /X /C "git rev-parse --verify HEAD"
[INFO] Working directory: C:\Users\ggregory\git\a\commons-cli
[INFO] Storing buildNumber: null at timestamp: 1692239650046
[INFO] Executing: cmd.exe /X /C "git symbolic-ref HEAD"
[INFO] Working directory: C:\Users\ggregory\git\a\commons-cli
[INFO] Storing scmBranch: master
[INFO]
[INFO] --- resources:3.3.1:resources (default-resources) @ commons-cli ---
[INFO] skip non existing resourceDirectory 
C:\Users\ggregory\git\a\commons-cli\src\main\resources
[INFO] Copying 2 resources from  to target\classes\META-INF
[INFO]
[INFO] --- compiler:3.11.0:compile (default-compile) @ commons-cli ---
[INFO] Changes detected - recompiling the module! :source
[INFO] Compiling 23 source files with javac [debug target 1.8] to target\classes
[INFO] 
/C:/Users/ggregory/git/a/commons-cli/src/main/java/org/apache/commons/cli/Parser.java:
 Some input files use unchecked or unsafe operations.
[INFO] 
/C:/Users/ggregory/git/a/commons-cli/src/main/java/org/apache/commons/cli/Parser.java:
 Recompile with -Xlint:unchecked for details.
[INFO]
[INFO] --- bundle:5.1.9:manifest (bundle-manifest) @ commons-cli ---
[INFO] No MANIFEST.MF file found, generating manifest.
[INFO] Writing manifest: 
C:\Users\ggregory\git\a\commons-cli\target\osgi\MANIFEST.MF
[INFO]
[INFO] --- resources:3.3.1:testResources (default-testResources) @ commons-cli 
---
[INFO] Copying 1 resource from src\test\resources to target\test-classes
[INFO] Copying 2 resources from  to target\test-classes\META-INF
[INFO]
[INFO] --- compiler:3.11.0:testCompile (default-testCompile) @ commons-cli ---
[INFO] Changes detected - recompiling the module! :dependency
[INFO] Compiling 29 source files with javac [debug target 1.8] to 
target\test-classes
[INFO] 
/C:/Users/ggregory/git/a/commons-cli/src/test/java/org/apache/commons/cli/bug/BugCLI148Test.java:
 Some input files use or override a deprecated API.
[INFO] 
/C:/Users/ggregory/git/a/commons-cli/src/test/java/org/apache/commons/cli/bug/BugCLI148Test.java:
 Recompile with -Xlint:deprecation for details.
[INFO]
[INFO] --- animal-sniffer:1.23:check (checkAPIcompatibility) @ commons-cli ---
[INFO] Checking unresolved references to org.codehaus.mojo.signature:java18:1.0
[INFO]
[INFO] --- jacoco:0.8.10:prepare-agent (prepare-agent) @ commons-cli ---
[INFO] argLine set to 

[jira] [Commented] (MSOURCES-143) Can't create a source and test jar in Commons using commons-parent

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MSOURCES-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755330#comment-17755330
 ] 

Gary D. Gregory commented on MSOURCES-143:
--

Here is my console output (using MAVEN_ARGS=-V)
{noformat}
mvn clean package
Apache Maven 3.9.3 (21122926829f1ead511c958d89bd2f672198ae9f)
Maven home: C:\java\apache-maven-3.9.3
Java version: 1.8.0_382, vendor: Temurin, runtime: C:\Program Files\Eclipse 
Adoptium\jdk-8.0.382.5-hotspot\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
[INFO] Scanning for projects...
[INFO]
[INFO] --< commons-cli:commons-cli >---
[INFO] Building Apache Commons CLI 1.6.0-SNAPSHOT
[INFO]   from pom.xml
[INFO] [ jar ]-
[INFO]
[INFO] --- clean:3.2.0:clean (default-clean) @ commons-cli ---
[INFO] Deleting C:\Users\ggregory\git\a\commons-cli\target
[INFO]
[INFO] --- enforcer:3.3.0:enforce (enforce-maven-version) @ commons-cli ---
[INFO] Rule 0: org.apache.maven.enforcer.rules.version.RequireMavenVersion 
passed
[INFO] Rule 1: org.apache.maven.enforcer.rules.version.RequireJavaVersion passed
[INFO]
[INFO] --- enforcer:3.3.0:enforce (enforce-java-version) @ commons-cli ---
[INFO]
[INFO] --- enforcer:3.3.0:enforce (enforce-maven-3) @ commons-cli ---
[INFO]
[INFO] --- apache-rat:0.15:check (rat-check) @ commons-cli ---
[INFO] Enabled default license matchers.
[INFO] Will parse SCM ignores for exclusions...
[INFO] Parsing exclusions from C:\Users\ggregory\git\a\commons-cli\.gitignore
[INFO] Finished adding exclusions from SCM ignore files.
[INFO] 76 implicit excludes.
[INFO] 13 explicit excludes.
[INFO] 100 resources included
[INFO] Rat check: Summary over all files. Unapproved: 0, unknown: 0, generated: 
0, approved: 93 licenses.
[INFO]
[INFO] --- build-helper:3.4.0:parse-version (parse-version) @ commons-cli ---
[INFO]
[INFO] --- antrun:3.1.0:run (javadoc.resources) @ commons-cli ---
[INFO] Executing tasks
[INFO]  [copy] Copying 2 files to 
C:\Users\ggregory\git\a\commons-cli\target\apidocs\META-INF
[INFO] Executed tasks
[INFO]
[INFO] --- remote-resources:3.1.0:process (process-resource-bundles) @ 
commons-cli ---
[INFO] Skipping remote resources execution.
[INFO]
[INFO] --- buildnumber:3.2.0:create (default) @ commons-cli ---
[INFO] Executing: cmd.exe /X /C "git rev-parse --verify HEAD"
[INFO] Working directory: C:\Users\ggregory\git\a\commons-cli
[INFO] Storing buildNumber: null at timestamp: 1692239650046
[INFO] Executing: cmd.exe /X /C "git symbolic-ref HEAD"
[INFO] Working directory: C:\Users\ggregory\git\a\commons-cli
[INFO] Storing scmBranch: master
[INFO]
[INFO] --- resources:3.3.1:resources (default-resources) @ commons-cli ---
[INFO] skip non existing resourceDirectory 
C:\Users\ggregory\git\a\commons-cli\src\main\resources
[INFO] Copying 2 resources from  to target\classes\META-INF
[INFO]
[INFO] --- compiler:3.11.0:compile (default-compile) @ commons-cli ---
[INFO] Changes detected - recompiling the module! :source
[INFO] Compiling 23 source files with javac [debug target 1.8] to target\classes
[INFO] 
/C:/Users/ggregory/git/a/commons-cli/src/main/java/org/apache/commons/cli/Parser.java:
 Some input files use unchecked or unsafe operations.
[INFO] 
/C:/Users/ggregory/git/a/commons-cli/src/main/java/org/apache/commons/cli/Parser.java:
 Recompile with -Xlint:unchecked for details.
[INFO]
[INFO] --- bundle:5.1.9:manifest (bundle-manifest) @ commons-cli ---
[INFO] No MANIFEST.MF file found, generating manifest.
[INFO] Writing manifest: 
C:\Users\ggregory\git\a\commons-cli\target\osgi\MANIFEST.MF
[INFO]
[INFO] --- resources:3.3.1:testResources (default-testResources) @ commons-cli 
---
[INFO] Copying 1 resource from src\test\resources to target\test-classes
[INFO] Copying 2 resources from  to target\test-classes\META-INF
[INFO]
[INFO] --- compiler:3.11.0:testCompile (default-testCompile) @ commons-cli ---
[INFO] Changes detected - recompiling the module! :dependency
[INFO] Compiling 29 source files with javac [debug target 1.8] to 
target\test-classes
[INFO] 
/C:/Users/ggregory/git/a/commons-cli/src/test/java/org/apache/commons/cli/bug/BugCLI148Test.java:
 Some input files use or override a deprecated API.
[INFO] 
/C:/Users/ggregory/git/a/commons-cli/src/test/java/org/apache/commons/cli/bug/BugCLI148Test.java:
 Recompile with -Xlint:deprecation for details.
[INFO]
[INFO] --- animal-sniffer:1.23:check (checkAPIcompatibility) @ commons-cli ---
[INFO] Checking unresolved references to org.codehaus.mojo.signature:java18:1.0
[INFO]
[INFO] --- jacoco:0.8.10:prepare-agent (prepare-agent) @ commons-cli ---
[INFO] argLine set to 

[jira] [Commented] (MSOURCES-143) Can't create a source and test jar in Commons using commons-parent

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MSOURCES-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755036#comment-17755036
 ] 

Gary D. Gregory commented on MSOURCES-143:
--

I am so sorry I missed a step! You must edit commons-cli's pom.xml to use the 
60-SNAPSHOT commons-parent. 

> Can't create a source and test jar in Commons using commons-parent
> --
>
> Key: MSOURCES-143
> URL: https://issues.apache.org/jira/browse/MSOURCES-143
> Project: Maven Source Plugin
>  Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Gary D. Gregory
>Priority: Major
>
> Steps to reproduce:
> # git clone https://gitbox.apache.org/repos/asf/commons-parent.git
> # cd commons-parent
> # git checkout 8d886ce8382f7a79f06d51a3afc386b8a37d0473
> # mvn clean install
> # cd ..
> # git clone https://gitbox.apache.org/repos/asf/commons-cli.git
> # cd commons-cli
> # git checkout 08f8c5034a8492be6db65b2086341c292489ee53
> # mvn clean package
> [INFO] --- source:3.3.0:jar-no-fork (create-source-jar) @ commons-cli ---
> [ERROR] We have duplicated artifacts attached.
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  15.233 s
> [INFO] Finished at: 2023-08-15T15:39:45-04:00
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-source-plugin:3.3.0:jar-no-fork 
> (create-source-jar) on project commons-cli: Presumably you have configured 
> maven-source-plugn to execute twice times in your build. You have to 
> configure a classifier for at least on of them. -> [Help 1]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MSOURCES-143) Can't create a source and test jar in Commons using commons-parent

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MSOURCES-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755035#comment-17755035
 ] 

Gary D. Gregory commented on MSOURCES-143:
--

FWIW I never use the apache-release profile, but I do use the release profile. 

> Can't create a source and test jar in Commons using commons-parent
> --
>
> Key: MSOURCES-143
> URL: https://issues.apache.org/jira/browse/MSOURCES-143
> Project: Maven Source Plugin
>  Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Gary D. Gregory
>Priority: Major
>
> Steps to reproduce:
> # git clone https://gitbox.apache.org/repos/asf/commons-parent.git
> # cd commons-parent
> # git checkout 8d886ce8382f7a79f06d51a3afc386b8a37d0473
> # mvn clean install
> # cd ..
> # git clone https://gitbox.apache.org/repos/asf/commons-cli.git
> # cd commons-cli
> # git checkout 08f8c5034a8492be6db65b2086341c292489ee53
> # mvn clean package
> [INFO] --- source:3.3.0:jar-no-fork (create-source-jar) @ commons-cli ---
> [ERROR] We have duplicated artifacts attached.
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  15.233 s
> [INFO] Finished at: 2023-08-15T15:39:45-04:00
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-source-plugin:3.3.0:jar-no-fork 
> (create-source-jar) on project commons-cli: Presumably you have configured 
> maven-source-plugn to execute twice times in your build. You have to 
> configure a classifier for at least on of them. -> [Help 1]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (MSOURCES-143) Can't create a source and test jar in Commons using commons-parent

[Gary D. Gregory (Jira)]

Gary D. Gregory created MSOURCES-143:


 Summary: Can't create a source and test jar in Commons using 
commons-parent
 Key: MSOURCES-143
 URL: https://issues.apache.org/jira/browse/MSOURCES-143
 Project: Maven Source Plugin
  Issue Type: Bug
Affects Versions: 3.3.0
Reporter: Gary D. Gregory


Steps to reproduce:
# git clone https://gitbox.apache.org/repos/asf/commons-parent
# cd commons-parent
# git checkout 8d886ce8382f7a79f06d51a3afc386b8a37d0473
# mvn clean install
# cd ..
# git clone https://gitbox.apache.org/repos/asf/commons-cli
# cd commons-cli
# git checkout 08f8c5034a8492be6db65b2086341c292489ee53
# mvn clean package

[INFO] --- source:3.3.0:jar-no-fork (create-source-jar) @ commons-cli ---
[ERROR] We have duplicated artifacts attached.
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  15.233 s
[INFO] Finished at: 2023-08-15T15:39:45-04:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-source-plugin:3.3.0:jar-no-fork 
(create-source-jar) on project commons-cli: Presumably you have configured 
maven-source-plugn to execute twice times in your build. You have to configure 
a classifier for at least on of them. -> [Help 1]





--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Comment Edited] (MSHARED-1248) maven-dependency-analyzer should log instead of failing when analyzing a corrupted jar file

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MSHARED-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17738096#comment-17738096
 ] 

Gary D. Gregory edited comment on MSHARED-1248 at 7/2/23 10:46 PM:
---

Next up, expectation management: Would someone tag this ticket with an expected 
version? Or, did this make it in 1.13.2?

And, would someone start the ball rolling on a release or provide a guesstimate?


was (Author: garydgregory):
Next up, expectation management: Would someone tag this ticket with an expected 
version? Or, did this make it in 11.3.2?

And, would someone start the ball rolling on a release or provide a guesstimate?

> maven-dependency-analyzer should log instead of failing when analyzing a 
> corrupted jar file
> ---
>
> Key: MSHARED-1248
> URL: https://issues.apache.org/jira/browse/MSHARED-1248
> Project: Maven Shared Components
>  Issue Type: Bug
>  Components: maven-dependency-analyzer
>Affects Versions: maven-dependency-analyzer-1.13.1
> Environment: Apache Maven 3.9.1 
> (2e178502fcdbffc201671fb2537d0cb4b4cc58f8)
> Maven home: C:\java\apache-maven-3.9.1
> Java version: 1.8.0_362, vendor: Temurin, runtime: C:\Program Files\Eclipse 
> Adoptium\jdk-8.0.362.9-hotspot\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> Microsoft Windows [Version 10.0.19044.2728]
>Reporter: Gary D. Gregory
>Priority: Major
>
> In Apache Commons BCEL, we include corrupted jar files created by the 
> oss-fuzz project which causes the build to fail when the CycloneDX plugin 
> runs to create an SBOM.
> This issue happens only after getting past the issue fixed by MSHARED-1247
> {noformat}
> [DEBUG] CycloneDX: Calculating Hashes
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  3.594 s
> [INFO] Finished at: 2023-04-29T15:23:05-04:00
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom (default-cli) on 
> project bcel: Execution default-cli of goal 
> org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom failed: 
> Unsupported class file major version 1025 from directory = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes, path = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes\ossfuzz\issue51980\Test.class
>  -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom 
> (default-cli) on project bcel: Execution default-cli of goal 
> org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom failed: 
> Unsupported class file major version 1025 from directory = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes, path = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes\ossfuzz\issue51980\Test.class
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:347)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
> (MojoExecutor.java:330)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:175)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 
> (MojoExecutor.java:76)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run 
> (MojoExecutor.java:163)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute 
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:160)
> 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:827)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:272)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:195)
> 

[jira] [Comment Edited] (MSHARED-1248) maven-dependency-analyzer should log instead of failing when analyzing a corrupted jar file

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MSHARED-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17738096#comment-17738096
 ] 

Gary D. Gregory edited comment on MSHARED-1248 at 7/2/23 10:46 PM:
---

Next up, expectation management: Would someone tag this ticket with an expected 
version? Or, did this make it in 11.3.2?

And, would someone start the ball rolling on a release or provide a guesstimate?


was (Author: garydgregory):
Next up, expectation management: Would someone tag this ticket with an expected 
version?

And, would someone start the ball rolling on a release or provide a guesstimate?

> maven-dependency-analyzer should log instead of failing when analyzing a 
> corrupted jar file
> ---
>
> Key: MSHARED-1248
> URL: https://issues.apache.org/jira/browse/MSHARED-1248
> Project: Maven Shared Components
>  Issue Type: Bug
>  Components: maven-dependency-analyzer
>Affects Versions: maven-dependency-analyzer-1.13.1
> Environment: Apache Maven 3.9.1 
> (2e178502fcdbffc201671fb2537d0cb4b4cc58f8)
> Maven home: C:\java\apache-maven-3.9.1
> Java version: 1.8.0_362, vendor: Temurin, runtime: C:\Program Files\Eclipse 
> Adoptium\jdk-8.0.362.9-hotspot\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> Microsoft Windows [Version 10.0.19044.2728]
>Reporter: Gary D. Gregory
>Priority: Major
>
> In Apache Commons BCEL, we include corrupted jar files created by the 
> oss-fuzz project which causes the build to fail when the CycloneDX plugin 
> runs to create an SBOM.
> This issue happens only after getting past the issue fixed by MSHARED-1247
> {noformat}
> [DEBUG] CycloneDX: Calculating Hashes
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  3.594 s
> [INFO] Finished at: 2023-04-29T15:23:05-04:00
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom (default-cli) on 
> project bcel: Execution default-cli of goal 
> org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom failed: 
> Unsupported class file major version 1025 from directory = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes, path = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes\ossfuzz\issue51980\Test.class
>  -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom 
> (default-cli) on project bcel: Execution default-cli of goal 
> org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom failed: 
> Unsupported class file major version 1025 from directory = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes, path = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes\ossfuzz\issue51980\Test.class
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:347)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
> (MojoExecutor.java:330)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:175)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 
> (MojoExecutor.java:76)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run 
> (MojoExecutor.java:163)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute 
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:160)
> 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:827)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:272)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:195)
> at 

[jira] [Commented] (MSHARED-1248) maven-dependency-analyzer should log instead of failing when analyzing a corrupted jar file

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MSHARED-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17738096#comment-17738096
 ] 

Gary D. Gregory commented on MSHARED-1248:
--

Next up, expectation management: Would someone tag this ticket with an expected 
version?

And, would someone start the ball rolling on a release or provide a guesstimate?

> maven-dependency-analyzer should log instead of failing when analyzing a 
> corrupted jar file
> ---
>
> Key: MSHARED-1248
> URL: https://issues.apache.org/jira/browse/MSHARED-1248
> Project: Maven Shared Components
>  Issue Type: Bug
>  Components: maven-dependency-analyzer
>Affects Versions: maven-dependency-analyzer-1.13.1
> Environment: Apache Maven 3.9.1 
> (2e178502fcdbffc201671fb2537d0cb4b4cc58f8)
> Maven home: C:\java\apache-maven-3.9.1
> Java version: 1.8.0_362, vendor: Temurin, runtime: C:\Program Files\Eclipse 
> Adoptium\jdk-8.0.362.9-hotspot\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> Microsoft Windows [Version 10.0.19044.2728]
>Reporter: Gary D. Gregory
>Priority: Major
>
> In Apache Commons BCEL, we include corrupted jar files created by the 
> oss-fuzz project which causes the build to fail when the CycloneDX plugin 
> runs to create an SBOM.
> This issue happens only after getting past the issue fixed by MSHARED-1247
> {noformat}
> [DEBUG] CycloneDX: Calculating Hashes
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  3.594 s
> [INFO] Finished at: 2023-04-29T15:23:05-04:00
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom (default-cli) on 
> project bcel: Execution default-cli of goal 
> org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom failed: 
> Unsupported class file major version 1025 from directory = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes, path = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes\ossfuzz\issue51980\Test.class
>  -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom 
> (default-cli) on project bcel: Execution default-cli of goal 
> org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom failed: 
> Unsupported class file major version 1025 from directory = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes, path = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes\ossfuzz\issue51980\Test.class
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:347)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
> (MojoExecutor.java:330)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:175)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 
> (MojoExecutor.java:76)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run 
> (MojoExecutor.java:163)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute 
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:160)
> 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:827)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:272)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:195)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke 
> (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke 
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:498)
>  

[jira] (MSHARED-1248) maven-dependency-analyzer should log instead of failing when analyzing a corrupted jar file

[Gary D. Gregory (Jira)]

[ https://issues.apache.org/jira/browse/MSHARED-1248 ]


Gary D. Gregory deleted comment on MSHARED-1248:
--

was (Author: garydgregory):
_emphasized text_

> maven-dependency-analyzer should log instead of failing when analyzing a 
> corrupted jar file
> ---
>
> Key: MSHARED-1248
> URL: https://issues.apache.org/jira/browse/MSHARED-1248
> Project: Maven Shared Components
>  Issue Type: Bug
>  Components: maven-dependency-analyzer
>Affects Versions: maven-dependency-analyzer-1.13.1
> Environment: Apache Maven 3.9.1 
> (2e178502fcdbffc201671fb2537d0cb4b4cc58f8)
> Maven home: C:\java\apache-maven-3.9.1
> Java version: 1.8.0_362, vendor: Temurin, runtime: C:\Program Files\Eclipse 
> Adoptium\jdk-8.0.362.9-hotspot\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> Microsoft Windows [Version 10.0.19044.2728]
>Reporter: Gary D. Gregory
>Priority: Major
>
> In Apache Commons BCEL, we include corrupted jar files created by the 
> oss-fuzz project which causes the build to fail when the CycloneDX plugin 
> runs to create an SBOM.
> This issue happens only after getting past the issue fixed by MSHARED-1247
> {noformat}
> [DEBUG] CycloneDX: Calculating Hashes
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  3.594 s
> [INFO] Finished at: 2023-04-29T15:23:05-04:00
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom (default-cli) on 
> project bcel: Execution default-cli of goal 
> org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom failed: 
> Unsupported class file major version 1025 from directory = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes, path = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes\ossfuzz\issue51980\Test.class
>  -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom 
> (default-cli) on project bcel: Execution default-cli of goal 
> org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom failed: 
> Unsupported class file major version 1025 from directory = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes, path = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes\ossfuzz\issue51980\Test.class
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:347)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
> (MojoExecutor.java:330)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:175)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 
> (MojoExecutor.java:76)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run 
> (MojoExecutor.java:163)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute 
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:160)
> 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:827)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:272)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:195)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke 
> (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke 
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:498)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced 
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch 
> (Launcher.java:225)
> at 

[jira] [Commented] (MSHARED-1247) maven-dependency-analyzer java.lang.RuntimeException: Unknown constant pool type '17'

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MSHARED-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17718146#comment-17718146
 ] 

Gary D. Gregory commented on MSHARED-1247:
--

[~sjaranowski] TY!

> maven-dependency-analyzer java.lang.RuntimeException: Unknown constant pool 
> type '17'
> -
>
> Key: MSHARED-1247
> URL: https://issues.apache.org/jira/browse/MSHARED-1247
> Project: Maven Shared Components
>  Issue Type: Bug
>  Components: maven-dependency-analyzer
>Affects Versions: maven-dependency-analyzer-1.13.1
> Environment: Apache Maven 3.9.1 
> (2e178502fcdbffc201671fb2537d0cb4b4cc58f8)
> Maven home: C:\java\apache-maven-3.9.1
> Java version: 1.8.0_362, vendor: Temurin, runtime: C:\Program Files\Eclipse 
> Adoptium\jdk-8.0.362.9-hotspot\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> Microsoft Windows [Version 10.0.19044.2728]
>Reporter: Gary D. Gregory
>Assignee: Slawomir Jaranowski
>Priority: Blocker
> Fix For: maven-dependency-analyzer-1.13.2
>
>
> You get the exception:
> {noformat}
> ...
> Caused by: java.lang.RuntimeException: Unknown constant pool type '17'
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ConstantPoolParser.parseConstantPoolClassReferences
>  (ConstantPoolParser.java:120)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ConstantPoolParser.getConstantPoolClassReferences
>  (ConstantPoolParser.java:104)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.DependencyClassFileVisitor.visitClass
>  (DependencyClassFileVisitor.java:59)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
> (ClassFileVisitorUtils.java:114)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
> (ClassFileVisitorUtils.java:106)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.acceptDirectory
>  (ClassFileVisitorUtils.java:97)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.accept 
> (ClassFileVisitorUtils.java:59)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ASMDependencyAnalyzer.analyze 
> (ASMDependencyAnalyzer.java:43)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildDependencyClasses
>  (DefaultProjectDependencyAnalyzer.java:206)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildTestDependencyClasses
>  (DefaultProjectDependencyAnalyzer.java:200)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.analyze
>  (DefaultProjectDependencyAnalyzer.java:68)
> at org.cyclonedx.maven.CycloneDxMojo.doProjectDependencyAnalysis 
> (CycloneDxMojo.java:86)
> at 
> org.cyclonedx.maven.CycloneDxAggregateMojo.extractComponentsAndDependencies 
> (CycloneDxAggregateMojo.java:130)
> at org.cyclonedx.maven.BaseCycloneDxMojo.execute 
> (BaseCycloneDxMojo.java:258)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:342)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
> (MojoExecutor.java:330)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:175)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 
> (MojoExecutor.java:76)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run 
> (MojoExecutor.java:163)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute 
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:160)
> 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:827)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:272)
> at 

[jira] [Updated] (MSHARED-1247) maven-dependency-analyzer java.lang.RuntimeException: Unknown constant pool type '17'

[Gary D. Gregory (Jira)]

 [ 
https://issues.apache.org/jira/browse/MSHARED-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gary D. Gregory updated MSHARED-1247:
-
Description: 
You get the exception:
{noformat}
...
Caused by: java.lang.RuntimeException: Unknown constant pool type '17'
at 
org.apache.maven.shared.dependency.analyzer.asm.ConstantPoolParser.parseConstantPoolClassReferences
 (ConstantPoolParser.java:120)
at 
org.apache.maven.shared.dependency.analyzer.asm.ConstantPoolParser.getConstantPoolClassReferences
 (ConstantPoolParser.java:104)
at 
org.apache.maven.shared.dependency.analyzer.asm.DependencyClassFileVisitor.visitClass
 (DependencyClassFileVisitor.java:59)
at 
org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
(ClassFileVisitorUtils.java:114)
at 
org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
(ClassFileVisitorUtils.java:106)
at 
org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.acceptDirectory
 (ClassFileVisitorUtils.java:97)
at org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.accept 
(ClassFileVisitorUtils.java:59)
at 
org.apache.maven.shared.dependency.analyzer.asm.ASMDependencyAnalyzer.analyze 
(ASMDependencyAnalyzer.java:43)
at 
org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildDependencyClasses
 (DefaultProjectDependencyAnalyzer.java:206)
at 
org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildTestDependencyClasses
 (DefaultProjectDependencyAnalyzer.java:200)
at 
org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.analyze
 (DefaultProjectDependencyAnalyzer.java:68)
at org.cyclonedx.maven.CycloneDxMojo.doProjectDependencyAnalysis 
(CycloneDxMojo.java:86)
at 
org.cyclonedx.maven.CycloneDxAggregateMojo.extractComponentsAndDependencies 
(CycloneDxAggregateMojo.java:130)
at org.cyclonedx.maven.BaseCycloneDxMojo.execute 
(BaseCycloneDxMojo.java:258)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
(DefaultBuildPluginManager.java:126)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
(MojoExecutor.java:342)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
(MojoExecutor.java:330)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:175)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 
(MojoExecutor.java:76)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run 
(MojoExecutor.java:163)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute 
(DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:160)
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:827)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:272)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:195)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke 
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke 
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced 
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch 
(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode 
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main 
(Launcher.java:347)
{noformat}
When running:
{noformat}
git clone https://gitbox.apache.org/repos/asf/commons-bcel.git
cd commons-bcel
git checkout 9a36684def5f113dea5cbc11012f4c3189ef7c7a
{noformat}
edit pom.xml to and update commons-parent to 57
{noformat}
mvn cyclonedx:makeAggregateBom
{noformat}

PR: https://github.com/apache/maven-dependency-analyzer/pull/88
 

  was:
You get the exception:
{noformat}
...
Caused by: java.lang.RuntimeException: Unknown constant pool type '17'
at 

[jira] [Commented] (MSHARED-1247) maven-dependency-analyzer java.lang.RuntimeException: Unknown constant pool type '17'

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MSHARED-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17718054#comment-17718054
 ] 

Gary D. Gregory commented on MSHARED-1247:
--

FYI, BCEL will wait for 1.13.2 before it can update it's parent pom dependency.

> maven-dependency-analyzer java.lang.RuntimeException: Unknown constant pool 
> type '17'
> -
>
> Key: MSHARED-1247
> URL: https://issues.apache.org/jira/browse/MSHARED-1247
> Project: Maven Shared Components
>  Issue Type: Bug
>  Components: maven-dependency-analyzer
>Affects Versions: maven-dependency-analyzer-1.13.1
> Environment: Apache Maven 3.9.1 
> (2e178502fcdbffc201671fb2537d0cb4b4cc58f8)
> Maven home: C:\java\apache-maven-3.9.1
> Java version: 1.8.0_362, vendor: Temurin, runtime: C:\Program Files\Eclipse 
> Adoptium\jdk-8.0.362.9-hotspot\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> Microsoft Windows [Version 10.0.19044.2728]
>Reporter: Gary D. Gregory
>Priority: Blocker
> Fix For: maven-dependency-analyzer-1.13.2
>
>
> You get the exception:
> {noformat}
> ...
> Caused by: java.lang.RuntimeException: Unknown constant pool type '17'
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ConstantPoolParser.parseConstantPoolClassReferences
>  (ConstantPoolParser.java:120)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ConstantPoolParser.getConstantPoolClassReferences
>  (ConstantPoolParser.java:104)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.DependencyClassFileVisitor.visitClass
>  (DependencyClassFileVisitor.java:59)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
> (ClassFileVisitorUtils.java:114)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
> (ClassFileVisitorUtils.java:106)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.acceptDirectory
>  (ClassFileVisitorUtils.java:97)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.accept 
> (ClassFileVisitorUtils.java:59)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ASMDependencyAnalyzer.analyze 
> (ASMDependencyAnalyzer.java:43)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildDependencyClasses
>  (DefaultProjectDependencyAnalyzer.java:206)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildTestDependencyClasses
>  (DefaultProjectDependencyAnalyzer.java:200)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.analyze
>  (DefaultProjectDependencyAnalyzer.java:68)
> at org.cyclonedx.maven.CycloneDxMojo.doProjectDependencyAnalysis 
> (CycloneDxMojo.java:86)
> at 
> org.cyclonedx.maven.CycloneDxAggregateMojo.extractComponentsAndDependencies 
> (CycloneDxAggregateMojo.java:130)
> at org.cyclonedx.maven.BaseCycloneDxMojo.execute 
> (BaseCycloneDxMojo.java:258)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:342)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
> (MojoExecutor.java:330)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:175)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 
> (MojoExecutor.java:76)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run 
> (MojoExecutor.java:163)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute 
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:160)
> 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:827)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:272)
>   

[jira] [Commented] (MSHARED-1248) maven-dependency-analyzer should log instead of failing when analyzing a corrupted jar file

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MSHARED-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17718038#comment-17718038
 ] 

Gary D. Gregory commented on MSHARED-1248:
--

I appreciate the pragmatic solution [~sjaranowski] ;-) but that does not solve 
the issue for the general case. I've merged your PR in Apache Commons BCEL so 
at least we are past the issue I encountered :-)

> maven-dependency-analyzer should log instead of failing when analyzing a 
> corrupted jar file
> ---
>
> Key: MSHARED-1248
> URL: https://issues.apache.org/jira/browse/MSHARED-1248
> Project: Maven Shared Components
>  Issue Type: Improvement
>  Components: maven-dependency-analyzer
>Affects Versions: maven-dependency-analyzer-1.13.1
> Environment: Apache Maven 3.9.1 
> (2e178502fcdbffc201671fb2537d0cb4b4cc58f8)
> Maven home: C:\java\apache-maven-3.9.1
> Java version: 1.8.0_362, vendor: Temurin, runtime: C:\Program Files\Eclipse 
> Adoptium\jdk-8.0.362.9-hotspot\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> Microsoft Windows [Version 10.0.19044.2728]
>Reporter: Gary D. Gregory
>Priority: Major
>
> In Apache Commons BCEL, we include corrupted jar files created by the 
> oss-fuzz project which causes the build to fail when the CycloneDX plugin 
> runs to create an SBOM.
> This issue happens only after getting past the issue fixed by MSHARED-1247
> {noformat}
> [DEBUG] CycloneDX: Calculating Hashes
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  3.594 s
> [INFO] Finished at: 2023-04-29T15:23:05-04:00
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom (default-cli) on 
> project bcel: Execution default-cli of goal 
> org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom failed: 
> Unsupported class file major version 1025 from directory = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes, path = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes\ossfuzz\issue51980\Test.class
>  -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom 
> (default-cli) on project bcel: Execution default-cli of goal 
> org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom failed: 
> Unsupported class file major version 1025 from directory = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes, path = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes\ossfuzz\issue51980\Test.class
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:347)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
> (MojoExecutor.java:330)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:175)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 
> (MojoExecutor.java:76)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run 
> (MojoExecutor.java:163)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute 
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:160)
> 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:827)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:272)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:195)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke 
> (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke 
> (DelegatingMethodAccessorImpl.java:43)
> at 

[jira] [Updated] (MSHARED-1248) maven-dependency-analyzer should log instead of failing when analyzing a corrupted jar file

[Gary D. Gregory (Jira)]

 [ 
https://issues.apache.org/jira/browse/MSHARED-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gary D. Gregory updated MSHARED-1248:
-
Summary: maven-dependency-analyzer should log instead of failing when 
analyzing a corrupted jar file  (was: maven-dependency-analyzer should not log 
and not fail when analyzing a corrupted jar file)

> maven-dependency-analyzer should log instead of failing when analyzing a 
> corrupted jar file
> ---
>
> Key: MSHARED-1248
> URL: https://issues.apache.org/jira/browse/MSHARED-1248
> Project: Maven Shared Components
>  Issue Type: Improvement
>  Components: maven-dependency-analyzer
>Affects Versions: maven-dependency-analyzer-1.13.1
> Environment: Apache Maven 3.9.1 
> (2e178502fcdbffc201671fb2537d0cb4b4cc58f8)
> Maven home: C:\java\apache-maven-3.9.1
> Java version: 1.8.0_362, vendor: Temurin, runtime: C:\Program Files\Eclipse 
> Adoptium\jdk-8.0.362.9-hotspot\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> Microsoft Windows [Version 10.0.19044.2728]
>Reporter: Gary D. Gregory
>Priority: Major
>
> In Apache Commons BCEL, we include corrupted jar files created by the 
> oss-fuzz project which causes the build to fail when the CycloneDX plugin 
> runs to create an SBOM.
> This issue happens only after getting past the issue fixed by MSHARED-1247
> {noformat}
> [DEBUG] CycloneDX: Calculating Hashes
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  3.594 s
> [INFO] Finished at: 2023-04-29T15:23:05-04:00
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom (default-cli) on 
> project bcel: Execution default-cli of goal 
> org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom failed: 
> Unsupported class file major version 1025 from directory = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes, path = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes\ossfuzz\issue51980\Test.class
>  -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom 
> (default-cli) on project bcel: Execution default-cli of goal 
> org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom failed: 
> Unsupported class file major version 1025 from directory = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes, path = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes\ossfuzz\issue51980\Test.class
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:347)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
> (MojoExecutor.java:330)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:175)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 
> (MojoExecutor.java:76)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run 
> (MojoExecutor.java:163)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute 
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:160)
> 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:827)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:272)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:195)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke 
> (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke 
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:498)
>  

[jira] [Commented] (MSHARED-1248) maven-dependency-analyzer should not log and not fail when analyzing a corrupted jar file

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MSHARED-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17717971#comment-17717971
 ] 

Gary D. Gregory commented on MSHARED-1248:
--

_emphasized text_

> maven-dependency-analyzer should not log and not fail when analyzing a 
> corrupted jar file
> -
>
> Key: MSHARED-1248
> URL: https://issues.apache.org/jira/browse/MSHARED-1248
> Project: Maven Shared Components
>  Issue Type: Improvement
>  Components: maven-dependency-analyzer
>Affects Versions: maven-dependency-analyzer-1.13.1
> Environment: Apache Maven 3.9.1 
> (2e178502fcdbffc201671fb2537d0cb4b4cc58f8)
> Maven home: C:\java\apache-maven-3.9.1
> Java version: 1.8.0_362, vendor: Temurin, runtime: C:\Program Files\Eclipse 
> Adoptium\jdk-8.0.362.9-hotspot\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> Microsoft Windows [Version 10.0.19044.2728]
>Reporter: Gary D. Gregory
>Priority: Major
>
> In Apache Commons BCEL, we include corrupted jar files created by the 
> oss-fuzz project which causes the build to fail when the CycloneDX plugin 
> runs to create an SBOM.
> This issue happens only after getting past the issue fixed by MSHARED-1247
> {noformat}
> [DEBUG] CycloneDX: Calculating Hashes
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  3.594 s
> [INFO] Finished at: 2023-04-29T15:23:05-04:00
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom (default-cli) on 
> project bcel: Execution default-cli of goal 
> org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom failed: 
> Unsupported class file major version 1025 from directory = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes, path = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes\ossfuzz\issue51980\Test.class
>  -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom 
> (default-cli) on project bcel: Execution default-cli of goal 
> org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom failed: 
> Unsupported class file major version 1025 from directory = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes, path = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes\ossfuzz\issue51980\Test.class
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:347)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
> (MojoExecutor.java:330)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:175)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 
> (MojoExecutor.java:76)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run 
> (MojoExecutor.java:163)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute 
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:160)
> 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:827)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:272)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:195)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke 
> (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke 
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:498)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced 
> (Launcher.java:282)
> at 

[jira] [Updated] (MSHARED-1248) maven-dependency-analyzer should not log and not fail when analyzing a corrupted jar file

[Gary D. Gregory (Jira)]

 [ 
https://issues.apache.org/jira/browse/MSHARED-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gary D. Gregory updated MSHARED-1248:
-
  Component/s: maven-dependency-analyzer
Affects Version/s: maven-dependency-analyzer-1.13.1
  Environment: 
Apache Maven 3.9.1 (2e178502fcdbffc201671fb2537d0cb4b4cc58f8)
Maven home: C:\java\apache-maven-3.9.1
Java version: 1.8.0_362, vendor: Temurin, runtime: C:\Program Files\Eclipse 
Adoptium\jdk-8.0.362.9-hotspot\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

Microsoft Windows [Version 10.0.19044.2728]


> maven-dependency-analyzer should not log and not fail when analyzing a 
> corrupted jar file
> -
>
> Key: MSHARED-1248
> URL: https://issues.apache.org/jira/browse/MSHARED-1248
> Project: Maven Shared Components
>  Issue Type: Improvement
>  Components: maven-dependency-analyzer
>Affects Versions: maven-dependency-analyzer-1.13.1
> Environment: Apache Maven 3.9.1 
> (2e178502fcdbffc201671fb2537d0cb4b4cc58f8)
> Maven home: C:\java\apache-maven-3.9.1
> Java version: 1.8.0_362, vendor: Temurin, runtime: C:\Program Files\Eclipse 
> Adoptium\jdk-8.0.362.9-hotspot\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> Microsoft Windows [Version 10.0.19044.2728]
>Reporter: Gary D. Gregory
>Priority: Major
>
> In Apache Commons BCEL, we include corrupted jar files created by the 
> oss-fuzz project which causes the build to fail when the CycloneDX plugin 
> runs to create an SBOM.
> This issue happens only after getting past the issue fixed by MSHARED-1247
> {noformat}
> [DEBUG] CycloneDX: Calculating Hashes
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  3.594 s
> [INFO] Finished at: 2023-04-29T15:23:05-04:00
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom (default-cli) on 
> project bcel: Execution default-cli of goal 
> org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom failed: 
> Unsupported class file major version 1025 from directory = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes, path = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes\ossfuzz\issue51980\Test.class
>  -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom 
> (default-cli) on project bcel: Execution default-cli of goal 
> org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom failed: 
> Unsupported class file major version 1025 from directory = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes, path = 
> C:\Users\ggregory\git\a\commons-bcel\target\test-classes\ossfuzz\issue51980\Test.class
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:347)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
> (MojoExecutor.java:330)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:175)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 
> (MojoExecutor.java:76)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run 
> (MojoExecutor.java:163)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute 
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:160)
> 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:827)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:272)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:195)
> at 

[jira] [Updated] (MSHARED-1248) maven-dependency-analyzer should not log and not fail when analyzing a corrupted jar file

[Gary D. Gregory (Jira)]

 [ 
https://issues.apache.org/jira/browse/MSHARED-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gary D. Gregory updated MSHARED-1248:
-
Description: 
In Apache Commons BCEL, we include corrupted jar files created by the oss-fuzz 
project which causes the build to fail when the CycloneDX plugin runs to create 
an SBOM.

This issue happens only after getting past the issue fixed by MSHARED-1247

{noformat}
[DEBUG] CycloneDX: Calculating Hashes
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  3.594 s
[INFO] Finished at: 2023-04-29T15:23:05-04:00
[INFO] 
[ERROR] Failed to execute goal 
org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom (default-cli) on 
project bcel: Execution default-cli of goal 
org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom failed: Unsupported 
class file major version 1025 from directory = 
C:\Users\ggregory\git\a\commons-bcel\target\test-classes, path = 
C:\Users\ggregory\git\a\commons-bcel\target\test-classes\ossfuzz\issue51980\Test.class
 -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom (default-cli) on 
project bcel: Execution default-cli of goal 
org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom failed: Unsupported 
class file major version 1025 from directory = 
C:\Users\ggregory\git\a\commons-bcel\target\test-classes, path = 
C:\Users\ggregory\git\a\commons-bcel\target\test-classes\ossfuzz\issue51980\Test.class
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
(MojoExecutor.java:347)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
(MojoExecutor.java:330)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:175)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 
(MojoExecutor.java:76)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run 
(MojoExecutor.java:163)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute 
(DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:160)
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:827)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:272)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:195)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke 
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke 
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced 
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch 
(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode 
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main 
(Launcher.java:347)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
default-cli of goal org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom 
failed: Unsupported class file major version 1025 from directory = 
C:\Users\ggregory\git\a\commons-bcel\target\test-classes, path = 
C:\Users\ggregory\git\a\commons-bcel\target\test-classes\ossfuzz\issue51980\Test.class
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
(DefaultBuildPluginManager.java:133)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
(MojoExecutor.java:342)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
(MojoExecutor.java:330)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:175)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 
(MojoExecutor.java:76)
at 

[jira] [Created] (MSHARED-1248) maven-dependency-analyzer should not log and not fail when analyzing a corrupted jar file

[Gary D. Gregory (Jira)]

Gary D. Gregory created MSHARED-1248:


 Summary: maven-dependency-analyzer should not log and not fail 
when analyzing a corrupted jar file
 Key: MSHARED-1248
 URL: https://issues.apache.org/jira/browse/MSHARED-1248
 Project: Maven Shared Components
  Issue Type: Improvement
Reporter: Gary D. Gregory


In Apache Commons BCEL, we include corrupted jar files created by the oss-fuzz 
project which causes the build to fail when the CycloneDX plugin runs to create 
an SBOM.

This issue happens only after getting past the issue fixed by MSHARED-1247

{noformat}
[DEBUG] CycloneDX: Calculating Hashes
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  3.594 s
[INFO] Finished at: 2023-04-29T15:23:05-04:00
[INFO] 
[ERROR] Failed to execute goal 
org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom (default-cli) on 
project bcel: Execution default-cli of goal 
org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom failed: Unsupported 
class file major version 1025 from directory = 
C:\Users\ggregory\git\a\commons-bcel\target\test-classes, path = 
C:\Users\ggregory\git\a\commons-bcel\target\test-classes\ossfuzz\issue51980\Test.class
 -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom (default-cli) on 
project bcel: Execution default-cli of goal 
org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom failed: Unsupported 
class file major version 1025 from directory = 
C:\Users\ggregory\git\a\commons-bcel\target\test-classes, path = 
C:\Users\ggregory\git\a\commons-bcel\target\test-classes\ossfuzz\issue51980\Test.class
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
(MojoExecutor.java:347)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
(MojoExecutor.java:330)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:175)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 
(MojoExecutor.java:76)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run 
(MojoExecutor.java:163)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute 
(DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:160)
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:827)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:272)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:195)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke 
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke 
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced 
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch 
(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode 
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main 
(Launcher.java:347)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
default-cli of goal org.cyclonedx:cyclonedx-maven-plugin:2.7.7:makeAggregateBom 
failed: Unsupported class file major version 1025 from directory = 
C:\Users\ggregory\git\a\commons-bcel\target\test-classes, path = 
C:\Users\ggregory\git\a\commons-bcel\target\test-classes\ossfuzz\issue51980\Test.class
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
(DefaultBuildPluginManager.java:133)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
(MojoExecutor.java:342)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
(MojoExecutor.java:330)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:213)

[jira] [Updated] (MSHARED-1247) maven-dependency-analyzer java.lang.RuntimeException: Unknown constant pool type '17'

[Gary D. Gregory (Jira)]

 [ 
https://issues.apache.org/jira/browse/MSHARED-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gary D. Gregory updated MSHARED-1247:
-
Summary: maven-dependency-analyzer java.lang.RuntimeException: Unknown 
constant pool type '17'  (was: java.lang.RuntimeException: Unknown constant 
pool type '17')

> maven-dependency-analyzer java.lang.RuntimeException: Unknown constant pool 
> type '17'
> -
>
> Key: MSHARED-1247
> URL: https://issues.apache.org/jira/browse/MSHARED-1247
> Project: Maven Shared Components
>  Issue Type: Bug
>  Components: maven-dependency-analyzer
>Affects Versions: maven-dependency-analyzer-1.13.1
> Environment: Apache Maven 3.9.1 
> (2e178502fcdbffc201671fb2537d0cb4b4cc58f8)
> Maven home: C:\java\apache-maven-3.9.1
> Java version: 1.8.0_362, vendor: Temurin, runtime: C:\Program Files\Eclipse 
> Adoptium\jdk-8.0.362.9-hotspot\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> Microsoft Windows [Version 10.0.19044.2728]
>Reporter: Gary D. Gregory
>Priority: Blocker
> Fix For: maven-dependency-analyzer-1.13.2
>
>
> You get the exception:
> {noformat}
> ...
> Caused by: java.lang.RuntimeException: Unknown constant pool type '17'
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ConstantPoolParser.parseConstantPoolClassReferences
>  (ConstantPoolParser.java:120)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ConstantPoolParser.getConstantPoolClassReferences
>  (ConstantPoolParser.java:104)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.DependencyClassFileVisitor.visitClass
>  (DependencyClassFileVisitor.java:59)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
> (ClassFileVisitorUtils.java:114)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
> (ClassFileVisitorUtils.java:106)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.acceptDirectory
>  (ClassFileVisitorUtils.java:97)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.accept 
> (ClassFileVisitorUtils.java:59)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ASMDependencyAnalyzer.analyze 
> (ASMDependencyAnalyzer.java:43)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildDependencyClasses
>  (DefaultProjectDependencyAnalyzer.java:206)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildTestDependencyClasses
>  (DefaultProjectDependencyAnalyzer.java:200)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.analyze
>  (DefaultProjectDependencyAnalyzer.java:68)
> at org.cyclonedx.maven.CycloneDxMojo.doProjectDependencyAnalysis 
> (CycloneDxMojo.java:86)
> at 
> org.cyclonedx.maven.CycloneDxAggregateMojo.extractComponentsAndDependencies 
> (CycloneDxAggregateMojo.java:130)
> at org.cyclonedx.maven.BaseCycloneDxMojo.execute 
> (BaseCycloneDxMojo.java:258)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:342)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
> (MojoExecutor.java:330)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:175)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 
> (MojoExecutor.java:76)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run 
> (MojoExecutor.java:163)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute 
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:160)
> 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:827)
> at 

[jira] [Commented] (MSHARED-1247) java.lang.RuntimeException: Unknown constant pool type '17'

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MSHARED-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17717967#comment-17717967
 ] 

Gary D. Gregory commented on MSHARED-1247:
--

Hi [~sjaranowski] 

"But we should think again ... we can get IllegalArgumentException also when 
class will be ok, but not supported by current asm version ...
So we lost information that processed classes are not supported by the current 
version of analyzer/asm"

I would hope that logging messages that are precise enough will help users 
understand what case they've encountered.

 

> java.lang.RuntimeException: Unknown constant pool type '17'
> ---
>
> Key: MSHARED-1247
> URL: https://issues.apache.org/jira/browse/MSHARED-1247
> Project: Maven Shared Components
>  Issue Type: Bug
>  Components: maven-dependency-analyzer
>Affects Versions: maven-dependency-analyzer-1.13.1
> Environment: Apache Maven 3.9.1 
> (2e178502fcdbffc201671fb2537d0cb4b4cc58f8)
> Maven home: C:\java\apache-maven-3.9.1
> Java version: 1.8.0_362, vendor: Temurin, runtime: C:\Program Files\Eclipse 
> Adoptium\jdk-8.0.362.9-hotspot\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> Microsoft Windows [Version 10.0.19044.2728]
>Reporter: Gary D. Gregory
>Priority: Blocker
> Fix For: maven-dependency-analyzer-1.13.2
>
>
> You get the exception:
> {noformat}
> ...
> Caused by: java.lang.RuntimeException: Unknown constant pool type '17'
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ConstantPoolParser.parseConstantPoolClassReferences
>  (ConstantPoolParser.java:120)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ConstantPoolParser.getConstantPoolClassReferences
>  (ConstantPoolParser.java:104)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.DependencyClassFileVisitor.visitClass
>  (DependencyClassFileVisitor.java:59)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
> (ClassFileVisitorUtils.java:114)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
> (ClassFileVisitorUtils.java:106)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.acceptDirectory
>  (ClassFileVisitorUtils.java:97)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.accept 
> (ClassFileVisitorUtils.java:59)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ASMDependencyAnalyzer.analyze 
> (ASMDependencyAnalyzer.java:43)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildDependencyClasses
>  (DefaultProjectDependencyAnalyzer.java:206)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildTestDependencyClasses
>  (DefaultProjectDependencyAnalyzer.java:200)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.analyze
>  (DefaultProjectDependencyAnalyzer.java:68)
> at org.cyclonedx.maven.CycloneDxMojo.doProjectDependencyAnalysis 
> (CycloneDxMojo.java:86)
> at 
> org.cyclonedx.maven.CycloneDxAggregateMojo.extractComponentsAndDependencies 
> (CycloneDxAggregateMojo.java:130)
> at org.cyclonedx.maven.BaseCycloneDxMojo.execute 
> (BaseCycloneDxMojo.java:258)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:342)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
> (MojoExecutor.java:330)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:175)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 
> (MojoExecutor.java:76)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run 
> (MojoExecutor.java:163)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute 
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:160)
> 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 

[jira] [Commented] (MSHARED-1247) java.lang.RuntimeException: Unknown constant pool type '17'

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MSHARED-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17717912#comment-17717912
 ] 

Gary D. Gregory commented on MSHARED-1247:
--

Hi [~sjaranowski]
I feel that seems like a good idea. 
Is that something I should add to my PR, something you will do, or should I 
provide a separate PR?
An argument for a separate PR and ticket could be made since this now is about 
a corrupted class file as opposed to missing Java 11 support. Please advise :)

> java.lang.RuntimeException: Unknown constant pool type '17'
> ---
>
> Key: MSHARED-1247
> URL: https://issues.apache.org/jira/browse/MSHARED-1247
> Project: Maven Shared Components
>  Issue Type: Bug
>  Components: maven-dependency-analyzer
>Affects Versions: maven-dependency-analyzer-1.13.1
> Environment: Apache Maven 3.9.1 
> (2e178502fcdbffc201671fb2537d0cb4b4cc58f8)
> Maven home: C:\java\apache-maven-3.9.1
> Java version: 1.8.0_362, vendor: Temurin, runtime: C:\Program Files\Eclipse 
> Adoptium\jdk-8.0.362.9-hotspot\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> Microsoft Windows [Version 10.0.19044.2728]
>Reporter: Gary D. Gregory
>Priority: Blocker
>
> You get the exception:
> {noformat}
> ...
> Caused by: java.lang.RuntimeException: Unknown constant pool type '17'
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ConstantPoolParser.parseConstantPoolClassReferences
>  (ConstantPoolParser.java:120)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ConstantPoolParser.getConstantPoolClassReferences
>  (ConstantPoolParser.java:104)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.DependencyClassFileVisitor.visitClass
>  (DependencyClassFileVisitor.java:59)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
> (ClassFileVisitorUtils.java:114)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
> (ClassFileVisitorUtils.java:106)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.acceptDirectory
>  (ClassFileVisitorUtils.java:97)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.accept 
> (ClassFileVisitorUtils.java:59)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ASMDependencyAnalyzer.analyze 
> (ASMDependencyAnalyzer.java:43)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildDependencyClasses
>  (DefaultProjectDependencyAnalyzer.java:206)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildTestDependencyClasses
>  (DefaultProjectDependencyAnalyzer.java:200)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.analyze
>  (DefaultProjectDependencyAnalyzer.java:68)
> at org.cyclonedx.maven.CycloneDxMojo.doProjectDependencyAnalysis 
> (CycloneDxMojo.java:86)
> at 
> org.cyclonedx.maven.CycloneDxAggregateMojo.extractComponentsAndDependencies 
> (CycloneDxAggregateMojo.java:130)
> at org.cyclonedx.maven.BaseCycloneDxMojo.execute 
> (BaseCycloneDxMojo.java:258)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:342)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
> (MojoExecutor.java:330)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:175)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 
> (MojoExecutor.java:76)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run 
> (MojoExecutor.java:163)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute 
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:160)
> 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 

[jira] [Comment Edited] (MSHARED-1247) java.lang.RuntimeException: Unknown constant pool type '17'

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MSHARED-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17717722#comment-17717722
 ] 

Gary D. Gregory edited comment on MSHARED-1247 at 4/28/23 8:50 PM:
---

[~sjaranowski]

WRT ossfuzz/issue51980/Test.class:

A related problem is that 
{{ConstantPoolParser.parseConstantPoolClassReferences(ByteBuffer)}} throws a 
{{RuntimeException}} which is an anti-pattern; as opposed to an better 
unchecked exception like {{{}IllegalArgumentException{}}}, 
{{{}IllegalStateException{}}}, or {{{}UncheckedIOException{}}}.

IIRC, if in the PR, I change {{ClassFileVisitorUtils.acceptDirectory(File, 
ClassFileVisitor)}} to rethrow the {{RuntimeException}} as an {{IOException}}, 
then any error is logged and does not blow up the Maven run (the method already 
throws {{IOException}}).


was (Author: garydgregory):
WRT ossfuzz/issue51980/Test.class:

A related problem is that 
{{ConstantPoolParser.parseConstantPoolClassReferences(ByteBuffer)}} throws a 
{{RuntimeException}} which is an anti-pattern; as opposed to an better 
unchecked exception like {{{}IllegalArgumentException{}}}, 
{{{}IllegalStateException{}}}, or {{{}UncheckedIOException{}}}.

IIRC, if in the PR, I change {{ClassFileVisitorUtils.acceptDirectory(File, 
ClassFileVisitor)}} to rethrow the {{RuntimeException}} as an {{IOException}}, 
then any error is logged and does not blow up the Maven run (the method already 
throws {{IOException}}).

> java.lang.RuntimeException: Unknown constant pool type '17'
> ---
>
> Key: MSHARED-1247
> URL: https://issues.apache.org/jira/browse/MSHARED-1247
> Project: Maven Shared Components
>  Issue Type: Bug
>  Components: maven-dependency-analyzer
>Affects Versions: maven-dependency-analyzer-1.13.1
> Environment: Apache Maven 3.9.1 
> (2e178502fcdbffc201671fb2537d0cb4b4cc58f8)
> Maven home: C:\java\apache-maven-3.9.1
> Java version: 1.8.0_362, vendor: Temurin, runtime: C:\Program Files\Eclipse 
> Adoptium\jdk-8.0.362.9-hotspot\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> Microsoft Windows [Version 10.0.19044.2728]
>Reporter: Gary D. Gregory
>Priority: Blocker
>
> You get the exception:
> {noformat}
> ...
> Caused by: java.lang.RuntimeException: Unknown constant pool type '17'
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ConstantPoolParser.parseConstantPoolClassReferences
>  (ConstantPoolParser.java:120)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ConstantPoolParser.getConstantPoolClassReferences
>  (ConstantPoolParser.java:104)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.DependencyClassFileVisitor.visitClass
>  (DependencyClassFileVisitor.java:59)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
> (ClassFileVisitorUtils.java:114)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
> (ClassFileVisitorUtils.java:106)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.acceptDirectory
>  (ClassFileVisitorUtils.java:97)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.accept 
> (ClassFileVisitorUtils.java:59)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ASMDependencyAnalyzer.analyze 
> (ASMDependencyAnalyzer.java:43)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildDependencyClasses
>  (DefaultProjectDependencyAnalyzer.java:206)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildTestDependencyClasses
>  (DefaultProjectDependencyAnalyzer.java:200)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.analyze
>  (DefaultProjectDependencyAnalyzer.java:68)
> at org.cyclonedx.maven.CycloneDxMojo.doProjectDependencyAnalysis 
> (CycloneDxMojo.java:86)
> at 
> org.cyclonedx.maven.CycloneDxAggregateMojo.extractComponentsAndDependencies 
> (CycloneDxAggregateMojo.java:130)
> at org.cyclonedx.maven.BaseCycloneDxMojo.execute 
> (BaseCycloneDxMojo.java:258)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:342)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
> (MojoExecutor.java:330)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:175)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 
> (MojoExecutor.java:76)
> at 

[jira] [Comment Edited] (MSHARED-1247) java.lang.RuntimeException: Unknown constant pool type '17'

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MSHARED-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17717722#comment-17717722
 ] 

Gary D. Gregory edited comment on MSHARED-1247 at 4/28/23 3:22 PM:
---

WRT ossfuzz/issue51980/Test.class:

A related problem is that 
{{ConstantPoolParser.parseConstantPoolClassReferences(ByteBuffer)}} throws a 
{{RuntimeException}} which is an anti-pattern; as opposed to an better 
unchecked exception like {{{}IllegalArgumentException{}}}, 
{{{}IllegalStateException{}}}, or {{{}UncheckedIOException{}}}.

IIRC, if in the PR, I change {{ClassFileVisitorUtils.acceptDirectory(File, 
ClassFileVisitor)}} to rethrow the {{RuntimeException}} as an {{IOException}}, 
then any error is logged and does not blow up the Maven run (the method already 
throws {{IOException}}).


was (Author: garydgregory):
A related problem is that 
{{ConstantPoolParser.parseConstantPoolClassReferences(ByteBuffer)}} throws a 
{{RuntimeException}} which is an anti-pattern; as opposed to an better 
unchecked exception like {{{}IllegalArgumentException{}}}, 
{{{}IllegalStateException{}}}, or {{{}UncheckedIOException{}}}.

IIRC, if in the PR, I change {{ClassFileVisitorUtils.acceptDirectory(File, 
ClassFileVisitor)}} to rethrow the {{RuntimeException}} as an {{IOException}}, 
then any error is logged and does not blow up the Maven run (the method already 
throws {{IOException}}).

> java.lang.RuntimeException: Unknown constant pool type '17'
> ---
>
> Key: MSHARED-1247
> URL: https://issues.apache.org/jira/browse/MSHARED-1247
> Project: Maven Shared Components
>  Issue Type: Bug
>  Components: maven-dependency-analyzer
>Affects Versions: maven-dependency-analyzer-1.13.1
> Environment: Apache Maven 3.9.1 
> (2e178502fcdbffc201671fb2537d0cb4b4cc58f8)
> Maven home: C:\java\apache-maven-3.9.1
> Java version: 1.8.0_362, vendor: Temurin, runtime: C:\Program Files\Eclipse 
> Adoptium\jdk-8.0.362.9-hotspot\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> Microsoft Windows [Version 10.0.19044.2728]
>Reporter: Gary D. Gregory
>Priority: Blocker
>
> You get the exception:
> {noformat}
> ...
> Caused by: java.lang.RuntimeException: Unknown constant pool type '17'
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ConstantPoolParser.parseConstantPoolClassReferences
>  (ConstantPoolParser.java:120)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ConstantPoolParser.getConstantPoolClassReferences
>  (ConstantPoolParser.java:104)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.DependencyClassFileVisitor.visitClass
>  (DependencyClassFileVisitor.java:59)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
> (ClassFileVisitorUtils.java:114)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
> (ClassFileVisitorUtils.java:106)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.acceptDirectory
>  (ClassFileVisitorUtils.java:97)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.accept 
> (ClassFileVisitorUtils.java:59)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ASMDependencyAnalyzer.analyze 
> (ASMDependencyAnalyzer.java:43)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildDependencyClasses
>  (DefaultProjectDependencyAnalyzer.java:206)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildTestDependencyClasses
>  (DefaultProjectDependencyAnalyzer.java:200)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.analyze
>  (DefaultProjectDependencyAnalyzer.java:68)
> at org.cyclonedx.maven.CycloneDxMojo.doProjectDependencyAnalysis 
> (CycloneDxMojo.java:86)
> at 
> org.cyclonedx.maven.CycloneDxAggregateMojo.extractComponentsAndDependencies 
> (CycloneDxAggregateMojo.java:130)
> at org.cyclonedx.maven.BaseCycloneDxMojo.execute 
> (BaseCycloneDxMojo.java:258)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:342)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
> (MojoExecutor.java:330)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:175)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 
> (MojoExecutor.java:76)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run 
> 

[jira] [Comment Edited] (MSHARED-1247) java.lang.RuntimeException: Unknown constant pool type '17'

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MSHARED-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17717722#comment-17717722
 ] 

Gary D. Gregory edited comment on MSHARED-1247 at 4/28/23 3:22 PM:
---

A related problem is that 
{{ConstantPoolParser.parseConstantPoolClassReferences(ByteBuffer)}} throws a 
{{RuntimeException}} which is an anti-pattern; as opposed to an better 
unchecked exception like {{{}IllegalArgumentException{}}}, 
{{{}IllegalStateException{}}}, or {{{}UncheckedIOException{}}}.

IIRC, if in the PR, I change {{ClassFileVisitorUtils.acceptDirectory(File, 
ClassFileVisitor)}} to rethrow the {{RuntimeException}} as an {{IOException}}, 
then any error is logged and does not blow up the Maven run (the method already 
throws {{IOException}}).


was (Author: garydgregory):
A related problem is that 
{{ConstantPoolParser.parseConstantPoolClassReferences(ByteBuffer)}} throws a 
{{RuntimeException}} which is an anti-pattern; as opposed to an better 
unchecked exception like {{{}IllegalArgumentException{}}}, 
{{{}IllegalStateException{}}}, or {{{}UncheckedIOException{}}}.

IIRC, if in the PR, I change {{ClassFileVisitorUtils.acceptDirectory(File, 
ClassFileVisitor)}} to rethrow the {{RuntimeException}} as an IOException, then 
any error is logged and does not blow up the Maven run (the method already 
throws {{{}IOException{}}}).

> java.lang.RuntimeException: Unknown constant pool type '17'
> ---
>
> Key: MSHARED-1247
> URL: https://issues.apache.org/jira/browse/MSHARED-1247
> Project: Maven Shared Components
>  Issue Type: Bug
>  Components: maven-dependency-analyzer
>Affects Versions: maven-dependency-analyzer-1.13.1
> Environment: Apache Maven 3.9.1 
> (2e178502fcdbffc201671fb2537d0cb4b4cc58f8)
> Maven home: C:\java\apache-maven-3.9.1
> Java version: 1.8.0_362, vendor: Temurin, runtime: C:\Program Files\Eclipse 
> Adoptium\jdk-8.0.362.9-hotspot\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> Microsoft Windows [Version 10.0.19044.2728]
>Reporter: Gary D. Gregory
>Priority: Blocker
>
> You get the exception:
> {noformat}
> ...
> Caused by: java.lang.RuntimeException: Unknown constant pool type '17'
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ConstantPoolParser.parseConstantPoolClassReferences
>  (ConstantPoolParser.java:120)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ConstantPoolParser.getConstantPoolClassReferences
>  (ConstantPoolParser.java:104)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.DependencyClassFileVisitor.visitClass
>  (DependencyClassFileVisitor.java:59)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
> (ClassFileVisitorUtils.java:114)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
> (ClassFileVisitorUtils.java:106)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.acceptDirectory
>  (ClassFileVisitorUtils.java:97)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.accept 
> (ClassFileVisitorUtils.java:59)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ASMDependencyAnalyzer.analyze 
> (ASMDependencyAnalyzer.java:43)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildDependencyClasses
>  (DefaultProjectDependencyAnalyzer.java:206)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildTestDependencyClasses
>  (DefaultProjectDependencyAnalyzer.java:200)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.analyze
>  (DefaultProjectDependencyAnalyzer.java:68)
> at org.cyclonedx.maven.CycloneDxMojo.doProjectDependencyAnalysis 
> (CycloneDxMojo.java:86)
> at 
> org.cyclonedx.maven.CycloneDxAggregateMojo.extractComponentsAndDependencies 
> (CycloneDxAggregateMojo.java:130)
> at org.cyclonedx.maven.BaseCycloneDxMojo.execute 
> (BaseCycloneDxMojo.java:258)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:342)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
> (MojoExecutor.java:330)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:175)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 
> (MojoExecutor.java:76)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run 
> (MojoExecutor.java:163)
> at 

[jira] [Comment Edited] (MSHARED-1247) java.lang.RuntimeException: Unknown constant pool type '17'

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MSHARED-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17717722#comment-17717722
 ] 

Gary D. Gregory edited comment on MSHARED-1247 at 4/28/23 3:21 PM:
---

A related problem is that 
{{ConstantPoolParser.parseConstantPoolClassReferences(ByteBuffer)}} throws a 
{{RuntimeException}} which is an anti-pattern; as opposed to an better 
unchecked exception like {{{}IllegalArgumentException{}}}, 
{{{}IllegalStateException{}}}, or {{{}UncheckedIOException{}}}.

IIRC, if in the PR, I change {{ClassFileVisitorUtils.acceptDirectory(File, 
ClassFileVisitor)}} to rethrow the {{RuntimeException}} as an IOException, then 
any error is logged and does not blow up the Maven run (the method already 
throws {{{}IOException{}}}).


was (Author: garydgregory):
A related problem is that 
{{org.apache.maven.shared.dependency.analyzer.asm.ConstantPoolParser.parseConstantPoolClassReferences(ByteBuffer)}}
 throws a {{RuntimeException}} which is an anti-pattern; as opposed to an 
better unchecked exception like {{{}IllegalArgumentException{}}}, 
{{{}IllegalStateException{}}}, or {{{}UncheckedIOException{}}}.

IIRC, if in the PR, I change {{ClassFileVisitorUtils.acceptDirectory(File, 
ClassFileVisitor)}} to rethrow the {{RuntimeException}} as an IOException, then 
any error is logged and does not blow up the Maven run (the method already 
throws {{{}IOException{}}}).

> java.lang.RuntimeException: Unknown constant pool type '17'
> ---
>
> Key: MSHARED-1247
> URL: https://issues.apache.org/jira/browse/MSHARED-1247
> Project: Maven Shared Components
>  Issue Type: Bug
>  Components: maven-dependency-analyzer
>Affects Versions: maven-dependency-analyzer-1.13.1
> Environment: Apache Maven 3.9.1 
> (2e178502fcdbffc201671fb2537d0cb4b4cc58f8)
> Maven home: C:\java\apache-maven-3.9.1
> Java version: 1.8.0_362, vendor: Temurin, runtime: C:\Program Files\Eclipse 
> Adoptium\jdk-8.0.362.9-hotspot\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> Microsoft Windows [Version 10.0.19044.2728]
>Reporter: Gary D. Gregory
>Priority: Blocker
>
> You get the exception:
> {noformat}
> ...
> Caused by: java.lang.RuntimeException: Unknown constant pool type '17'
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ConstantPoolParser.parseConstantPoolClassReferences
>  (ConstantPoolParser.java:120)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ConstantPoolParser.getConstantPoolClassReferences
>  (ConstantPoolParser.java:104)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.DependencyClassFileVisitor.visitClass
>  (DependencyClassFileVisitor.java:59)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
> (ClassFileVisitorUtils.java:114)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
> (ClassFileVisitorUtils.java:106)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.acceptDirectory
>  (ClassFileVisitorUtils.java:97)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.accept 
> (ClassFileVisitorUtils.java:59)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ASMDependencyAnalyzer.analyze 
> (ASMDependencyAnalyzer.java:43)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildDependencyClasses
>  (DefaultProjectDependencyAnalyzer.java:206)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildTestDependencyClasses
>  (DefaultProjectDependencyAnalyzer.java:200)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.analyze
>  (DefaultProjectDependencyAnalyzer.java:68)
> at org.cyclonedx.maven.CycloneDxMojo.doProjectDependencyAnalysis 
> (CycloneDxMojo.java:86)
> at 
> org.cyclonedx.maven.CycloneDxAggregateMojo.extractComponentsAndDependencies 
> (CycloneDxAggregateMojo.java:130)
> at org.cyclonedx.maven.BaseCycloneDxMojo.execute 
> (BaseCycloneDxMojo.java:258)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:342)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
> (MojoExecutor.java:330)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:175)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 
> (MojoExecutor.java:76)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run 

[jira] [Commented] (MSHARED-1247) java.lang.RuntimeException: Unknown constant pool type '17'

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MSHARED-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17717722#comment-17717722
 ] 

Gary D. Gregory commented on MSHARED-1247:
--

A related problem is that 
{{org.apache.maven.shared.dependency.analyzer.asm.ConstantPoolParser.parseConstantPoolClassReferences(ByteBuffer)}}
 throws a {{RuntimeException}} which is an anti-pattern; as opposed to an 
better unchecked exception like {{{}IllegalArgumentException{}}}, 
{{{}IllegalStateException{}}}, or {{{}UncheckedIOException{}}}.

IIRC, if in the PR, I change {{ClassFileVisitorUtils.acceptDirectory(File, 
ClassFileVisitor)}} to rethrow the {{RuntimeException}} as an IOException, then 
any error is logged and does not blow up the Maven run (the method already 
throws {{{}IOException{}}}).

> java.lang.RuntimeException: Unknown constant pool type '17'
> ---
>
> Key: MSHARED-1247
> URL: https://issues.apache.org/jira/browse/MSHARED-1247
> Project: Maven Shared Components
>  Issue Type: Bug
>  Components: maven-dependency-analyzer
>Affects Versions: maven-dependency-analyzer-1.13.1
> Environment: Apache Maven 3.9.1 
> (2e178502fcdbffc201671fb2537d0cb4b4cc58f8)
> Maven home: C:\java\apache-maven-3.9.1
> Java version: 1.8.0_362, vendor: Temurin, runtime: C:\Program Files\Eclipse 
> Adoptium\jdk-8.0.362.9-hotspot\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> Microsoft Windows [Version 10.0.19044.2728]
>Reporter: Gary D. Gregory
>Priority: Blocker
>
> You get the exception:
> {noformat}
> ...
> Caused by: java.lang.RuntimeException: Unknown constant pool type '17'
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ConstantPoolParser.parseConstantPoolClassReferences
>  (ConstantPoolParser.java:120)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ConstantPoolParser.getConstantPoolClassReferences
>  (ConstantPoolParser.java:104)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.DependencyClassFileVisitor.visitClass
>  (DependencyClassFileVisitor.java:59)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
> (ClassFileVisitorUtils.java:114)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
> (ClassFileVisitorUtils.java:106)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.acceptDirectory
>  (ClassFileVisitorUtils.java:97)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.accept 
> (ClassFileVisitorUtils.java:59)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ASMDependencyAnalyzer.analyze 
> (ASMDependencyAnalyzer.java:43)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildDependencyClasses
>  (DefaultProjectDependencyAnalyzer.java:206)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildTestDependencyClasses
>  (DefaultProjectDependencyAnalyzer.java:200)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.analyze
>  (DefaultProjectDependencyAnalyzer.java:68)
> at org.cyclonedx.maven.CycloneDxMojo.doProjectDependencyAnalysis 
> (CycloneDxMojo.java:86)
> at 
> org.cyclonedx.maven.CycloneDxAggregateMojo.extractComponentsAndDependencies 
> (CycloneDxAggregateMojo.java:130)
> at org.cyclonedx.maven.BaseCycloneDxMojo.execute 
> (BaseCycloneDxMojo.java:258)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:342)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
> (MojoExecutor.java:330)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:175)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 
> (MojoExecutor.java:76)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run 
> (MojoExecutor.java:163)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute 
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:160)
> 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 

[jira] [Commented] (MSHARED-1247) java.lang.RuntimeException: Unknown constant pool type '17'

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MSHARED-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17717718#comment-17717718
 ] 

Gary D. Gregory commented on MSHARED-1247:
--

Hi [~sjaranowski] 

Thank you for the quick feedback.

I added a test to the PR.

Yeah, {{cyclonedx}}  I suppose a downstream project can depend on any jar 
files test or not, and end up delivering it. That's the only reason I can 
imagine for analyzing test code and resources.

> java.lang.RuntimeException: Unknown constant pool type '17'
> ---
>
> Key: MSHARED-1247
> URL: https://issues.apache.org/jira/browse/MSHARED-1247
> Project: Maven Shared Components
>  Issue Type: Bug
>  Components: maven-dependency-analyzer
>Affects Versions: maven-dependency-analyzer-1.13.1
> Environment: Apache Maven 3.9.1 
> (2e178502fcdbffc201671fb2537d0cb4b4cc58f8)
> Maven home: C:\java\apache-maven-3.9.1
> Java version: 1.8.0_362, vendor: Temurin, runtime: C:\Program Files\Eclipse 
> Adoptium\jdk-8.0.362.9-hotspot\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> Microsoft Windows [Version 10.0.19044.2728]
>Reporter: Gary D. Gregory
>Priority: Blocker
>
> You get the exception:
> {noformat}
> ...
> Caused by: java.lang.RuntimeException: Unknown constant pool type '17'
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ConstantPoolParser.parseConstantPoolClassReferences
>  (ConstantPoolParser.java:120)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ConstantPoolParser.getConstantPoolClassReferences
>  (ConstantPoolParser.java:104)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.DependencyClassFileVisitor.visitClass
>  (DependencyClassFileVisitor.java:59)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
> (ClassFileVisitorUtils.java:114)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
> (ClassFileVisitorUtils.java:106)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.acceptDirectory
>  (ClassFileVisitorUtils.java:97)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.accept 
> (ClassFileVisitorUtils.java:59)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ASMDependencyAnalyzer.analyze 
> (ASMDependencyAnalyzer.java:43)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildDependencyClasses
>  (DefaultProjectDependencyAnalyzer.java:206)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildTestDependencyClasses
>  (DefaultProjectDependencyAnalyzer.java:200)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.analyze
>  (DefaultProjectDependencyAnalyzer.java:68)
> at org.cyclonedx.maven.CycloneDxMojo.doProjectDependencyAnalysis 
> (CycloneDxMojo.java:86)
> at 
> org.cyclonedx.maven.CycloneDxAggregateMojo.extractComponentsAndDependencies 
> (CycloneDxAggregateMojo.java:130)
> at org.cyclonedx.maven.BaseCycloneDxMojo.execute 
> (BaseCycloneDxMojo.java:258)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:342)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
> (MojoExecutor.java:330)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:175)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 
> (MojoExecutor.java:76)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run 
> (MojoExecutor.java:163)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute 
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:160)
> 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 

[jira] [Commented] (MSHARED-1247) java.lang.RuntimeException: Unknown constant pool type '17'

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MSHARED-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17717668#comment-17717668
 ] 

Gary D. Gregory commented on MSHARED-1247:
--

Here is an attempt at fixing this issue: 
[https://github.com/apache/maven-dependency-analyzer/pull/88]

It might not be complete or there might be other issues.

If I run "mvn clean install" and then update BCEL's pom.xml to:

{noformat}
diff --git a/pom.xml b/pom.xml
index 7ebef432..4b3bd4e1 100644
--- a/pom.xml
+++ b/pom.xml
@@ -27,7 +27,7 @@
   
 org.apache.commons
 commons-parent
-56
+57^M
   

   org.apache.bcel
@@ -210,6 +210,17 @@
   
 clean verify apache-rat:check japicmp:cmp checkstyle:check 
pmd:check spotbugs:check javadoc:javadoc
 
+  ^M
+org.cyclonedx^M
+cyclonedx-maven-plugin^M
+^M
+  ^M
+org.apache.maven.shared^M
+maven-dependency-analyzer^M
+1.13.2-SNAPSHOT^M
+  ^M
+   ^M
+  ^M
   
 org.apache.felix
 maven-bundle-plugin
{noformat}

I then get a different error that suggests the parsing is still wrong: 
{noformat}
Caused by: java.lang.IllegalArgumentException: Unsupported class file major 
version 1025
at org.objectweb.asm.ClassReader. (ClassReader.java:199)
at org.objectweb.asm.ClassReader. (ClassReader.java:180)
at org.objectweb.asm.ClassReader. (ClassReader.java:166)
at 
org.apache.maven.shared.dependency.analyzer.asm.DependencyClassFileVisitor.visitClass
 (DependencyClassFileVisitor.java:57)
at 
org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
(ClassFileVisitorUtils.java:114)
at 
org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
(ClassFileVisitorUtils.java:106)
at 
org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.acceptDirectory
 (ClassFileVisitorUtils.java:97)
at org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.accept 
(ClassFileVisitorUtils.java:59)
at 
org.apache.maven.shared.dependency.analyzer.asm.ASMDependencyAnalyzer.analyze 
(ASMDependencyAnalyzer.java:43)
{noformat}

Any suggestions or fix?


> java.lang.RuntimeException: Unknown constant pool type '17'
> ---
>
> Key: MSHARED-1247
> URL: https://issues.apache.org/jira/browse/MSHARED-1247
> Project: Maven Shared Components
>  Issue Type: Bug
>  Components: maven-dependency-analyzer
>Affects Versions: maven-dependency-analyzer-1.13.1
> Environment: Apache Maven 3.9.1 
> (2e178502fcdbffc201671fb2537d0cb4b4cc58f8)
> Maven home: C:\java\apache-maven-3.9.1
> Java version: 1.8.0_362, vendor: Temurin, runtime: C:\Program Files\Eclipse 
> Adoptium\jdk-8.0.362.9-hotspot\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> Microsoft Windows [Version 10.0.19044.2728]
>Reporter: Gary D. Gregory
>Priority: Blocker
>
> You get the exception:
> {noformat}
> ...
> Caused by: java.lang.RuntimeException: Unknown constant pool type '17'
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ConstantPoolParser.parseConstantPoolClassReferences
>  (ConstantPoolParser.java:120)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ConstantPoolParser.getConstantPoolClassReferences
>  (ConstantPoolParser.java:104)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.DependencyClassFileVisitor.visitClass
>  (DependencyClassFileVisitor.java:59)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
> (ClassFileVisitorUtils.java:114)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
> (ClassFileVisitorUtils.java:106)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.acceptDirectory
>  (ClassFileVisitorUtils.java:97)
> at 
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.accept 
> (ClassFileVisitorUtils.java:59)
> at 
> org.apache.maven.shared.dependency.analyzer.asm.ASMDependencyAnalyzer.analyze 
> (ASMDependencyAnalyzer.java:43)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildDependencyClasses
>  (DefaultProjectDependencyAnalyzer.java:206)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildTestDependencyClasses
>  (DefaultProjectDependencyAnalyzer.java:200)
> at 
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.analyze
>  (DefaultProjectDependencyAnalyzer.java:68)
> at org.cyclonedx.maven.CycloneDxMojo.doProjectDependencyAnalysis 
> (CycloneDxMojo.java:86)
> at 
> 

[jira] [Created] (MSHARED-1247) java.lang.RuntimeException: Unknown constant pool type '17'

[Gary D. Gregory (Jira)]

Gary D. Gregory created MSHARED-1247:


 Summary: java.lang.RuntimeException: Unknown constant pool type 
'17'
 Key: MSHARED-1247
 URL: https://issues.apache.org/jira/browse/MSHARED-1247
 Project: Maven Shared Components
  Issue Type: Bug
  Components: maven-dependency-analyzer
Affects Versions: maven-dependency-analyzer-1.13.1
 Environment: Apache Maven 3.9.1 
(2e178502fcdbffc201671fb2537d0cb4b4cc58f8)
Maven home: C:\java\apache-maven-3.9.1
Java version: 1.8.0_362, vendor: Temurin, runtime: C:\Program Files\Eclipse 
Adoptium\jdk-8.0.362.9-hotspot\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

Microsoft Windows [Version 10.0.19044.2728]
Reporter: Gary D. Gregory


You get the exception:
{noformat}
...
Caused by: java.lang.RuntimeException: Unknown constant pool type '17'
at 
org.apache.maven.shared.dependency.analyzer.asm.ConstantPoolParser.parseConstantPoolClassReferences
 (ConstantPoolParser.java:120)
at 
org.apache.maven.shared.dependency.analyzer.asm.ConstantPoolParser.getConstantPoolClassReferences
 (ConstantPoolParser.java:104)
at 
org.apache.maven.shared.dependency.analyzer.asm.DependencyClassFileVisitor.visitClass
 (DependencyClassFileVisitor.java:59)
at 
org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
(ClassFileVisitorUtils.java:114)
at 
org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
(ClassFileVisitorUtils.java:106)
at 
org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.acceptDirectory
 (ClassFileVisitorUtils.java:97)
at org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.accept 
(ClassFileVisitorUtils.java:59)
at 
org.apache.maven.shared.dependency.analyzer.asm.ASMDependencyAnalyzer.analyze 
(ASMDependencyAnalyzer.java:43)
at 
org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildDependencyClasses
 (DefaultProjectDependencyAnalyzer.java:206)
at 
org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildTestDependencyClasses
 (DefaultProjectDependencyAnalyzer.java:200)
at 
org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.analyze
 (DefaultProjectDependencyAnalyzer.java:68)
at org.cyclonedx.maven.CycloneDxMojo.doProjectDependencyAnalysis 
(CycloneDxMojo.java:86)
at 
org.cyclonedx.maven.CycloneDxAggregateMojo.extractComponentsAndDependencies 
(CycloneDxAggregateMojo.java:130)
at org.cyclonedx.maven.BaseCycloneDxMojo.execute 
(BaseCycloneDxMojo.java:258)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
(DefaultBuildPluginManager.java:126)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
(MojoExecutor.java:342)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
(MojoExecutor.java:330)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:175)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 
(MojoExecutor.java:76)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run 
(MojoExecutor.java:163)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute 
(DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:160)
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:827)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:272)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:195)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke 
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke 
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced 
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch 
(Launcher.java:225)
at 

[jira] [Created] (MCOMPILER-534) Broken command line generated on Java 8 when maven.compiler.release is set

[Gary D. Gregory (Jira)]

Gary D. Gregory created MCOMPILER-534:
-

 Summary: Broken command line generated on Java 8 when 
maven.compiler.release is set
 Key: MCOMPILER-534
 URL: https://issues.apache.org/jira/browse/MCOMPILER-534
 Project: Maven Compiler Plugin
  Issue Type: Bug
Affects Versions: 3.11.0
 Environment: Apache Maven 3.9.1 
(2e178502fcdbffc201671fb2537d0cb4b4cc58f8)
Maven home: /usr/local/Cellar/maven/3.9.1/libexec
Java version: 1.8.0_362, vendor: Homebrew, runtime: 
/usr/local/Cellar/openjdk@8/1.8.0+362/libexec/openjdk.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "13.3.1", arch: "x86_64", family: "mac"

Darwin  22.4.0 Darwin Kernel Version 22.4.0: Mon Mar  6 21:00:17 PST 2023; 
root:xnu-8796.101.5~3/RELEASE_X86_64 x86_64
Reporter: Gary D. Gregory


Apache Commons Parent 57 RC1 
(https://lists.apache.org/thread/rwgf9c7dgl2bymq3jg6ckxs6gk9pz4mg) attempts to 
use the javac release flag only on Java 9 and above with 
{code:xml}
8
{code}
and
{code:xml}

  jdk9-compiler
  
[9
  
  

  

  org.apache.maven.plugins
  maven-compiler-plugin
  
${maven.compiler.release}
  

  

  

{code}
This fails miserably:
{noformat}
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  5.402 s
[INFO] Finished at: 2023-04-23T09:23:21-04:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.11.0:compile (default-compile) 
on project commons-lang3: Fatal error compiling: invalid flag: --release -> 
[Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
{noformat}
IMO, setting a property "maven.compiler.release" should not be used on 
compilers that do not support the flag.




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MNG-7744) Maven 3.9.0 and 3.9.1 break compatibility with Apache Mina SSHD build

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-7744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17704341#comment-17704341
 ] 

Gary D. Gregory commented on MNG-7744:
--

Hi [~cstamas] 

Thank you for the pointer, it worked. For the curious: I committed 
[https://github.com/apache/mina-sshd/commit/77fde8c47ed1502ecf2c5b24369c27884430f931]

Feel free to close this issue.

> Maven 3.9.0 and 3.9.1 break compatibility with Apache Mina SSHD build
> -
>
> Key: MNG-7744
> URL: https://issues.apache.org/jira/browse/MNG-7744
> Project: Maven
>  Issue Type: Bug
>Affects Versions: 3.9.0, 3.9.1
>Reporter: Gary D. Gregory
>Priority: Major
>
> The following works fine with 3.8.7:
>  # git clone [https://gitbox.apache.org/repos/asf/mina-sshd.git]
>  # cd mina-sshd
>  # mvn -V clean install javadoc:javadoc
> {noformat}
> Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
> Maven home: C:\java\apache-maven-3.9.0
> Java version: 1.8.0_362, vendor: Temurin, runtime: C:\Program Files\Eclipse 
> Adoptium\jdk-8.0.362.9-hotspot\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> ...
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  32.853 s
> [INFO] Finished at: 2023-03-20T09:14:04-04:00
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> net.revelc.code:impsort-maven-plugin:1.6.2:sort (sort-imports) on project 
> sshd-common: Execution sort-imports of goal 
> net.revelc.code:impsort-maven-plugin:1.6.2:sort failed: A required class was 
> missing while executing net.revelc.code:impsort-maven-plugin:1.6.2:sort: 
> org/codehaus/plexus/util/DirectoryScanner
> [ERROR] -
> [ERROR] realm =plugin>net.revelc.code:impsort-maven-plugin:1.6.2
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] = 
> file:/C:/Users/ggregory/.m2/repository/net/revelc/code/impsort-maven-plugin/1.6.2/impsort-maven-plugin-1.6.2.jar
> [ERROR] urls[1] = 
> file:/C:/Users/ggregory/.m2/repository/com/github/javaparser/javaparser-core/3.22.1/javaparser-core-3.22.1.jar
> [ERROR] urls[2] = 
> file:/C:/Users/ggregory/.m2/repository/com/google/guava/guava/30.1.1-jre/guava-30.1.1-jre.jar
> [ERROR] urls[3] = 
> file:/C:/Users/ggregory/.m2/repository/com/google/guava/failureaccess/1.0.1/failureaccess-1.0.1.jar
> [ERROR] urls[4] = 
> file:/C:/Users/ggregory/.m2/repository/com/google/guava/listenablefuture/.0-empty-to-avoid-conflict-with-guava/listenablefuture-.0-empty-to-avoid-conflict-with-guava.jar
> [ERROR] urls[5] = 
> file:/C:/Users/ggregory/.m2/repository/com/google/code/findbugs/jsr305/3.0.2/jsr305-3.0.2.jar
> [ERROR] urls[6] = 
> file:/C:/Users/ggregory/.m2/repository/org/checkerframework/checker-qual/3.8.0/checker-qual-3.8.0.jar
> [ERROR] urls[7] = 
> file:/C:/Users/ggregory/.m2/repository/com/google/errorprone/error_prone_annotations/2.5.1/error_prone_annotations-2.5.1.jar
> [ERROR] urls[8] = 
> file:/C:/Users/ggregory/.m2/repository/com/google/j2objc/j2objc-annotations/1.3/j2objc-annotations-1.3.jar
> [ERROR] Number of foreign imports: 1
> [ERROR] import: Entry[import  from realm 
> ClassRealm[project>org.apache.sshd:sshd:2.9.3-SNAPSHOT, parent: 
> ClassRealm[maven.api, parent: null]]]
> [ERROR]
> [ERROR] -
> [ERROR] : org.codehaus.plexus.util.DirectoryScanner
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :sshd-common
> {noformat} 
> Same problem with 3.9.1 :
> {noformat}
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  21.064 s
> [INFO] Finished at: 2023-03-20T09:36:52-04:00
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> net.revelc.code:impsort-maven-plugin:1.6.2:sort (sort-imports) on project 
> sshd-common: Execution sort-imports of goal 
> 

[jira] [Commented] (MNG-7744) Maven 3.9.0 and 3.9.1 break compatibility with Apache Mina SSHD build

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-7744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17702799#comment-17702799
 ] 

Gary D. Gregory commented on MNG-7744:
--

But that plugin requires an update to Java 11... not great but doable of course.

> Maven 3.9.0 and 3.9.1 break compatibility with Apache Mina SSHD build
> -
>
> Key: MNG-7744
> URL: https://issues.apache.org/jira/browse/MNG-7744
> Project: Maven
>  Issue Type: Bug
>Affects Versions: 3.9.0, 3.9.1
>Reporter: Gary D. Gregory
>Priority: Major
>
> The following works fine with 3.8.7:
>  # git clone [https://gitbox.apache.org/repos/asf/mina-sshd.git]
>  # cd mina-sshd
>  # mvn -V clean install javadoc:javadoc
> {noformat}
> Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
> Maven home: C:\java\apache-maven-3.9.0
> Java version: 1.8.0_362, vendor: Temurin, runtime: C:\Program Files\Eclipse 
> Adoptium\jdk-8.0.362.9-hotspot\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> ...
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  32.853 s
> [INFO] Finished at: 2023-03-20T09:14:04-04:00
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> net.revelc.code:impsort-maven-plugin:1.6.2:sort (sort-imports) on project 
> sshd-common: Execution sort-imports of goal 
> net.revelc.code:impsort-maven-plugin:1.6.2:sort failed: A required class was 
> missing while executing net.revelc.code:impsort-maven-plugin:1.6.2:sort: 
> org/codehaus/plexus/util/DirectoryScanner
> [ERROR] -
> [ERROR] realm =plugin>net.revelc.code:impsort-maven-plugin:1.6.2
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] = 
> file:/C:/Users/ggregory/.m2/repository/net/revelc/code/impsort-maven-plugin/1.6.2/impsort-maven-plugin-1.6.2.jar
> [ERROR] urls[1] = 
> file:/C:/Users/ggregory/.m2/repository/com/github/javaparser/javaparser-core/3.22.1/javaparser-core-3.22.1.jar
> [ERROR] urls[2] = 
> file:/C:/Users/ggregory/.m2/repository/com/google/guava/guava/30.1.1-jre/guava-30.1.1-jre.jar
> [ERROR] urls[3] = 
> file:/C:/Users/ggregory/.m2/repository/com/google/guava/failureaccess/1.0.1/failureaccess-1.0.1.jar
> [ERROR] urls[4] = 
> file:/C:/Users/ggregory/.m2/repository/com/google/guava/listenablefuture/.0-empty-to-avoid-conflict-with-guava/listenablefuture-.0-empty-to-avoid-conflict-with-guava.jar
> [ERROR] urls[5] = 
> file:/C:/Users/ggregory/.m2/repository/com/google/code/findbugs/jsr305/3.0.2/jsr305-3.0.2.jar
> [ERROR] urls[6] = 
> file:/C:/Users/ggregory/.m2/repository/org/checkerframework/checker-qual/3.8.0/checker-qual-3.8.0.jar
> [ERROR] urls[7] = 
> file:/C:/Users/ggregory/.m2/repository/com/google/errorprone/error_prone_annotations/2.5.1/error_prone_annotations-2.5.1.jar
> [ERROR] urls[8] = 
> file:/C:/Users/ggregory/.m2/repository/com/google/j2objc/j2objc-annotations/1.3/j2objc-annotations-1.3.jar
> [ERROR] Number of foreign imports: 1
> [ERROR] import: Entry[import  from realm 
> ClassRealm[project>org.apache.sshd:sshd:2.9.3-SNAPSHOT, parent: 
> ClassRealm[maven.api, parent: null]]]
> [ERROR]
> [ERROR] -
> [ERROR] : org.codehaus.plexus.util.DirectoryScanner
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :sshd-common
> {noformat} 
> Same problem with 3.9.1 :
> {noformat}
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  21.064 s
> [INFO] Finished at: 2023-03-20T09:36:52-04:00
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> net.revelc.code:impsort-maven-plugin:1.6.2:sort (sort-imports) on project 
> sshd-common: Execution sort-imports of goal 
> net.revelc.code:impsort-maven-plugin:1.6.2:sort failed: A required class was 
> missing while executing 

[jira] [Updated] (MNG-7744) Maven 3.9.0 and 3.9.1 break compatibility with Apache Mina SSHD build

[Gary D. Gregory (Jira)]

 [ 
https://issues.apache.org/jira/browse/MNG-7744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gary D. Gregory updated MNG-7744:
-
Affects Version/s: 3.9.1
  Description: 
The following works fine with 3.8.7:
 # git clone [https://gitbox.apache.org/repos/asf/mina-sshd.git]
 # cd mina-sshd
 # mvn -V clean install javadoc:javadoc

{noformat}
Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
Maven home: C:\java\apache-maven-3.9.0
Java version: 1.8.0_362, vendor: Temurin, runtime: C:\Program Files\Eclipse 
Adoptium\jdk-8.0.362.9-hotspot\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
...
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  32.853 s
[INFO] Finished at: 2023-03-20T09:14:04-04:00
[INFO] 
[ERROR] Failed to execute goal net.revelc.code:impsort-maven-plugin:1.6.2:sort 
(sort-imports) on project sshd-common: Execution sort-imports of goal 
net.revelc.code:impsort-maven-plugin:1.6.2:sort failed: A required class was 
missing while executing net.revelc.code:impsort-maven-plugin:1.6.2:sort: 
org/codehaus/plexus/util/DirectoryScanner
[ERROR] -
[ERROR] realm =plugin>net.revelc.code:impsort-maven-plugin:1.6.2
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = 
file:/C:/Users/ggregory/.m2/repository/net/revelc/code/impsort-maven-plugin/1.6.2/impsort-maven-plugin-1.6.2.jar
[ERROR] urls[1] = 
file:/C:/Users/ggregory/.m2/repository/com/github/javaparser/javaparser-core/3.22.1/javaparser-core-3.22.1.jar
[ERROR] urls[2] = 
file:/C:/Users/ggregory/.m2/repository/com/google/guava/guava/30.1.1-jre/guava-30.1.1-jre.jar
[ERROR] urls[3] = 
file:/C:/Users/ggregory/.m2/repository/com/google/guava/failureaccess/1.0.1/failureaccess-1.0.1.jar
[ERROR] urls[4] = 
file:/C:/Users/ggregory/.m2/repository/com/google/guava/listenablefuture/.0-empty-to-avoid-conflict-with-guava/listenablefuture-.0-empty-to-avoid-conflict-with-guava.jar
[ERROR] urls[5] = 
file:/C:/Users/ggregory/.m2/repository/com/google/code/findbugs/jsr305/3.0.2/jsr305-3.0.2.jar
[ERROR] urls[6] = 
file:/C:/Users/ggregory/.m2/repository/org/checkerframework/checker-qual/3.8.0/checker-qual-3.8.0.jar
[ERROR] urls[7] = 
file:/C:/Users/ggregory/.m2/repository/com/google/errorprone/error_prone_annotations/2.5.1/error_prone_annotations-2.5.1.jar
[ERROR] urls[8] = 
file:/C:/Users/ggregory/.m2/repository/com/google/j2objc/j2objc-annotations/1.3/j2objc-annotations-1.3.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import  from realm 
ClassRealm[project>org.apache.sshd:sshd:2.9.3-SNAPSHOT, parent: 
ClassRealm[maven.api, parent: null]]]
[ERROR]
[ERROR] -
[ERROR] : org.codehaus.plexus.util.DirectoryScanner
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :sshd-common
{noformat} 

Same problem with 3.9.1 :
{noformat}
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  21.064 s
[INFO] Finished at: 2023-03-20T09:36:52-04:00
[INFO] 
[ERROR] Failed to execute goal net.revelc.code:impsort-maven-plugin:1.6.2:sort 
(sort-imports) on project sshd-common: Execution sort-imports of goal 
net.revelc.code:impsort-maven-plugin:1.6.2:sort failed: A required class was 
missing while executing net.revelc.code:impsort-maven-plugin:1.6.2:sort: 
org/codehaus/plexus/util/DirectoryScanner
[ERROR] -
[ERROR] realm =plugin>net.revelc.code:impsort-maven-plugin:1.6.2
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = 
file:/C:/Users/ggregory/.m2/repository/net/revelc/code/impsort-maven-plugin/1.6.2/impsort-maven-plugin-1.6.2.jar
[ERROR] urls[1] = 
file:/C:/Users/ggregory/.m2/repository/com/github/javaparser/javaparser-core/3.22.1/javaparser-core-3.22.1.jar
[ERROR] urls[2] = 
file:/C:/Users/ggregory/.m2/repository/com/google/guava/guava/30.1.1-jre/guava-30.1.1-jre.jar
[ERROR] urls[3] = 

[jira] [Updated] (MNG-7744) Maven 3.9.0 and 3.9.1 break compatibility with Apache Mina SSHD build

[Gary D. Gregory (Jira)]

 [ 
https://issues.apache.org/jira/browse/MNG-7744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gary D. Gregory updated MNG-7744:
-
Summary: Maven 3.9.0 and 3.9.1 break compatibility with Apache Mina SSHD 
build  (was: Broken compatibility with Apache Mina SSHD build)

> Maven 3.9.0 and 3.9.1 break compatibility with Apache Mina SSHD build
> -
>
> Key: MNG-7744
> URL: https://issues.apache.org/jira/browse/MNG-7744
> Project: Maven
>  Issue Type: Bug
>Affects Versions: 3.9.0
>Reporter: Gary D. Gregory
>Priority: Major
>
> The following works fine with 3.8.7:
>  # git clone [https://gitbox.apache.org/repos/asf/mina-sshd.git]
>  # cd mina-sshd
>  # mvn -V clean install javadoc:javadoc
> {noformat}
> Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
> Maven home: C:\java\apache-maven-3.9.0
> Java version: 1.8.0_362, vendor: Temurin, runtime: C:\Program Files\Eclipse 
> Adoptium\jdk-8.0.362.9-hotspot\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> ...
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  32.853 s
> [INFO] Finished at: 2023-03-20T09:14:04-04:00
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> net.revelc.code:impsort-maven-plugin:1.6.2:sort (sort-imports) on project 
> sshd-common: Execution sort-imports of goal 
> net.revelc.code:impsort-maven-plugin:1.6.2:sort failed: A required class was 
> missing while executing net.revelc.code:impsort-maven-plugin:1.6.2:sort: 
> org/codehaus/plexus/util/DirectoryScanner
> [ERROR] -
> [ERROR] realm =plugin>net.revelc.code:impsort-maven-plugin:1.6.2
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] = 
> file:/C:/Users/ggregory/.m2/repository/net/revelc/code/impsort-maven-plugin/1.6.2/impsort-maven-plugin-1.6.2.jar
> [ERROR] urls[1] = 
> file:/C:/Users/ggregory/.m2/repository/com/github/javaparser/javaparser-core/3.22.1/javaparser-core-3.22.1.jar
> [ERROR] urls[2] = 
> file:/C:/Users/ggregory/.m2/repository/com/google/guava/guava/30.1.1-jre/guava-30.1.1-jre.jar
> [ERROR] urls[3] = 
> file:/C:/Users/ggregory/.m2/repository/com/google/guava/failureaccess/1.0.1/failureaccess-1.0.1.jar
> [ERROR] urls[4] = 
> file:/C:/Users/ggregory/.m2/repository/com/google/guava/listenablefuture/.0-empty-to-avoid-conflict-with-guava/listenablefuture-.0-empty-to-avoid-conflict-with-guava.jar
> [ERROR] urls[5] = 
> file:/C:/Users/ggregory/.m2/repository/com/google/code/findbugs/jsr305/3.0.2/jsr305-3.0.2.jar
> [ERROR] urls[6] = 
> file:/C:/Users/ggregory/.m2/repository/org/checkerframework/checker-qual/3.8.0/checker-qual-3.8.0.jar
> [ERROR] urls[7] = 
> file:/C:/Users/ggregory/.m2/repository/com/google/errorprone/error_prone_annotations/2.5.1/error_prone_annotations-2.5.1.jar
> [ERROR] urls[8] = 
> file:/C:/Users/ggregory/.m2/repository/com/google/j2objc/j2objc-annotations/1.3/j2objc-annotations-1.3.jar
> [ERROR] Number of foreign imports: 1
> [ERROR] import: Entry[import  from realm 
> ClassRealm[project>org.apache.sshd:sshd:2.9.3-SNAPSHOT, parent: 
> ClassRealm[maven.api, parent: null]]]
> [ERROR]
> [ERROR] -
> [ERROR] : org.codehaus.plexus.util.DirectoryScanner
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :sshd-common
> {noformat} 
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (MNG-7744) Broken compatibility with Apache Mina SSHD build

[Gary D. Gregory (Jira)]

Gary D. Gregory created MNG-7744:


 Summary: Broken compatibility with Apache Mina SSHD build
 Key: MNG-7744
 URL: https://issues.apache.org/jira/browse/MNG-7744
 Project: Maven
  Issue Type: Bug
Affects Versions: 3.9.0
Reporter: Gary D. Gregory


The following works fine with 3.8.7:
 # git clone [https://gitbox.apache.org/repos/asf/mina-sshd.git]
 # cd mina-sshd
 # mvn -V clean install javadoc:javadoc

{noformat}
Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
Maven home: C:\java\apache-maven-3.9.0
Java version: 1.8.0_362, vendor: Temurin, runtime: C:\Program Files\Eclipse 
Adoptium\jdk-8.0.362.9-hotspot\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
...
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  32.853 s
[INFO] Finished at: 2023-03-20T09:14:04-04:00
[INFO] 
[ERROR] Failed to execute goal net.revelc.code:impsort-maven-plugin:1.6.2:sort 
(sort-imports) on project sshd-common: Execution sort-imports of goal 
net.revelc.code:impsort-maven-plugin:1.6.2:sort failed: A required class was 
missing while executing net.revelc.code:impsort-maven-plugin:1.6.2:sort: 
org/codehaus/plexus/util/DirectoryScanner
[ERROR] -
[ERROR] realm =plugin>net.revelc.code:impsort-maven-plugin:1.6.2
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = 
file:/C:/Users/ggregory/.m2/repository/net/revelc/code/impsort-maven-plugin/1.6.2/impsort-maven-plugin-1.6.2.jar
[ERROR] urls[1] = 
file:/C:/Users/ggregory/.m2/repository/com/github/javaparser/javaparser-core/3.22.1/javaparser-core-3.22.1.jar
[ERROR] urls[2] = 
file:/C:/Users/ggregory/.m2/repository/com/google/guava/guava/30.1.1-jre/guava-30.1.1-jre.jar
[ERROR] urls[3] = 
file:/C:/Users/ggregory/.m2/repository/com/google/guava/failureaccess/1.0.1/failureaccess-1.0.1.jar
[ERROR] urls[4] = 
file:/C:/Users/ggregory/.m2/repository/com/google/guava/listenablefuture/.0-empty-to-avoid-conflict-with-guava/listenablefuture-.0-empty-to-avoid-conflict-with-guava.jar
[ERROR] urls[5] = 
file:/C:/Users/ggregory/.m2/repository/com/google/code/findbugs/jsr305/3.0.2/jsr305-3.0.2.jar
[ERROR] urls[6] = 
file:/C:/Users/ggregory/.m2/repository/org/checkerframework/checker-qual/3.8.0/checker-qual-3.8.0.jar
[ERROR] urls[7] = 
file:/C:/Users/ggregory/.m2/repository/com/google/errorprone/error_prone_annotations/2.5.1/error_prone_annotations-2.5.1.jar
[ERROR] urls[8] = 
file:/C:/Users/ggregory/.m2/repository/com/google/j2objc/j2objc-annotations/1.3/j2objc-annotations-1.3.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import  from realm 
ClassRealm[project>org.apache.sshd:sshd:2.9.3-SNAPSHOT, parent: 
ClassRealm[maven.api, parent: null]]]
[ERROR]
[ERROR] -
[ERROR] : org.codehaus.plexus.util.DirectoryScanner
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :sshd-common
{noformat} 

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (MNG-7711) Maven 3.9.0 fails to builds Jakarta EE servlet when 3.8.7 did

[Gary D. Gregory (Jira)]

Gary D. Gregory created MNG-7711:


 Summary: Maven 3.9.0 fails to builds Jakarta EE servlet when 3.8.7 
did
 Key: MNG-7711
 URL: https://issues.apache.org/jira/browse/MNG-7711
 Project: Maven
  Issue Type: Bug
  Components: Core
Affects Versions: 3.9.0
 Environment: Apache Maven 3.9.0 
(9b58d2bad23a66be161c4664ef21ce219c2c8584)
Maven home: C:\java\apache-maven-3.9.0
Java version: 11.0.18, vendor: Eclipse Adoptium, runtime: C:\Program 
Files\Eclipse Adoptium\jdk-11.0.18.10-hotspot
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
Reporter: Gary D. Gregory


# Requires Java 11
 # git clone [https://github.com/jakartaee/servlet.git 
|https://github.com/jakartaee/servlet.git]
 # cd servlet
 # mvn clean install

This output is from my fresh untouched fork instead of 
[servlet.git:|https://github.com/jakartaee/servlet.git]
{quote}[INFO] 

[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 4.842 s
[INFO] Finished at: 2023-02-24T13:00:13-05:00
[INFO] 
[ERROR] Failed to execute goal net.revelc.code:impsort-maven-plugin:1.4.1:sort 
(sort-imports) on project jakarta.servlet-api: Execution sort-imports of goal 
net.revelc.code:impsort-maven-plugin:1.4.1:sort failed: A required class was 
missing while executing net.revelc.code:impsort-maven-plugin:1.4.1:sort: 
org/codehaus/plexus/util/DirectoryScanner
[ERROR] -
[ERROR] realm = plugin>net.revelc.code:impsort-maven-plugin:1.4.1
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = 
[file:/C:/Users/ggregory/.m2/repository/net/revelc/code/impsort-maven-plugin/1.4.1/impsort-maven-plugin-1.4.1.jar|file:///C:/Users/ggregory/.m2/repository/net/revelc/code/impsort-maven-plugin/1.4.1/impsort-maven-plugin-1.4.1.jar]
[ERROR] urls[1] = 
[file:/C:/Users/ggregory/.m2/repository/com/github/javaparser/javaparser-core/3.15.21/javaparser-core-3.15.21.jar|file:///C:/Users/ggregory/.m2/repository/com/github/javaparser/javaparser-core/3.15.21/javaparser-core-3.15.21.jar]
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import from realm ClassRealm[maven.api, parent: null]]
[ERROR]
[ERROR] -
[ERROR] : org.codehaus.plexus.util.DirectoryScanner
[ERROR] -> [Help 1]
{quote}
This worked fine in 3.8.7



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MCHANGES-412) Allow an action to carry an optional scope

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MCHANGES-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17679558#comment-17679558
 ] 

Gary D. Gregory commented on MCHANGES-412:
--

Is this something I should bother creating a PR for or are you guys not 
interested? 

> Allow an action to carry an optional scope
> --
>
> Key: MCHANGES-412
> URL: https://issues.apache.org/jira/browse/MCHANGES-412
> Project: Maven Changes Plugin
>  Issue Type: New Feature
>  Components: changes.xml
>Reporter: Gary D. Gregory
>Priority: Major
>
> In changes.xml, I would like an *action* to carry an optional {*}scope{*}.
> This would help users understand what changes affect which part of their 
> projects.
> For example:
> Fix some bug
> Bump dependency foo 
> from 1 to 2
> Bump commons-parent 
> foo from 1 to 2
> The use of the scope documents where the change applies, usually runtime, 
> test, or build, but it could be string maybe.
> This somewhat parallels the concept of a scope in a dependency so the value 
> set could be the same as allowed for a dependency scope but that might be too 
> restrictive.
> Thoughts?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (MCHANGES-414) Site looks nasty on mobile

[Gary D. Gregory (Jira)]

Gary D. Gregory created MCHANGES-414:


 Summary: Site looks nasty on mobile
 Key: MCHANGES-414
 URL: https://issues.apache.org/jira/browse/MCHANGES-414
 Project: Maven Changes Plugin
  Issue Type: Improvement
Reporter: Gary D. Gregory
 Attachments: Screenshot_20230122-083709_Chrome.jpg

See screenshot.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MNG-7636) Partially revert MNG-5868 to restore backward compatibility (see MNG-7316)

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-7636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17648957#comment-17648957
 ] 

Gary D. Gregory commented on MNG-7636:
--

Thanks for the heads up [~michael-o] 

> Partially revert MNG-5868 to restore backward compatibility (see MNG-7316)
> --
>
> Key: MNG-7636
> URL: https://issues.apache.org/jira/browse/MNG-7636
> Project: Maven
>  Issue Type: Task
>Affects Versions: 3.8.6
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.9.0, 3.8.7
>
>
> Due to the lack of documentation it was never clear whether 
> {{org.apache.maven.project.MavenProject.getAttachedArtifacts()}} is mutable 
> or not. Components used or abused this collection. The change was done in 
> 3.8.x in a patch release which was unfortunately and make things obvious. To 
> better address the breaking situation this change will be partially reverted 
> in 3.8.x, but documented in 3.9.0 and 4.0.0 that the collection is read-only. 
> A proper solution to remove attached is desired in the future.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MNG-7316) MavenProject.getAttachedArtifacts() regression with 3.8.1

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17640663#comment-17640663
 ] 

Gary D. Gregory commented on MNG-7316:
--

>From a functional level, I only care that our Commons plugin works and let's 
>us simplify our release process. The details are not important to me at least; 
>yes, the current implementation is hacky-nasty but that's what we had to do to 
>adapt to changes in Maven.

I think [~chtompki] wrote that part of the plugin and I hacked on top of it to 
adapt to the Maven change, but, again, I am happy that it works, and I am also 
ok if it gets rewritten, as long as it all works the same from the command line.

I don't know what the best path forward is, but for now, I think the hack will 
stay in place on our end until either it breaks or there is an official API to 
do what we need. From my POV, any Maven public or protected API is fair game 
and therefore "official" unless it is clearly documented not to be or is in a 
package with an obvious name like "internal".

 

What should we do?

> MavenProject.getAttachedArtifacts() regression with 3.8.1
> -
>
> Key: MNG-7316
> URL: https://issues.apache.org/jira/browse/MNG-7316
> Project: Maven
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 3.8.2, 3.8.3
>Reporter: Gary D. Gregory
>Assignee: Michael Osipov
>Priority: Critical
> Fix For: waiting-for-feedback, wontfix-candidate
>
>
> The method {{MavenProject.getAttachedArtifacts()}} as of 3.8.2 breaks 
> releasing components for us at Apache Commons using our Maven Release plugin 
> because the list returned is now immutable, we now get an exception when 
> calling {{remove()}} on the collection returned by the API; see 
> [https://github.com/apache/commons-release-plugin/blob/master/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java#L137]
> This worked fine in 3.8.1, may you please change it back for 3.8.4?
> We cannot use Maven 3.8.2 and 3.8.3 to release our components.
> ([~michael-o]: Ironically, I discovered this trying to create a release 
> candidate for Apache Commons CLI.)
> The exception in 3.8.3:
> {quote}Caused by: java.lang.UnsupportedOperationException
>  at java.util.Collections$UnmodifiableCollection.remove 
> (Collections.java:1060)
>  at 
> org.apache.commons.release.plugin.mojos.CommonsDistributionDetachmentMojo.execute
>  (CommonsDistributionDetachmentMojo.java:136)
>  at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:137)
> {quote}
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MNG-7316) MavenProject.getAttachedArtifacts() regression with 3.8.1

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635829#comment-17635829
 ] 

Gary D. Gregory commented on MNG-7316:
--

Hi [~michael-o] CC [~chtompki] 

As long as the plugin works, I am not so concerned about how the internals are 
implemented. If you are able to take the time and Rob cannot, I'd appreciate 
the help on a rewrite. 

> MavenProject.getAttachedArtifacts() regression with 3.8.1
> -
>
> Key: MNG-7316
> URL: https://issues.apache.org/jira/browse/MNG-7316
> Project: Maven
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 3.8.2, 3.8.3
>Reporter: Gary D. Gregory
>Priority: Critical
> Fix For: waiting-for-feedback, wontfix-candidate
>
>
> The method {{MavenProject.getAttachedArtifacts()}} as of 3.8.2 breaks 
> releasing components for us at Apache Commons using our Maven Release plugin 
> because the list returned is now immutable, we now get an exception when 
> calling {{remove()}} on the collection returned by the API; see 
> [https://github.com/apache/commons-release-plugin/blob/master/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java#L137]
> This worked fine in 3.8.1, may you please change it back for 3.8.4?
> We cannot use Maven 3.8.2 and 3.8.3 to release our components.
> ([~michael-o]: Ironically, I discovered this trying to create a release 
> candidate for Apache Commons CLI.)
> The exception in 3.8.3:
> {quote}Caused by: java.lang.UnsupportedOperationException
>  at java.util.Collections$UnmodifiableCollection.remove 
> (Collections.java:1060)
>  at 
> org.apache.commons.release.plugin.mojos.CommonsDistributionDetachmentMojo.execute
>  (CommonsDistributionDetachmentMojo.java:136)
>  at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:137)
> {quote}
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MNG-7316) MavenProject.getAttachedArtifacts() regression with 3.8.1

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635818#comment-17635818
 ] 

Gary D. Gregory commented on MNG-7316:
--

Hi [~michael-o] CC [~chtompki] 

This is part of the black magic of Maven and our plugin that I don't know; I 
hope [~chtompki] can provide an answer. 

 

> MavenProject.getAttachedArtifacts() regression with 3.8.1
> -
>
> Key: MNG-7316
> URL: https://issues.apache.org/jira/browse/MNG-7316
> Project: Maven
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 3.8.2, 3.8.3
>Reporter: Gary D. Gregory
>Priority: Critical
> Fix For: waiting-for-feedback, wontfix-candidate
>
>
> The method {{MavenProject.getAttachedArtifacts()}} as of 3.8.2 breaks 
> releasing components for us at Apache Commons using our Maven Release plugin 
> because the list returned is now immutable, we now get an exception when 
> calling {{remove()}} on the collection returned by the API; see 
> [https://github.com/apache/commons-release-plugin/blob/master/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java#L137]
> This worked fine in 3.8.1, may you please change it back for 3.8.4?
> We cannot use Maven 3.8.2 and 3.8.3 to release our components.
> ([~michael-o]: Ironically, I discovered this trying to create a release 
> candidate for Apache Commons CLI.)
> The exception in 3.8.3:
> {quote}Caused by: java.lang.UnsupportedOperationException
>  at java.util.Collections$UnmodifiableCollection.remove 
> (Collections.java:1060)
>  at 
> org.apache.commons.release.plugin.mojos.CommonsDistributionDetachmentMojo.execute
>  (CommonsDistributionDetachmentMojo.java:136)
>  at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:137)
> {quote}
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Comment Edited] (MNG-7316) MavenProject.getAttachedArtifacts() regression with 3.8.1

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17634818#comment-17634818
 ] 

Gary D. Gregory edited comment on MNG-7316 at 11/16/22 12:35 PM:
-

I'll be ok with it being fixed in 3.8.x or 3.9.0 or both so I can drop the 
reflection hack currently in place in the Commons Release plugin.


was (Author: garydgregory):
I'll be ok with it being fixed in 3.8.x or 3.9.0 or both so I can drop the 
reflection hack currently in place the Commons Release plugin.

> MavenProject.getAttachedArtifacts() regression with 3.8.1
> -
>
> Key: MNG-7316
> URL: https://issues.apache.org/jira/browse/MNG-7316
> Project: Maven
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 3.8.2, 3.8.3
>Reporter: Gary D. Gregory
>Priority: Critical
> Fix For: waiting-for-feedback, wontfix-candidate
>
>
> The method {{MavenProject.getAttachedArtifacts()}} as of 3.8.2 breaks 
> releasing components for us at Apache Commons using our Maven Release plugin 
> because the list returned is now immutable, we now get an exception when 
> calling {{remove()}} on the collection returned by the API; see 
> [https://github.com/apache/commons-release-plugin/blob/master/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java#L137]
> This worked fine in 3.8.1, may you please change it back for 3.8.4?
> We cannot use Maven 3.8.2 and 3.8.3 to release our components.
> ([~michael-o]: Ironically, I discovered this trying to create a release 
> candidate for Apache Commons CLI.)
> The exception in 3.8.3:
> {quote}Caused by: java.lang.UnsupportedOperationException
>  at java.util.Collections$UnmodifiableCollection.remove 
> (Collections.java:1060)
>  at 
> org.apache.commons.release.plugin.mojos.CommonsDistributionDetachmentMojo.execute
>  (CommonsDistributionDetachmentMojo.java:136)
>  at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:137)
> {quote}
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MNG-7316) MavenProject.getAttachedArtifacts() regression with 3.8.1

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17634818#comment-17634818
 ] 

Gary D. Gregory commented on MNG-7316:
--

I'll be ok with it being fixed in 3.8.x or 3.9.0 or both so I can drop the 
reflection hack currently in place the Commons Release plugin.

> MavenProject.getAttachedArtifacts() regression with 3.8.1
> -
>
> Key: MNG-7316
> URL: https://issues.apache.org/jira/browse/MNG-7316
> Project: Maven
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 3.8.2, 3.8.3
>Reporter: Gary D. Gregory
>Priority: Critical
> Fix For: waiting-for-feedback, wontfix-candidate
>
>
> The method {{MavenProject.getAttachedArtifacts()}} as of 3.8.2 breaks 
> releasing components for us at Apache Commons using our Maven Release plugin 
> because the list returned is now immutable, we now get an exception when 
> calling {{remove()}} on the collection returned by the API; see 
> [https://github.com/apache/commons-release-plugin/blob/master/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java#L137]
> This worked fine in 3.8.1, may you please change it back for 3.8.4?
> We cannot use Maven 3.8.2 and 3.8.3 to release our components.
> ([~michael-o]: Ironically, I discovered this trying to create a release 
> candidate for Apache Commons CLI.)
> The exception in 3.8.3:
> {quote}Caused by: java.lang.UnsupportedOperationException
>  at java.util.Collections$UnmodifiableCollection.remove 
> (Collections.java:1060)
>  at 
> org.apache.commons.release.plugin.mojos.CommonsDistributionDetachmentMojo.execute
>  (CommonsDistributionDetachmentMojo.java:136)
>  at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:137)
> {quote}
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (MCHANGES-413) Jira report throws NPE when the resolution field is missing the "name" attribute

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MCHANGES-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625614#comment-17625614
 ] 

Gary D. Gregory commented on MCHANGES-413:
--

I'd prefer the plugin be made more resilient. It's quite the debugging hunt for 
anyone else to track this down when using the plugin as a plain user.

> Jira report throws NPE when the resolution field is missing the "name" 
> attribute
> 
>
> Key: MCHANGES-413
> URL: https://issues.apache.org/jira/browse/MCHANGES-413
> Project: Maven Changes Plugin
>  Issue Type: Bug
>  Components: jira
>Affects Versions: 2.12.1
>Reporter: Alex Herbert
>Priority: Trivial
>
> The `jira-report` goal throws a NullPointerException when the resolution 
> JsonNode has no "name" attribute.
> At Commons BCEL we had some tickets that were created from external issues. 
> The priority field was set to an enum in [P0, P1, P2, P3, P4, P5]. See for 
> example [BCEL-4|https://issues.apache.org/jira/projects/BCEL/issues/BCEL-4]. 
> This field did not use the standard [Major, Minor, etc] and may have been a 
> custom field. (The details of how these tickets were created is unknown.) The 
> "standard" priority field was missing and the data downloaded by the 
> \{{RestJiraDownloader}} had no "name" attribute for this node. Thus the NPE 
> from this line:
> {code:java}
> // Note: val is not null here
> issue.setPriority( val.get( "name" ).asText() );{code}
> Patching the latest maven-changes-plugin to print all these offending tickets 
> allowed them to be identified and corrected by adding a "standard" priority. 
> In the example mentioned (BCEL-4) there are still two priority fields in the 
> ticket.
> Note that when the missing priority was ignored the Jira report completed 
> successfully.
> The solution is either:
>  * Patch the RestJiraDownloader to be robust to this field missing the 
> expected data
>  * Label as not-a-bug because this field is mandatory and BCEL has somehow 
> created invalid Jira tickets in the past



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (MCHANGES-412) Allow an action to carry an optional scope

[Gary D. Gregory (Jira)]

 [ 
https://issues.apache.org/jira/browse/MCHANGES-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gary D. Gregory updated MCHANGES-412:
-
Description: 
In changes.xml, I would like an *action* to carry an optional {*}scope{*}.

This would help users understand what changes affect which part of their 
projects.

For example:

Fix some bug
Bump dependency foo 
from 1 to 2
Bump commons-parent 
foo from 1 to 2

The use of the scope documents where the change applies, usually runtime, test, 
or build, but it could be string maybe.

This somewhat parallels the concept of a scope in a dependency so the value set 
could be the same as allowed for a dependency scope but that might be too 
restrictive.

Thoughts?

  was:
In changes.xml, I would like an *action* to carry an optional {*}scope{*}.

This would help users understand what changes affect which part of their 
projects.

For example:

Fix some bug
Bump dependency foo 
from 1 to 2
Bump commons-parent 
foo from 1 to 2

The use of the scope documents where the change applies, usually runtime, test, 
or build, but it could be anything maybe.
This somewhat parallels the concept of a scope in a dependency so the value 
could be the same as allowed for a dependency scope but that might be too 
restrictive.

Thoughts?


> Allow an action to carry an optional scope
> --
>
> Key: MCHANGES-412
> URL: https://issues.apache.org/jira/browse/MCHANGES-412
> Project: Maven Changes Plugin
>  Issue Type: New Feature
>  Components: changes.xml
>Reporter: Gary D. Gregory
>Priority: Major
>
> In changes.xml, I would like an *action* to carry an optional {*}scope{*}.
> This would help users understand what changes affect which part of their 
> projects.
> For example:
> Fix some bug
> Bump dependency foo 
> from 1 to 2
> Bump commons-parent 
> foo from 1 to 2
> The use of the scope documents where the change applies, usually runtime, 
> test, or build, but it could be string maybe.
> This somewhat parallels the concept of a scope in a dependency so the value 
> set could be the same as allowed for a dependency scope but that might be too 
> restrictive.
> Thoughts?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (MCHANGES-412) Allow an action to carry an optional scope

[Gary D. Gregory (Jira)]

 [ 
https://issues.apache.org/jira/browse/MCHANGES-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gary D. Gregory updated MCHANGES-412:
-
Description: 
In changes.xml, I would like an *action* to carry an optional {*}scope{*}.

This would help users understand what changes affect which part of their 
projects.

For example:

Fix some bug
Bump dependency foo 
from 1 to 2
Bump commons-parent 
foo from 1 to 2

The use of the scope documents where the change applies, usually runtime, test, 
or build, but it could be anything maybe.
This somewhat parallels the concept of a scope in a dependency so the value 
could be the same as allowed for a dependency scope but that might be too 
restrictive.

Thoughts?

  was:
In changes.xml, I would like an *action* to carry an optional {*}scope{*}.

This would help users understand what changes affect which part of their 
projects.

For example:

Fix some bug
Bump dependency foo 
from 1 to 2
Bump commons-parent 
foo from 1 to 2

The use of the scope documents where the fix applies, usually runtime, test, or 
build.
This somewhat parallels the concept of a scope in a dependency.

Thoughts?


> Allow an action to carry an optional scope
> --
>
> Key: MCHANGES-412
> URL: https://issues.apache.org/jira/browse/MCHANGES-412
> Project: Maven Changes Plugin
>  Issue Type: New Feature
>  Components: changes.xml
>Reporter: Gary D. Gregory
>Priority: Major
>
> In changes.xml, I would like an *action* to carry an optional {*}scope{*}.
> This would help users understand what changes affect which part of their 
> projects.
> For example:
> Fix some bug
> Bump dependency foo 
> from 1 to 2
> Bump commons-parent 
> foo from 1 to 2
> The use of the scope documents where the change applies, usually runtime, 
> test, or build, but it could be anything maybe.
> This somewhat parallels the concept of a scope in a dependency so the value 
> could be the same as allowed for a dependency scope but that might be too 
> restrictive.
> Thoughts?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (MCHANGES-412) Allow an action to carry an optional scope

[Gary D. Gregory (Jira)]

 [ 
https://issues.apache.org/jira/browse/MCHANGES-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gary D. Gregory updated MCHANGES-412:
-
Description: 
In changes.xml, I would like an *action* to carry an optional {*}scope{*}.

This would help users understand what changes affect which part of their 
projects.

For example:

Fix some bug
Bump dependency foo 
from 1 to 2
Bump commons-parent 
foo from 1 to 2

The use of the scope documents where the fix applies, usually runtime, test, or 
build.
This somewhat parallels the concept of a scope in a dependency.

Thoughts?

  was:
In changes.xml, I would like an *action* to carry an optional {*}scope{*}.

This would help users understand what changes affect which part of their 
projects.

For example:

Fix some bug
Bump dependency foo from 
1 to 2
Bump commons-parent foo 
from 1 to 2

The use of the scope documents where the fix applies, usually runtime, test, or 
build.
This somewhat parallels the concept of a scope in a dependency.

Thoughts?


> Allow an action to carry an optional scope
> --
>
> Key: MCHANGES-412
> URL: https://issues.apache.org/jira/browse/MCHANGES-412
> Project: Maven Changes Plugin
>  Issue Type: New Feature
>  Components: changes.xml
>Reporter: Gary D. Gregory
>Priority: Major
>
> In changes.xml, I would like an *action* to carry an optional {*}scope{*}.
> This would help users understand what changes affect which part of their 
> projects.
> For example:
> Fix some bug
> Bump dependency foo 
> from 1 to 2
> Bump commons-parent 
> foo from 1 to 2
> The use of the scope documents where the fix applies, usually runtime, test, 
> or build.
> This somewhat parallels the concept of a scope in a dependency.
> Thoughts?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (MCHANGES-412) Allow an action to carry an optional scope

[Gary D. Gregory (Jira)]

Gary D. Gregory created MCHANGES-412:


 Summary: Allow an action to carry an optional scope
 Key: MCHANGES-412
 URL: https://issues.apache.org/jira/browse/MCHANGES-412
 Project: Maven Changes Plugin
  Issue Type: New Feature
  Components: changes.xml
Reporter: Gary D. Gregory


In changes.xml, I would like an *action* to carry an optional {*}scope{*}.

This would help users understand what changes affect which part of their 
projects.

For example:

Fix some bug
Bump dependency foo from 
1 to 2
Bump commons-parent foo 
from 1 to 2

The use of the scope documents where the fix applies, usually runtime, test, or 
build.
This somewhat parallels the concept of a scope in a dependency.

Thoughts?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (MJAVADOC-733) Alternative doclet page points to an SEO spammy page

[Gary D. Gregory (Jira)]

 [ 
https://issues.apache.org/jira/browse/MJAVADOC-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gary D. Gregory updated MJAVADOC-733:
-
Description: On the page 
https://maven.apache.org/plugins/maven-javadoc-plugin/examples/alternate-doclet.html
 the site http://www.umlgraph.org/ is no longer valid.  (was: The site 
http://www.umlgraph.org/ is no longer valid.)

> Alternative doclet page points to an SEO spammy page
> 
>
> Key: MJAVADOC-733
> URL: https://issues.apache.org/jira/browse/MJAVADOC-733
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Reporter: Gary D. Gregory
>Priority: Major
>
> On the page 
> https://maven.apache.org/plugins/maven-javadoc-plugin/examples/alternate-doclet.html
>  the site http://www.umlgraph.org/ is no longer valid.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (MJAVADOC-733) Alternative doclet page points to an SEO spammy page

[Gary D. Gregory (Jira)]

Gary D. Gregory created MJAVADOC-733:


 Summary: Alternative doclet page points to an SEO spammy page
 Key: MJAVADOC-733
 URL: https://issues.apache.org/jira/browse/MJAVADOC-733
 Project: Maven Javadoc Plugin
  Issue Type: Bug
Reporter: Gary D. Gregory


The site http://www.umlgraph.org/ is no longer valid.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Comment Edited] (MNG-7316) MavenProject.getAttachedArtifacts() regression with 3.8.1

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17544891#comment-17544891
 ] 

Gary D. Gregory edited comment on MNG-7316 at 6/1/22 12:59 PM:
---

Hi, [~chtompki] Any chance you can look at recoding the Apache Commons Maven 
plugin before 3.8.6 goes out the door? We can recode it to avoid reflection, 
great, if not, we need a long-term solution instead of my reflection into the 
gut of Maven hack.


was (Author: garydgregory):
Hi [~chtompki] Any chance you can look at recoding the Apache Commons Maven 
plugin before 3.8.6 goes out the door? We can recode it to avoid reflection, 
great, if not, we need a long term solution instead of my reflection into the 
gut of Maven hack.

> MavenProject.getAttachedArtifacts() regression with 3.8.1
> -
>
> Key: MNG-7316
> URL: https://issues.apache.org/jira/browse/MNG-7316
> Project: Maven
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 3.8.2, 3.8.3
>Reporter: Gary D. Gregory
>Priority: Critical
> Fix For: waiting-for-feedback, wontfix-candidate
>
>
> The method {{MavenProject.getAttachedArtifacts()}} as of 3.8.2 breaks 
> releasing components for us at Apache Commons using our Maven Release plugin 
> because the list returned is now immutable, we now get an exception when 
> calling {{remove()}} on the collection returned by the API; see 
> [https://github.com/apache/commons-release-plugin/blob/master/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java#L137]
> This worked fine in 3.8.1, may you please change it back for 3.8.4?
> We cannot use Maven 3.8.2 and 3.8.3 to release our components.
> ([~michael-o]: Ironically, I discovered this trying to create a release 
> candidate for Apache Commons CLI.)
> The exception in 3.8.3:
> {quote}Caused by: java.lang.UnsupportedOperationException
>  at java.util.Collections$UnmodifiableCollection.remove 
> (Collections.java:1060)
>  at 
> org.apache.commons.release.plugin.mojos.CommonsDistributionDetachmentMojo.execute
>  (CommonsDistributionDetachmentMojo.java:136)
>  at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:137)
> {quote}
>  



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

[jira] [Comment Edited] (MNG-7316) MavenProject.getAttachedArtifacts() regression with 3.8.1

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17544891#comment-17544891
 ] 

Gary D. Gregory edited comment on MNG-7316 at 6/1/22 12:59 PM:
---

Hi, [~chtompki] Any chance you can look at recoding the Apache Commons Maven 
plugin before 3.8.6 goes out the door? If you can recode it to avoid 
reflection, great, if not, we need a long-term solution instead of my 
reflection into the gut of Maven hack.


was (Author: garydgregory):
Hi, [~chtompki] Any chance you can look at recoding the Apache Commons Maven 
plugin before 3.8.6 goes out the door? We can recode it to avoid reflection, 
great, if not, we need a long-term solution instead of my reflection into the 
gut of Maven hack.

> MavenProject.getAttachedArtifacts() regression with 3.8.1
> -
>
> Key: MNG-7316
> URL: https://issues.apache.org/jira/browse/MNG-7316
> Project: Maven
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 3.8.2, 3.8.3
>Reporter: Gary D. Gregory
>Priority: Critical
> Fix For: waiting-for-feedback, wontfix-candidate
>
>
> The method {{MavenProject.getAttachedArtifacts()}} as of 3.8.2 breaks 
> releasing components for us at Apache Commons using our Maven Release plugin 
> because the list returned is now immutable, we now get an exception when 
> calling {{remove()}} on the collection returned by the API; see 
> [https://github.com/apache/commons-release-plugin/blob/master/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java#L137]
> This worked fine in 3.8.1, may you please change it back for 3.8.4?
> We cannot use Maven 3.8.2 and 3.8.3 to release our components.
> ([~michael-o]: Ironically, I discovered this trying to create a release 
> candidate for Apache Commons CLI.)
> The exception in 3.8.3:
> {quote}Caused by: java.lang.UnsupportedOperationException
>  at java.util.Collections$UnmodifiableCollection.remove 
> (Collections.java:1060)
>  at 
> org.apache.commons.release.plugin.mojos.CommonsDistributionDetachmentMojo.execute
>  (CommonsDistributionDetachmentMojo.java:136)
>  at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:137)
> {quote}
>  



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

[jira] [Commented] (MNG-7316) MavenProject.getAttachedArtifacts() regression with 3.8.1

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17544891#comment-17544891
 ] 

Gary D. Gregory commented on MNG-7316:
--

Hi [~chtompki] Any chance you can look at recoding the Apache Commons Maven 
plugin before 3.8.6 goes out the door? We can recode it to avoid reflection, 
great, if not, we need a long term solution instead of my reflection into the 
gut of Maven hack.

> MavenProject.getAttachedArtifacts() regression with 3.8.1
> -
>
> Key: MNG-7316
> URL: https://issues.apache.org/jira/browse/MNG-7316
> Project: Maven
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 3.8.2, 3.8.3
>Reporter: Gary D. Gregory
>Priority: Critical
> Fix For: waiting-for-feedback, wontfix-candidate
>
>
> The method {{MavenProject.getAttachedArtifacts()}} as of 3.8.2 breaks 
> releasing components for us at Apache Commons using our Maven Release plugin 
> because the list returned is now immutable, we now get an exception when 
> calling {{remove()}} on the collection returned by the API; see 
> [https://github.com/apache/commons-release-plugin/blob/master/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java#L137]
> This worked fine in 3.8.1, may you please change it back for 3.8.4?
> We cannot use Maven 3.8.2 and 3.8.3 to release our components.
> ([~michael-o]: Ironically, I discovered this trying to create a release 
> candidate for Apache Commons CLI.)
> The exception in 3.8.3:
> {quote}Caused by: java.lang.UnsupportedOperationException
>  at java.util.Collections$UnmodifiableCollection.remove 
> (Collections.java:1060)
>  at 
> org.apache.commons.release.plugin.mojos.CommonsDistributionDetachmentMojo.execute
>  (CommonsDistributionDetachmentMojo.java:136)
>  at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:137)
> {quote}
>  



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

[jira] [Comment Edited] (MNG-7316) MavenProject.getAttachedArtifacts() regression with 3.8.1

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17544891#comment-17544891
 ] 

Gary D. Gregory edited comment on MNG-7316 at 6/1/22 12:59 PM:
---

Hi, [~chtompki] Any chance you can look at recoding the Apache Commons Maven 
plugin before 3.8.6 goes out the door? If you can recode it to avoid 
reflection, great, if not, we need a long-term solution instead of my 
reflection into the guts of Maven hack.


was (Author: garydgregory):
Hi, [~chtompki] Any chance you can look at recoding the Apache Commons Maven 
plugin before 3.8.6 goes out the door? If you can recode it to avoid 
reflection, great, if not, we need a long-term solution instead of my 
reflection into the gut of Maven hack.

> MavenProject.getAttachedArtifacts() regression with 3.8.1
> -
>
> Key: MNG-7316
> URL: https://issues.apache.org/jira/browse/MNG-7316
> Project: Maven
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 3.8.2, 3.8.3
>Reporter: Gary D. Gregory
>Priority: Critical
> Fix For: waiting-for-feedback, wontfix-candidate
>
>
> The method {{MavenProject.getAttachedArtifacts()}} as of 3.8.2 breaks 
> releasing components for us at Apache Commons using our Maven Release plugin 
> because the list returned is now immutable, we now get an exception when 
> calling {{remove()}} on the collection returned by the API; see 
> [https://github.com/apache/commons-release-plugin/blob/master/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java#L137]
> This worked fine in 3.8.1, may you please change it back for 3.8.4?
> We cannot use Maven 3.8.2 and 3.8.3 to release our components.
> ([~michael-o]: Ironically, I discovered this trying to create a release 
> candidate for Apache Commons CLI.)
> The exception in 3.8.3:
> {quote}Caused by: java.lang.UnsupportedOperationException
>  at java.util.Collections$UnmodifiableCollection.remove 
> (Collections.java:1060)
>  at 
> org.apache.commons.release.plugin.mojos.CommonsDistributionDetachmentMojo.execute
>  (CommonsDistributionDetachmentMojo.java:136)
>  at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:137)
> {quote}
>  



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

[jira] [Commented] (MNG-7316) MavenProject.getAttachedArtifacts() regression with 3.8.1

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17519128#comment-17519128
 ] 

Gary D. Gregory commented on MNG-7316:
--

Hi [~chtompki] Any news?

> MavenProject.getAttachedArtifacts() regression with 3.8.1
> -
>
> Key: MNG-7316
> URL: https://issues.apache.org/jira/browse/MNG-7316
> Project: Maven
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 3.8.2, 3.8.3
>Reporter: Gary D. Gregory
>Priority: Critical
> Fix For: waiting-for-feedback, wontfix-candidate
>
>
> The method {{MavenProject.getAttachedArtifacts()}} as of 3.8.2 breaks 
> releasing components for us at Apache Commons using our Maven Release plugin 
> because the list returned is now immutable, we now get an exception when 
> calling {{remove()}} on the collection returned by the API; see 
> [https://github.com/apache/commons-release-plugin/blob/master/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java#L137]
> This worked fine in 3.8.1, may you please change it back for 3.8.4?
> We cannot use Maven 3.8.2 and 3.8.3 to release our components.
> ([~michael-o]: Ironically, I discovered this trying to create a release 
> candidate for Apache Commons CLI.)
> The exception in 3.8.3:
> {quote}Caused by: java.lang.UnsupportedOperationException
>  at java.util.Collections$UnmodifiableCollection.remove 
> (Collections.java:1060)
>  at 
> org.apache.commons.release.plugin.mojos.CommonsDistributionDetachmentMojo.execute
>  (CommonsDistributionDetachmentMojo.java:136)
>  at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:137)
> {quote}
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (MNG-7316) MavenProject.getAttachedArtifacts() regression with 3.8.1

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17507782#comment-17507782
 ] 

Gary D. Gregory commented on MNG-7316:
--

Hi Maven,

The hack I went for is to call {{MavenProject#setAttachedArtifacts(List)}} 
using reflection. Ugly, but we have to do {_}something{_}: 
[https://github.com/apache/commons-release-plugin/commit/36b02c2cba36637669c6faf680932a23a540fc0a]

So my request is to change {{MavenProject#setAttachedArtifacts(List)}} from 
{{protected}} to {{public}} unless someone can explain how we can code our 
plugin differently.

> MavenProject.getAttachedArtifacts() regression with 3.8.1
> -
>
> Key: MNG-7316
> URL: https://issues.apache.org/jira/browse/MNG-7316
> Project: Maven
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 3.8.2, 3.8.3
>Reporter: Gary D. Gregory
>Priority: Critical
> Fix For: waiting-for-feedback, wontfix-candidate
>
>
> The method {{MavenProject.getAttachedArtifacts()}} as of 3.8.2 breaks 
> releasing components for us at Apache Commons using our Maven Release plugin 
> because the list returned is now immutable, we now get an exception when 
> calling {{remove()}} on the collection returned by the API; see 
> [https://github.com/apache/commons-release-plugin/blob/master/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java#L137]
> This worked fine in 3.8.1, may you please change it back for 3.8.4?
> We cannot use Maven 3.8.2 and 3.8.3 to release our components.
> ([~michael-o]: Ironically, I discovered this trying to create a release 
> candidate for Apache Commons CLI.)
> The exception in 3.8.3:
> {quote}Caused by: java.lang.UnsupportedOperationException
>  at java.util.Collections$UnmodifiableCollection.remove 
> (Collections.java:1060)
>  at 
> org.apache.commons.release.plugin.mojos.CommonsDistributionDetachmentMojo.execute
>  (CommonsDistributionDetachmentMojo.java:136)
>  at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:137)
> {quote}
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (MPOM-275) use Shared GitHub Actions

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MPOM-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17494302#comment-17494302
 ] 

Gary D. Gregory commented on MPOM-275:
--

Where is this new feature documented?
TY

> use Shared GitHub Actions
> -
>
> Key: MPOM-275
> URL: https://issues.apache.org/jira/browse/MPOM-275
> Project: Maven POMs
>  Issue Type: New Feature
>  Components: asf
>Affects Versions: ASF-24
>Reporter: Slawomir Jaranowski
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: ASF-25
>
>




--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (MNG-7316) MavenProject.getAttachedArtifacts() regression with 3.8.1

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17493895#comment-17493895
 ] 

Gary D. Gregory commented on MNG-7316:
--

I am hoping [~chtompki] can pitch in, [~chtompki]?

> MavenProject.getAttachedArtifacts() regression with 3.8.1
> -
>
> Key: MNG-7316
> URL: https://issues.apache.org/jira/browse/MNG-7316
> Project: Maven
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 3.8.2, 3.8.3
>Reporter: Gary D. Gregory
>Priority: Critical
> Fix For: waiting-for-feedback
>
>
> The method {{MavenProject.getAttachedArtifacts()}} as of 3.8.2 breaks 
> releasing components for us at Apache Commons using our Maven Release plugin 
> because the list returned is now immutable, we now get an exception when 
> calling {{remove()}} on the collection returned by the API; see 
> [https://github.com/apache/commons-release-plugin/blob/master/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java#L137]
> This worked fine in 3.8.1, may you please change it back for 3.8.4?
> We cannot use Maven 3.8.2 and 3.8.3 to release our components.
> ([~michael-o]: Ironically, I discovered this trying to create a release 
> candidate for Apache Commons CLI.)
> The exception in 3.8.3:
> {quote}Caused by: java.lang.UnsupportedOperationException
>  at java.util.Collections$UnmodifiableCollection.remove 
> (Collections.java:1060)
>  at 
> org.apache.commons.release.plugin.mojos.CommonsDistributionDetachmentMojo.execute
>  (CommonsDistributionDetachmentMojo.java:136)
>  at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:137)
> {quote}
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (MRELEASE-1066) FileUtils.copyDirectory(File srcDir, File destDir) fails on Windows

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MRELEASE-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17467628#comment-17467628
 ] 

Gary D. Gregory commented on MRELEASE-1066:
---

>From a Java POV, the commit looks like a plain old bug fix. You can't just 
>leak file handles. An other negative side effect of leaving some IO instances 
>open, is that it puts more pressure on GC because some IO classes implement 
>finalization, and relying on that is an anti-pattern. Using the NIO Files 
>class to open files returns instances that do not implement finalization. 

> FileUtils.copyDirectory(File srcDir, File destDir) fails on Windows
> ---
>
> Key: MRELEASE-1066
> URL: https://issues.apache.org/jira/browse/MRELEASE-1066
> Project: Maven Release Plugin
>  Issue Type: Bug
>  Components: prepare
> Environment: Windows
>Reporter: Elliotte Rusty Harold
>Assignee: Slawomir Jaranowski
>Priority: Major
>  Labels: up-for-grabs
> Fix For: 3.0.0-M5
>
>
> This bug is shared (likely because of code copied from one place to another) 
> between the similar methods in commons IO, codehaus-plexus-utils, and 
> maven-shared-utils. 
> I don't have an isolated test case because this bug is platform specific and 
> I've only seen it in Travis CI builds on Windows using JDK 7 through 15. I 
> don't have a Windows system handy to test it. However it is reproducible. 
> Typical code that triggers it is in RestoreBackupPomsPhaseTest in 
> maven-release:
> ```
> // copy poms so tests are valid without clean
> File sourceDir = getTestFile( "src/test/resources" + projectPath );
> File testDir = getTestFile( "target/test-classes" + projectPath );
> FileUtils.copyDirectoryStructure( sourceDir, testDir );
> ```
> I don't know whether there might be something weird in the setup of those two 
> directories that's involved. 
> Typical error message is:
> Caused by: java.nio.file.FileSystemException:
> F:\jenkins\jenkins-slave\workspace\maven-box_maven-release_windows@2@2\windows-jdk8-m3.6.x_build\maven-release-manager\target\test-classes\projects\restore-backup-poms\basic-pom\pom.xml:
>  The process cannot access the file because it is being used by another 
> process
> "The process cannot access the file because it is being used by another 
> process" I think points to the root of the bug. This is a Windows file system 
> error message.
> Some history is here where I noticed it:
> https://github.com/apache/maven-release/pull/42
> In this case, I started with plexus-utils 3.1.0 which worked, upgraded t 
> plexus-utils 3.3.0, which didn't. And then tried the FileUtils.copyDirectory 
> from both maven-shared-utils and commons-io, all of which failed in the same 
> way. 
> I think this is caused by the use of NIO, which doesn't work quite the same 
> when copying files on Windows as on Linux and Mac OS X.
> Also see https://issues.apache.org/jira/browse/IO-663?filter=-2



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (MNG-7153) Maven cmd does errors out when "MAVEN_OPTS=-V"

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464508#comment-17464508
 ] 

Gary D. Gregory commented on MNG-7153:
--

[~michael-o] , thanks for the good news. This is for a future 4.0.0 only right?

 

> Maven cmd does errors out when "MAVEN_OPTS=-V"
> --
>
> Key: MNG-7153
> URL: https://issues.apache.org/jira/browse/MNG-7153
> Project: Maven
>  Issue Type: Bug
>Reporter: Gary D. Gregory
>Priority: Major
>
> As a user, I want to see the Maven version banner every time, so on Windows, 
> I "set MAVEN_OPTS=-V" which fails Maven on the next invocation with this 
> error:
> {noformat}
> Unrecognized option: -V
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit. {noformat}
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Comment Edited] (MNG-7316) MavenProject.getAttachedArtifacts() regression with 3.8.1

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17434311#comment-17434311
 ] 

Gary D. Gregory edited comment on MNG-7316 at 10/26/21, 12:10 PM:
--

I'd prefer [~chtompki] to reply since I think he authored that part of the 
plugin.

 
Allow me to point out our big picture here at the risk of outlining a topic you 
may already know. Strictly speaking, Apache releases tar/zip sources. These 
source files go to the Apache svn repo, which in turn makes them visible to the 
world, and get mirrored all over by 3rd parties. Tar/zip, binaries are a bonus, 
and they sit next to the tar/zip sources. As a double-bonus, we publish to 
Nexus, then Maven Central, not a strict requirement either. For all of this, we 
want to publish release candidates, then actual releases. A release candidate 
is tar/zip sources, tar/zip binaries, a website, plus artifacts in the Apache 
Maven Nexus repository. If the RC goes well, then all that moves from the dev 
to the release folder of the Apache svn repo, same releasing the RC out of 
Nexus to Maven Central. If an RC fails, the RC files go away, the git tag 
stays, no need to burn release numbers. We have 2 plugins that help us do all 
that. The latest Maven release breaks all that, bummer.
This is obviously a regression. The choices appear to me: 

* Simplest: put it back to the way it was
* Provide the remove functionality in whichever way you want, and we'll have to 
update our code

If the MavenProject class is so concerned with duplicates, why is it using a 
List instead of a Set to track attached artifacts? Wouldn't a LinkedHashSet 
reflect this intent best? You get order and uniqueness.


was (Author: garydgregory):
I'd prefer [~chtompki] to reply since I think he authored that part of the 
plugin.

 
Allow me to point out our big picture here at the risk of outlining a topic you 
may already know. Strictly speaking, Apache releases tar/zip sources. These 
source files go to the Apache svn repo, which in turn makes them visible to the 
world, and get mirrored all over by 3rd parties. Tar/zip, binaries are a bonus, 
and they sit next to the tar/zip sources. As a double-bonus, we publish to 
Nexus, then Maven Central, not a strict requirement either. For all of this, we 
want to publish release candidates, then actual releases. A release candidate 
is tar/zip sources, tar/zip binaries, a website, plus artifacts in the Apache 
Maven Nexus repository. If the RC goes well, then all that moves from the dev 
to the release folder of the Apache svn repo, same releasing the RC out of 
Nexus to Maven Central. If an RC fails, the RC files go away, the git tag 
stays, no need to burn release numbers. We have 2 plugins that help us do all 
that. The latest Maven release breaks all that, bummer.
This is obviously a regression. The choices appear to me: * Simplest: put it 
back to the way it was
 * Provide the remove functionality in whichever way you want, and we'll have 
to update our code

If the MavenProject class is so concerned with duplicates, why is it using a 
List instead of a Set to track attached artifacts? Wouldn't a LinkedHashSet 
reflect this intent best? You get order and uniqueness.

> MavenProject.getAttachedArtifacts() regression with 3.8.1
> -
>
> Key: MNG-7316
> URL: https://issues.apache.org/jira/browse/MNG-7316
> Project: Maven
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 3.8.2, 3.8.3
>Reporter: Gary D. Gregory
>Assignee: Michael Osipov
>Priority: Critical
> Fix For: 3.8.x-candidate
>
>
> The method {{MavenProject.getAttachedArtifacts()}} as of 3.8.2 breaks 
> releasing components for us at Apache Commons using our Maven Release plugin 
> because the list returned is now immutable, we now get an exception when 
> calling {{remove()}} on the collection returned by the API; see 
> [https://github.com/apache/commons-release-plugin/blob/master/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java#L137]
> This worked fine in 3.8.1, may you please change it back for 3.8.4?
> We cannot use Maven 3.8.2 and 3.8.3 to release our components.
> ([~michael-o]: Ironically, I discovered this trying to create a release 
> candidate for Apache Commons CLI.)
> The exception in 3.8.3:
> {quote}Caused by: java.lang.UnsupportedOperationException
>  at java.util.Collections$UnmodifiableCollection.remove 
> (Collections.java:1060)
>  at 
> org.apache.commons.release.plugin.mojos.CommonsDistributionDetachmentMojo.execute
>  (CommonsDistributionDetachmentMojo.java:136)
>  at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:137)
> {quote}
>  



--
This message was sent by Atlassian Jira

[jira] [Comment Edited] (MNG-7316) MavenProject.getAttachedArtifacts() regression with 3.8.1

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17434311#comment-17434311
 ] 

Gary D. Gregory edited comment on MNG-7316 at 10/26/21, 12:10 PM:
--

I'd prefer [~chtompki] to reply since I think he authored that part of our 
plugin.

Allow me to point out our big picture here at the risk of outlining a topic you 
may already know. Strictly speaking, Apache releases tar/zip sources. These 
source files go to the Apache svn repo, which in turn makes them visible to the 
world, and get mirrored all over by 3rd parties. Tar/zip, binaries are a bonus, 
and they sit next to the tar/zip sources. As a double-bonus, we publish to 
Nexus, then Maven Central, not a strict requirement either. For all of this, we 
want to publish release candidates, then actual releases. A release candidate 
is tar/zip sources, tar/zip binaries, a website, plus artifacts in the Apache 
Maven Nexus repository. If the RC goes well, then all that moves from the dev 
to the release folder of the Apache svn repo, same releasing the RC out of 
Nexus to Maven Central. If an RC fails, the RC files go away, the git tag 
stays, no need to burn release numbers. We have 2 plugins that help us do all 
that. The latest Maven release breaks all that, bummer.
 This is obviously a regression. The choices appear to me:
 * Simplest: put it back to the way it was
 * Provide the remove functionality in whichever way you want, and we'll have 
to update our code

If the MavenProject class is so concerned with duplicates, why is it using a 
List instead of a Set to track attached artifacts? Wouldn't a LinkedHashSet 
reflect this intent best? You get order and uniqueness.


was (Author: garydgregory):
I'd prefer [~chtompki] to reply since I think he authored that part of the 
plugin.

 
Allow me to point out our big picture here at the risk of outlining a topic you 
may already know. Strictly speaking, Apache releases tar/zip sources. These 
source files go to the Apache svn repo, which in turn makes them visible to the 
world, and get mirrored all over by 3rd parties. Tar/zip, binaries are a bonus, 
and they sit next to the tar/zip sources. As a double-bonus, we publish to 
Nexus, then Maven Central, not a strict requirement either. For all of this, we 
want to publish release candidates, then actual releases. A release candidate 
is tar/zip sources, tar/zip binaries, a website, plus artifacts in the Apache 
Maven Nexus repository. If the RC goes well, then all that moves from the dev 
to the release folder of the Apache svn repo, same releasing the RC out of 
Nexus to Maven Central. If an RC fails, the RC files go away, the git tag 
stays, no need to burn release numbers. We have 2 plugins that help us do all 
that. The latest Maven release breaks all that, bummer.
This is obviously a regression. The choices appear to me: 

* Simplest: put it back to the way it was
* Provide the remove functionality in whichever way you want, and we'll have to 
update our code

If the MavenProject class is so concerned with duplicates, why is it using a 
List instead of a Set to track attached artifacts? Wouldn't a LinkedHashSet 
reflect this intent best? You get order and uniqueness.

> MavenProject.getAttachedArtifacts() regression with 3.8.1
> -
>
> Key: MNG-7316
> URL: https://issues.apache.org/jira/browse/MNG-7316
> Project: Maven
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 3.8.2, 3.8.3
>Reporter: Gary D. Gregory
>Assignee: Michael Osipov
>Priority: Critical
> Fix For: 3.8.x-candidate
>
>
> The method {{MavenProject.getAttachedArtifacts()}} as of 3.8.2 breaks 
> releasing components for us at Apache Commons using our Maven Release plugin 
> because the list returned is now immutable, we now get an exception when 
> calling {{remove()}} on the collection returned by the API; see 
> [https://github.com/apache/commons-release-plugin/blob/master/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java#L137]
> This worked fine in 3.8.1, may you please change it back for 3.8.4?
> We cannot use Maven 3.8.2 and 3.8.3 to release our components.
> ([~michael-o]: Ironically, I discovered this trying to create a release 
> candidate for Apache Commons CLI.)
> The exception in 3.8.3:
> {quote}Caused by: java.lang.UnsupportedOperationException
>  at java.util.Collections$UnmodifiableCollection.remove 
> (Collections.java:1060)
>  at 
> org.apache.commons.release.plugin.mojos.CommonsDistributionDetachmentMojo.execute
>  (CommonsDistributionDetachmentMojo.java:136)
>  at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:137)
> {quote}
>  



--
This message was sent by Atlassian Jira

[jira] [Commented] (MNG-7316) MavenProject.getAttachedArtifacts() regression with 3.8.1

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17434311#comment-17434311
 ] 

Gary D. Gregory commented on MNG-7316:
--

I'd prefer [~chtompki] to reply since I think he authored that part of the 
plugin.

 
Allow me to point out our big picture here at the risk of outlining a topic you 
may already know. Strictly speaking, Apache releases tar/zip sources. These 
source files go to the Apache svn repo, which in turn makes them visible to the 
world, and get mirrored all over by 3rd parties. Tar/zip, binaries are a bonus, 
and they sit next to the tar/zip sources. As a double-bonus, we publish to 
Nexus, then Maven Central, not a strict requirement either. For all of this, we 
want to publish release candidates, then actual releases. A release candidate 
is tar/zip sources, tar/zip binaries, a website, plus artifacts in the Apache 
Maven Nexus repository. If the RC goes well, then all that moves from the dev 
to the release folder of the Apache svn repo, same releasing the RC out of 
Nexus to Maven Central. If an RC fails, the RC files go away, the git tag 
stays, no need to burn release numbers. We have 2 plugins that help us do all 
that. The latest Maven release breaks all that, bummer.
This is obviously a regression. The choices appear to me: * Simplest: put it 
back to the way it was
 * Provide the remove functionality in whichever way you want, and we'll have 
to update our code

If the MavenProject class is so concerned with duplicates, why is it using a 
List instead of a Set to track attached artifacts? Wouldn't a LinkedHashSet 
reflect this intent best? You get order and uniqueness.

> MavenProject.getAttachedArtifacts() regression with 3.8.1
> -
>
> Key: MNG-7316
> URL: https://issues.apache.org/jira/browse/MNG-7316
> Project: Maven
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 3.8.2, 3.8.3
>Reporter: Gary D. Gregory
>Assignee: Michael Osipov
>Priority: Critical
> Fix For: 3.8.x-candidate
>
>
> The method {{MavenProject.getAttachedArtifacts()}} as of 3.8.2 breaks 
> releasing components for us at Apache Commons using our Maven Release plugin 
> because the list returned is now immutable, we now get an exception when 
> calling {{remove()}} on the collection returned by the API; see 
> [https://github.com/apache/commons-release-plugin/blob/master/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java#L137]
> This worked fine in 3.8.1, may you please change it back for 3.8.4?
> We cannot use Maven 3.8.2 and 3.8.3 to release our components.
> ([~michael-o]: Ironically, I discovered this trying to create a release 
> candidate for Apache Commons CLI.)
> The exception in 3.8.3:
> {quote}Caused by: java.lang.UnsupportedOperationException
>  at java.util.Collections$UnmodifiableCollection.remove 
> (Collections.java:1060)
>  at 
> org.apache.commons.release.plugin.mojos.CommonsDistributionDetachmentMojo.execute
>  (CommonsDistributionDetachmentMojo.java:136)
>  at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:137)
> {quote}
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (MNG-7316) MavenProject.getAttachedArtifacts() regression with 3.8.1

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17433429#comment-17433429
 ] 

Gary D. Gregory commented on MNG-7316:
--

Adding {{removeAttachedArtifact()}} would work for us I think.

Note that the "add" API is deprecated so it does not feel matchy-matchy.

> MavenProject.getAttachedArtifacts() regression with 3.8.1
> -
>
> Key: MNG-7316
> URL: https://issues.apache.org/jira/browse/MNG-7316
> Project: Maven
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 3.8.2, 3.8.3
>Reporter: Gary D. Gregory
>Priority: Critical
>
> The method {{MavenProject.getAttachedArtifacts()}} as of 3.8.2 breaks 
> releasing components for us at Apache Commons using our Maven Release plugin 
> because the list returned is now immutable, we now get an exception when 
> calling {{remove()}} on the collection returned by the API; see 
> [https://github.com/apache/commons-release-plugin/blob/master/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java#L137]
> This worked fine in 3.8.1, may you please change it back for 3.8.4?
> We cannot use Maven 3.8.2 and 3.8.3 to release our components.
> ([~michael-o]: Ironically, I discovered this trying to create a release 
> candidate for Apache Commons CLI.)
> The exception in 3.8.3:
> {quote}Caused by: java.lang.UnsupportedOperationException
>  at java.util.Collections$UnmodifiableCollection.remove 
> (Collections.java:1060)
>  at 
> org.apache.commons.release.plugin.mojos.CommonsDistributionDetachmentMojo.execute
>  (CommonsDistributionDetachmentMojo.java:136)
>  at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:137)
> {quote}
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (MNG-7316) MavenProject.getAttachedArtifacts() regression with 3.8.1

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17433393#comment-17433393
 ] 

Gary D. Gregory commented on MNG-7316:
--

Hi [~chtompki], would you comment, please?

> MavenProject.getAttachedArtifacts() regression with 3.8.1
> -
>
> Key: MNG-7316
> URL: https://issues.apache.org/jira/browse/MNG-7316
> Project: Maven
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 3.8.2, 3.8.3
>Reporter: Gary D. Gregory
>Priority: Critical
>
> The method {{MavenProject.getAttachedArtifacts()}} as of 3.8.2 breaks 
> releasing components for us at Apache Commons using our Maven Release plugin 
> because the list returned is now immutable, we now get an exception when 
> calling {{remove()}} on the collection returned by the API; see 
> [https://github.com/apache/commons-release-plugin/blob/master/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java#L137]
> This worked fine in 3.8.1, may you please change it back for 3.8.4?
> We cannot use Maven 3.8.2 and 3.8.3 to release our components.
> ([~michael-o]: Ironically, I discovered this trying to create a release 
> candidate for Apache Commons CLI.)
> The exception in 3.8.3:
> {quote}Caused by: java.lang.UnsupportedOperationException
>  at java.util.Collections$UnmodifiableCollection.remove 
> (Collections.java:1060)
>  at 
> org.apache.commons.release.plugin.mojos.CommonsDistributionDetachmentMojo.execute
>  (CommonsDistributionDetachmentMojo.java:136)
>  at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:137)
> {quote}
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (MNG-7316) MavenProject.getAttachedArtifacts() regression with 3.8.1

[Gary D. Gregory (Jira)]

 [ 
https://issues.apache.org/jira/browse/MNG-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gary D. Gregory updated MNG-7316:
-
Description: 
The method {{MavenProject.getAttachedArtifacts()}} as of 3.8.2 breaks releasing 
components for us at Apache Commons using our Maven Release plugin because the 
list returned is now immutable, we now get an exception when calling 
{{remove()}} on the collection returned by the API; see 
[https://github.com/apache/commons-release-plugin/blob/master/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java#L137]

This worked fine in 3.8.1, may you please change it back for 3.8.4?

We cannot use Maven 3.8.2 and 3.8.3 to release our components.

([~michael-o]: Ironically, I discovered this trying to create a release 
candidate for Apache Commons CLI.)

The exception in 3.8.3:

{quote}Caused by: java.lang.UnsupportedOperationException
 at java.util.Collections$UnmodifiableCollection.remove (Collections.java:1060)
 at 
org.apache.commons.release.plugin.mojos.CommonsDistributionDetachmentMojo.execute
 (CommonsDistributionDetachmentMojo.java:136)
 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
(DefaultBuildPluginManager.java:137)
{quote}
 

  was:
The method {{MavenProject.getAttachedArtifacts()}} as of 3.8.2 breaks releasing 
components for us at Apache Commons using our Maven Release plugin because the 
list returned is now immutable, we now get an exception when calling 
{{remove()}} on the collection returned by the API; see 
[https://github.com/apache/commons-release-plugin/blob/master/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java#L137]

This worked fine in 3.8.1, may you please change it back for 3.8.4?

We cannot use Maven 3.8.2 and 3.8.3 to release our components.

 ([~michael-o]: Ironically, I discovered this trying to create a release 
candidate for Apache Commons CLI.)


> MavenProject.getAttachedArtifacts() regression with 3.8.1
> -
>
> Key: MNG-7316
> URL: https://issues.apache.org/jira/browse/MNG-7316
> Project: Maven
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 3.8.2, 3.8.3
>Reporter: Gary D. Gregory
>Priority: Critical
>
> The method {{MavenProject.getAttachedArtifacts()}} as of 3.8.2 breaks 
> releasing components for us at Apache Commons using our Maven Release plugin 
> because the list returned is now immutable, we now get an exception when 
> calling {{remove()}} on the collection returned by the API; see 
> [https://github.com/apache/commons-release-plugin/blob/master/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java#L137]
> This worked fine in 3.8.1, may you please change it back for 3.8.4?
> We cannot use Maven 3.8.2 and 3.8.3 to release our components.
> ([~michael-o]: Ironically, I discovered this trying to create a release 
> candidate for Apache Commons CLI.)
> The exception in 3.8.3:
> {quote}Caused by: java.lang.UnsupportedOperationException
>  at java.util.Collections$UnmodifiableCollection.remove 
> (Collections.java:1060)
>  at 
> org.apache.commons.release.plugin.mojos.CommonsDistributionDetachmentMojo.execute
>  (CommonsDistributionDetachmentMojo.java:136)
>  at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:137)
> {quote}
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (MNG-7316) MavenProject.getAttachedArtifacts() regression with 3.8.1

[Gary D. Gregory (Jira)]

 [ 
https://issues.apache.org/jira/browse/MNG-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gary D. Gregory updated MNG-7316:
-
External issue URL: https://github.com/apache/maven/pull/601

> MavenProject.getAttachedArtifacts() regression with 3.8.1
> -
>
> Key: MNG-7316
> URL: https://issues.apache.org/jira/browse/MNG-7316
> Project: Maven
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 3.8.2, 3.8.3
>Reporter: Gary D. Gregory
>Priority: Critical
>
> The method {{MavenProject.getAttachedArtifacts()}} as of 3.8.2 breaks 
> releasing components for us at Apache Commons using our Maven Release plugin 
> because the list returned is now immutable, we now get an exception when 
> calling {{remove()}} on the collection returned by the API; see 
> [https://github.com/apache/commons-release-plugin/blob/master/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java#L137]
> This worked fine in 3.8.1, may you please change it back for 3.8.4?
> We cannot use Maven 3.8.2 and 3.8.3 to release our components.
>  ([~michael-o]: Ironically, I discovered this trying to create a release 
> candidate for Apache Commons CLI.)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (MNG-7316) MavenProject.getAttachedArtifacts() regression with 3.8.1

[Gary D. Gregory (Jira)]

 [ 
https://issues.apache.org/jira/browse/MNG-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gary D. Gregory updated MNG-7316:
-
Description: 
The method {{MavenProject.getAttachedArtifacts()}} as of 3.8.2 breaks releasing 
components for us at Apache Commons using our Maven Release plugin because the 
list returned is now immutable, we now get an exception when calling 
{{remove()}} on the collection returned by the API; see 
[https://github.com/apache/commons-release-plugin/blob/master/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java#L137]

This worked fine in 3.8.1, may you please change it back for 3.8.4?

We cannot use Maven 3.8.2 and 3.8.3 to release our components.

 ([~michael-o]: Ironically, I discovered this trying to create a release 
candidate for Apache Commons CLI.)

  was:
The method {{MavenProject.getAttachedArtifacts()}} as of 3.8.2 breaks releasing 
components for us at Apache Commons using our Maven Release plugin because the 
list returned is now immutable, we now get an exception when calling 
{{remove()}} on the collection returned by the API; see 
[https://github.com/apache/commons-release-plugin/blob/master/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java#L137]

This worked fine in 3.8.1, may you please change it back for 3.8.4?

We cannot use Maven 3.8.2 and 3.8.3 to release our components.

 


> MavenProject.getAttachedArtifacts() regression with 3.8.1
> -
>
> Key: MNG-7316
> URL: https://issues.apache.org/jira/browse/MNG-7316
> Project: Maven
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 3.8.2, 3.8.3
>Reporter: Gary D. Gregory
>Priority: Critical
>
> The method {{MavenProject.getAttachedArtifacts()}} as of 3.8.2 breaks 
> releasing components for us at Apache Commons using our Maven Release plugin 
> because the list returned is now immutable, we now get an exception when 
> calling {{remove()}} on the collection returned by the API; see 
> [https://github.com/apache/commons-release-plugin/blob/master/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java#L137]
> This worked fine in 3.8.1, may you please change it back for 3.8.4?
> We cannot use Maven 3.8.2 and 3.8.3 to release our components.
>  ([~michael-o]: Ironically, I discovered this trying to create a release 
> candidate for Apache Commons CLI.)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (MNG-7316) MavenProject.getAttachedArtifacts() regression with 3.8.1

[Gary D. Gregory (Jira)]

Gary D. Gregory created MNG-7316:


 Summary: MavenProject.getAttachedArtifacts() regression with 3.8.1
 Key: MNG-7316
 URL: https://issues.apache.org/jira/browse/MNG-7316
 Project: Maven
  Issue Type: Bug
  Components: Core
Affects Versions: 3.8.3, 3.8.2
Reporter: Gary D. Gregory


The method {{MavenProject.getAttachedArtifacts()}} as of 3.8.2 breaks releasing 
components for us at Apache Commons using our Maven Release plugin because the 
list returned is now immutable, we now get an exception when calling 
{{remove()}} on the collection returned by the API; see 
[https://github.com/apache/commons-release-plugin/blob/master/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java#L137]

This worked fine in 3.8.1, may you please change it back for 3.8.4?

We cannot use Maven 3.8.2 and 3.8.3 to release our components.

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (MNG-7217) Completely update CLI handling according to Commons CLI 1.4 documentation

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17428158#comment-17428158
 ] 

Gary D. Gregory commented on MNG-7217:
--

[~michael-o],

I am still reviewing PRs but I hope to have a release "soon".

 

> Completely update CLI handling according to Commons CLI 1.4 documentation
> -
>
> Key: MNG-7217
> URL: https://issues.apache.org/jira/browse/MNG-7217
> Project: Maven
>  Issue Type: Task
>  Components: Command Line
>Reporter: Michael Osipov
>Priority: Major
> Fix For: 4.0.x-candidate
>
>
> We currently don't have code which complies with the documentation of Commons 
> CLI 1.4. As soon as we move we can address a few issues, e.g., support of 
> {{--}} to separate options from real args.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Comment Edited] (MNG-6042) Properties defined in POM>properties are not resolved in POM repositories>repository>url

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17417738#comment-17417738
 ] 

Gary D. Gregory edited comment on MNG-6042 at 9/20/21, 5:12 PM:


In my case the problem happens when the parent POM is sought:
{noformat}
13:03:18.83 C:\d3vsrc\git\rocket\access-and-connectivity-agent>mvn -U -V clean 
install assembly:single -V
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: C:\Java\apache-maven-3.6.3\bin\..
Java version: 1.8.0_302, vendor: Temurin, runtime: C:\Program Files\Eclipse 
Foundation\jdk-8.0.302.8-hotspot\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
[INFO] Scanning for projects...
Downloading from central: 
https://repo.maven.apache.org/maven2/com/rs/seagull/com.rs.seagull.master/1.0.4/com.rs.seagull.master-1.0.4.pom
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for 
com.rs.seagull.centipede:http-monitor:10.1.2-SNAPSHOT: Could not transfer 
artifact com.rs.seagull:com.rs.seagull.master:pom:1.0.4 from/to 
artifactory-release (${rs.repo}/rocket-maven-release-local): Cannot access 
${rs.repo}/rocket-maven-release-local with type default using the available 
connector factories: BasicRepositoryConnectorFactory and 'parent.relativePath' 
points at wrong local POM @ line 16, column 11
 @
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project com.rs.seagull.centipede:http-monitor:10.1.2-SNAPSHOT 
(C:\d3vsrc\git\rocket\access-and-connectivity-agent\pom.xml) has 1 error
[ERROR] Non-resolvable parent POM for 
com.rs.seagull.centipede:http-monitor:10.1.2-SNAPSHOT: Could not transfer 
artifact com.rs.seagull:com.rs.seagull.master:pom:1.0.4 from/to 
artifactory-release (${rs.repo}/rocket-maven-release-local): Cannot access 
${rs.repo}/rocket-maven-release-local with type default using the available 
connector factories: BasicRepositoryConnectorFactory and 'parent.relativePath' 
points at wrong local POM @ line 16, column 11: Cannot access 
${rs.repo}/rocket-maven-release-local using the registered transporter 
factories: WagonTransporterFactory: Unsupported transport protocol -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] 
http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
{noformat}
So this might be restricted to resolving the parent POM only. Our company's 
parent POM of course will not be in [https://repo.maven.apache.org/maven2]. We 
have three custom repos listed first in our POM before the Apache Snapshot repo 
like the one in error above: ${rs.repo}/rocket-maven-release-local

(I don't have karma to reopen this ticket)


was (Author: garydgregory):
In my case the problem happens when the parent POM is sought:
{noformat}
13:03:18.83 C:\d3vsrc\git\rocket\access-and-connectivity-agent>mvn -U -V clean 
install assembly:single -V
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: C:\Java\apache-maven-3.6.3\bin\..
Java version: 1.8.0_302, vendor: Temurin, runtime: C:\Program Files\Eclipse 
Foundation\jdk-8.0.302.8-hotspot\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
[INFO] Scanning for projects...
Downloading from central: 
https://repo.maven.apache.org/maven2/com/rs/seagull/com.rs.seagull.master/1.0.4/com.rs.seagull.master-1.0.4.pom
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for 
com.rs.seagull.centipede:http-monitor:10.1.2-SNAPSHOT: Could not transfer 
artifact com.rs.seagull:com.rs.seagull.master:pom:1.0.4 from/to 
artifactory-release (${rs.repo}/rocket-maven-release-local): Cannot access 
${rs.repo}/rocket-maven-release-local with type default using the available 
connector factories: BasicRepositoryConnectorFactory and 'parent.relativePath' 
points at wrong local POM @ line 16, column 11
 @
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project com.rs.seagull.centipede:http-monitor:10.1.2-SNAPSHOT 
(C:\d3vsrc\git\rocket\access-and-connectivity-agent\pom.xml) has 1 error
[ERROR] Non-resolvable parent POM for 
com.rs.seagull.centipede:http-monitor:10.1.2-SNAPSHOT: Could not transfer 
artifact com.rs.seagull:com.rs.seagull.master:pom:1.0.4 from/to 
artifactory-release (${rs.repo}/rocket-maven-release-local): Cannot access 
${rs.repo}/rocket-maven-release-local with type default using the available 

[jira] [Commented] (MNG-6042) Properties defined in POM>properties are not resolved in POM repositories>repository>url

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17417738#comment-17417738
 ] 

Gary D. Gregory commented on MNG-6042:
--

In my case the problem happens when the parent POM is sought:
{noformat}
13:03:18.83 C:\d3vsrc\git\rocket\access-and-connectivity-agent>mvn -U -V clean 
install assembly:single -V
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: C:\Java\apache-maven-3.6.3\bin\..
Java version: 1.8.0_302, vendor: Temurin, runtime: C:\Program Files\Eclipse 
Foundation\jdk-8.0.302.8-hotspot\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
[INFO] Scanning for projects...
Downloading from central: 
https://repo.maven.apache.org/maven2/com/rs/seagull/com.rs.seagull.master/1.0.4/com.rs.seagull.master-1.0.4.pom
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for 
com.rs.seagull.centipede:http-monitor:10.1.2-SNAPSHOT: Could not transfer 
artifact com.rs.seagull:com.rs.seagull.master:pom:1.0.4 from/to 
artifactory-release (${rs.repo}/rocket-maven-release-local): Cannot access 
${rs.repo}/rocket-maven-release-local with type default using the available 
connector factories: BasicRepositoryConnectorFactory and 'parent.relativePath' 
points at wrong local POM @ line 16, column 11
 @
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project com.rs.seagull.centipede:http-monitor:10.1.2-SNAPSHOT 
(C:\d3vsrc\git\rocket\access-and-connectivity-agent\pom.xml) has 1 error
[ERROR] Non-resolvable parent POM for 
com.rs.seagull.centipede:http-monitor:10.1.2-SNAPSHOT: Could not transfer 
artifact com.rs.seagull:com.rs.seagull.master:pom:1.0.4 from/to 
artifactory-release (${rs.repo}/rocket-maven-release-local): Cannot access 
${rs.repo}/rocket-maven-release-local with type default using the available 
connector factories: BasicRepositoryConnectorFactory and 'parent.relativePath' 
points at wrong local POM @ line 16, column 11: Cannot access 
${rs.repo}/rocket-maven-release-local using the registered transporter 
factories: WagonTransporterFactory: Unsupported transport protocol -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] 
http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
{noformat}
So this might be restricted to resolving the parent POM only. Our company's 
parent POM of course will not be in https://repo.maven.apache.org/maven2. We 
have three custom repos listed first in our POM before the Apache Snapshot repo 
like the one in error above: ${rs.repo}/rocket-maven-release-local


> Properties defined in POM>properties are not resolved in POM 
> repositories>repository>url
> 
>
> Key: MNG-6042
> URL: https://issues.apache.org/jira/browse/MNG-6042
> Project: Maven
>  Issue Type: Bug
>Affects Versions: 3.3.9
> Environment: Apache Maven 3.3.9 
> (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T08:41:47-08:00)
> Maven home: E:\Java\apache-maven-3.3.9
> Java version: 1.7.0_79, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_79\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>Reporter: Gary D. Gregory
>Priority: Major
>
> Properties defined in POM>properties are not resolved in POM 
> repositories>repository>url.
> For example:
> {code:xml}
>   ...
>   
> ...
> http://example.com/artifactory
>   
>   
> 
>   artifactory-libs
>   ${rs.repo}/libs-release-local
> 
>...
>   
>   ...
> {code}
> This will give me errors showing {{$\{rs.repo\}/libs-release-local}} instead 
> of the resolved property.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (MNG-6042) Properties defined in POM>properties are not resolved in POM repositories>repository>url

[Gary D. Gregory (Jira)]

 [ 
https://issues.apache.org/jira/browse/MNG-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gary D. Gregory updated MNG-6042:
-
Affects Version/s: 3.6.3

> Properties defined in POM>properties are not resolved in POM 
> repositories>repository>url
> 
>
> Key: MNG-6042
> URL: https://issues.apache.org/jira/browse/MNG-6042
> Project: Maven
>  Issue Type: Bug
>Affects Versions: 3.3.9, 3.6.3
> Environment: Apache Maven 3.3.9 
> (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T08:41:47-08:00)
> Maven home: E:\Java\apache-maven-3.3.9
> Java version: 1.7.0_79, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_79\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>Reporter: Gary D. Gregory
>Priority: Major
>
> Properties defined in POM>properties are not resolved in POM 
> repositories>repository>url.
> For example:
> {code:xml}
>   ...
>   
> ...
> http://example.com/artifactory
>   
>   
> 
>   artifactory-libs
>   ${rs.repo}/libs-release-local
> 
>...
>   
>   ...
> {code}
> This will give me errors showing {{$\{rs.repo\}/libs-release-local}} instead 
> of the resolved property.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Issue Comment Deleted] (MNG-6042) Properties defined in POM>properties are not resolved in POM repositories>repository>url

[Gary D. Gregory (Jira)]

 [ 
https://issues.apache.org/jira/browse/MNG-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gary D. Gregory updated MNG-6042:
-
Comment: was deleted

(was: Works OK in Apache Maven 3.6.3 
(cecedd343002696d0abb50b32b541b8a6ba2883f).)

> Properties defined in POM>properties are not resolved in POM 
> repositories>repository>url
> 
>
> Key: MNG-6042
> URL: https://issues.apache.org/jira/browse/MNG-6042
> Project: Maven
>  Issue Type: Bug
>Affects Versions: 3.3.9
> Environment: Apache Maven 3.3.9 
> (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T08:41:47-08:00)
> Maven home: E:\Java\apache-maven-3.3.9
> Java version: 1.7.0_79, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_79\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>Reporter: Gary D. Gregory
>Priority: Major
>
> Properties defined in POM>properties are not resolved in POM 
> repositories>repository>url.
> For example:
> {code:xml}
>   ...
>   
> ...
> http://example.com/artifactory
>   
>   
> 
>   artifactory-libs
>   ${rs.repo}/libs-release-local
> 
>...
>   
>   ...
> {code}
> This will give me errors showing {{$\{rs.repo\}/libs-release-local}} instead 
> of the resolved property.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (MNG-6042) Properties defined in POM>properties are not resolved in POM repositories>repository>url

[Gary D. Gregory (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17417696#comment-17417696
 ] 

Gary D. Gregory commented on MNG-6042:
--

Works OK in Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f).

> Properties defined in POM>properties are not resolved in POM 
> repositories>repository>url
> 
>
> Key: MNG-6042
> URL: https://issues.apache.org/jira/browse/MNG-6042
> Project: Maven
>  Issue Type: Bug
>Affects Versions: 3.3.9
> Environment: Apache Maven 3.3.9 
> (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T08:41:47-08:00)
> Maven home: E:\Java\apache-maven-3.3.9
> Java version: 1.7.0_79, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_79\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>Reporter: Gary D. Gregory
>Priority: Major
>
> Properties defined in POM>properties are not resolved in POM 
> repositories>repository>url.
> For example:
> {code:xml}
>   ...
>   
> ...
> http://example.com/artifactory
>   
>   
> 
>   artifactory-libs
>   ${rs.repo}/libs-release-local
> 
>...
>   
>   ...
> {code}
> This will give me errors showing {{$\{rs.repo\}/libs-release-local}} instead 
> of the resolved property.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)