[jira] [Comment Edited] (MNG-6109) PluginDescriptor doesn't read since value of parameter
[
https://issues.apache.org/jira/browse/MNG-6109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15623418#comment-15623418
]
Hervé Boutemy edited comment on MNG-6109 at 1/14/17 3:36 AM:
-
SUCCESS: Integrated in Jenkins build maven-3.x #1404 (See
[https://builds.apache.org/job/maven-3.x/1404/])
[MNG-6109] PluginDescriptor doesn't read since value of parameter (rfscholte:
rev
http://git-wip-us.apache.org/repos/asf/maven/commit/a277f6f43a9b52c17b6aa2af069554edd2b0e42e)
* (edit)
maven-plugin-api/src/main/java/org/apache/maven/plugin/descriptor/PluginDescriptorBuilder.java
* (edit)
maven-plugin-api/src/test/java/org/apache/maven/plugin/descriptor/PluginDescriptorBuilderTest.java
* (edit) maven-plugin-api/src/test/resources/plugin.xml
was (Author: hudson):
SUCCESS: Integrated in Jenkins build maven-3.x #1404 (See
[https://builds.apache.org/job/maven-3.x/1404/])
[MNG-6109] PluginDescriptor doesn't read since value of parameter (rfscholte:
rev a277f6f43a9b52c17b6aa2af069554edd2b0e42e)
* (edit)
maven-plugin-api/src/main/java/org/apache/maven/plugin/descriptor/PluginDescriptorBuilder.java
* (edit)
maven-plugin-api/src/test/java/org/apache/maven/plugin/descriptor/PluginDescriptorBuilderTest.java
* (edit) maven-plugin-api/src/test/resources/plugin.xml
> PluginDescriptor doesn't read since value of parameter
> --
>
> Key: MNG-6109
> URL: https://issues.apache.org/jira/browse/MNG-6109
> Project: Maven
> Issue Type: Bug
> Components: Plugin API
>Affects Versions: 3.3.9
>Reporter: Robert Scholte
>Assignee: Robert Scholte
> Fix For: 3.5.0-candidate
>
>
> This causes missing information for code manipulating plugins "normally"
> through PluginDescriptor read by Maven core from
> {{META-INF/maven/plugin.xml}}.
> For example MPLUGIN-319, which parses code to create PluginDescriptor then
> generate {{META-INF/maven/plugin.xml}}, but gets truncated info when getting
> back PluginDescriptor as read by Maven core...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MNG-6109) PluginDescriptor doesn't read since value of parameter
[
https://issues.apache.org/jira/browse/MNG-6109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MNG-6109:
---
Description:
This causes missing information for code manipulating plugins "normally"
through PluginDescriptor read by Maven core from {{META-INF/maven/plugin.xml}}.
For example MPLUGIN-319, which parses code to create PluginDescriptor then
generate {{META-INF/maven/plugin.xml}}, but gets truncated info when getting
back PluginDescriptor as read by Maven core...
> PluginDescriptor doesn't read since value of parameter
> --
>
> Key: MNG-6109
> URL: https://issues.apache.org/jira/browse/MNG-6109
> Project: Maven
> Issue Type: Bug
> Components: Plugin API
>Affects Versions: 3.3.9
>Reporter: Robert Scholte
>Assignee: Robert Scholte
> Fix For: 3.5.0-candidate
>
>
> This causes missing information for code manipulating plugins "normally"
> through PluginDescriptor read by Maven core from
> {{META-INF/maven/plugin.xml}}.
> For example MPLUGIN-319, which parses code to create PluginDescriptor then
> generate {{META-INF/maven/plugin.xml}}, but gets truncated info when getting
> back PluginDescriptor as read by Maven core...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (MNG-6109) PluginDescriptor doesn't read since value of parameter
[ https://issues.apache.org/jira/browse/MNG-6109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MNG-6109: --- Comment: was deleted (was: FAILURE: Integrated in Jenkins build maven-plugin-tools Jigsaw #4 (See [https://builds.apache.org/job/maven-plugin-tools%20Jigsaw/4/]) [MPLUGIN-319] @since values ignored in report Only use plugin.xml for M3.4.0 and above due to MNG-6109 (rfscholte: [http://svn.apache.org/viewvc/?view=rev&rev=1770562]) * (add) maven-plugin-plugin/src/it/mplugin-329_report-since * (add) maven-plugin-plugin/src/it/mplugin-329_report-since/invoker.properties * (add) maven-plugin-plugin/src/it/mplugin-329_report-since/pom.xml * (add) maven-plugin-plugin/src/it/mplugin-329_report-since/src * (add) maven-plugin-plugin/src/it/mplugin-329_report-since/src/main * (add) maven-plugin-plugin/src/it/mplugin-329_report-since/src/main/java * (add) maven-plugin-plugin/src/it/mplugin-329_report-since/src/main/java/org * (add) maven-plugin-plugin/src/it/mplugin-329_report-since/src/main/java/org/MyMojo.java * (add) maven-plugin-plugin/src/it/mplugin-329_report-since/verify.groovy * (edit) maven-plugin-plugin/src/it/plugin-info-jdk/pom.xml * (edit) maven-plugin-plugin/src/main/java/org/apache/maven/plugin/plugin/PluginReport.java ) > PluginDescriptor doesn't read since value of parameter > -- > > Key: MNG-6109 > URL: https://issues.apache.org/jira/browse/MNG-6109 > Project: Maven > Issue Type: Bug > Components: Plugin API >Affects Versions: 3.3.9 >Reporter: Robert Scholte >Assignee: Robert Scholte > Fix For: 3.5.0-candidate > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (MNG-6109) PluginDescriptor doesn't read since value of parameter
[ https://issues.apache.org/jira/browse/MNG-6109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MNG-6109: --- Comment: was deleted (was: FAILURE: Integrated in Jenkins build maven-3.x Jigsaw #3 (See [https://builds.apache.org/job/maven-3.x%20Jigsaw/3/]) [MNG-6109] PluginDescriptor doesn't read since value of parameter (rfscholte: rev a277f6f43a9b52c17b6aa2af069554edd2b0e42e) * (edit) maven-plugin-api/src/main/java/org/apache/maven/plugin/descriptor/PluginDescriptorBuilder.java * (edit) maven-plugin-api/src/test/resources/plugin.xml * (edit) maven-plugin-api/src/test/java/org/apache/maven/plugin/descriptor/PluginDescriptorBuilderTest.java ) > PluginDescriptor doesn't read since value of parameter > -- > > Key: MNG-6109 > URL: https://issues.apache.org/jira/browse/MNG-6109 > Project: Maven > Issue Type: Bug > Components: Plugin API >Affects Versions: 3.3.9 >Reporter: Robert Scholte >Assignee: Robert Scholte > Fix For: 3.5.0-candidate > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MNG-6157) org.codehaus.plexus.component.repository.exception.ComponentLookupException: java.util.NoSuchElementException
[
https://issues.apache.org/jira/browse/MNG-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822018#comment-15822018
]
Hervé Boutemy edited comment on MNG-6157 at 1/14/17 3:01 AM:
-
Root cause is not inside Maven.
was (Author: rfscholte):
Root cause it not inside Maven.
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> java.util.NoSuchElementException
> -
>
> Key: MNG-6157
> URL: https://issues.apache.org/jira/browse/MNG-6157
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.3.9
>Reporter: Michael Vorburger
>Assignee: Robert Scholte
>Priority: Critical
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=496944 (and
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=510439) report an issue
> encountered in M2E which shows a
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> java.util.NoSuchElementException as the root caused by, so the underlying
> problem may be here in Maven core?
> May be a concurrency issue - could it be made more multi thread safe?
> {code}org.apache.maven.plugin.PluginExecutionException: Execution
> default-testResources of goal
> org.apache.maven.plugins:maven-resources-plugin:3.0.1:testResources failed:
> Unable to load the mojo 'testResources' (or one of its required components)
> from the plugin 'org.apache.maven.plugins:maven-resources-plugin:3.0.1'
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:153)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:331)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1362)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1360)
> at
> org.eclipse.m2e.core.project.configurator.MojoExecutionBuildParticipant.build(MojoExecutionBuildParticipant.java:52)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:137)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:172)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:1)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1$1.call(MavenBuilder.java:115)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:105)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200)
> at
> org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at
> org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
> at
> org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
> at
> org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:142)
> at
> org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:232)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: org.apache.maven.plugin.PluginContainerException: Unable to load
> the mojo 'testResources' (or one of its required components)
[jira] [Updated] (MCHECKSTYLE-333) Intermittent NPE on checkstyle:check
[
https://issues.apache.org/jira/browse/MCHECKSTYLE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Short updated MCHECKSTYLE-333:
Environment: OSX El Captain, java 8, maven 3.x, checkstyle 6.19 (was: OSX
El Captain, maven 3.x, checkstyle 6.19)
> Intermittent NPE on checkstyle:check
>
>
> Key: MCHECKSTYLE-333
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-333
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.17
> Environment: OSX El Captain, java 8, maven 3.x, checkstyle 6.19
>Reporter: James Short
>
> I generally run checkstyle:check manually but I wanted to integrate it into
> the validate phase of my root build.
> After doing this, it will intermittent fail with an NPE:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (checkstyle) on
> project dropwizard-api: Execution checkstyle of goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed.
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (checkstyle)
> on project dropwizard-api: Execution checkstyle of goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> 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:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> checkstyle of goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 20 more
> Caused by: java.lang.NullPointerException
> at java.util.zip.ZipFile.getZipEntry(ZipFile.java:566)
> at java.util.zip.ZipFile.access$900(ZipFile.java:60)
> at java.util.zip.ZipFile$ZipEntryIterator.next(ZipFile.java:524)
> at java.util.zip.ZipFile$ZipEntryIterator.nextElement(ZipFile.java:499)
> at java.util.zip.ZipFile$ZipEntryIterator.nextElement(ZipFile.java:480)
> at java.util.jar.JarFile$JarEntryIterator.next(JarFile.java:257)
> at java.util.jar.JarFile$JarEntryIterator.nextElement(JarFile.java:266)
> at java.util.jar.JarFile$JarEntryIterator.nextElement(JarFile.java:247)
> at
> org.codehaus.plexus.resource.loader.JarHolder.getEntries(JarHolder.java:132)
> at
> org.codehaus.plexus.resource.loader.JarResourceLoader.loadJar(JarResourceLoader.java:100)
> at
> org.codehaus.plexus.resource.loader.JarResourceLoader.initialize(JarResourceLoader.java:63)
> at
> org.codehaus.plexus.resource.loader.JarResourceLoader.getResource(JarResourceLoader.java:141)
> at
> org.apache.maven.plugin.checkstyle.resource.LicenseResourceManager.getResource(LicenseResourceManager.java:75)
> at
> org.codehaus.plexus.resource.DefaultResourceManager.getResourceAsFil
[jira] [Commented] (MCHECKSTYLE-333) Intermittent NPE on checkstyle:check
[
https://issues.apache.org/jira/browse/MCHECKSTYLE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822453#comment-15822453
]
James Short commented on MCHECKSTYLE-333:
-
I changed it run during the compile phase and ran `mvn clean install` 10-12
times before it failed in the same way (this is far less frequent that when run
during the verify phase).
Without my config above, checkstyle:check does not run during the verify phase
(unless verify is not run by default with install).
> Intermittent NPE on checkstyle:check
>
>
> Key: MCHECKSTYLE-333
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-333
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.17
> Environment: OSX El Captain, maven 3.x, checkstyle 6.19
>Reporter: James Short
>
> I generally run checkstyle:check manually but I wanted to integrate it into
> the validate phase of my root build.
> After doing this, it will intermittent fail with an NPE:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (checkstyle) on
> project dropwizard-api: Execution checkstyle of goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed.
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (checkstyle)
> on project dropwizard-api: Execution checkstyle of goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> 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:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> checkstyle of goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 20 more
> Caused by: java.lang.NullPointerException
> at java.util.zip.ZipFile.getZipEntry(ZipFile.java:566)
> at java.util.zip.ZipFile.access$900(ZipFile.java:60)
> at java.util.zip.ZipFile$ZipEntryIterator.next(ZipFile.java:524)
> at java.util.zip.ZipFile$ZipEntryIterator.nextElement(ZipFile.java:499)
> at java.util.zip.ZipFile$ZipEntryIterator.nextElement(ZipFile.java:480)
> at java.util.jar.JarFile$JarEntryIterator.next(JarFile.java:257)
> at java.util.jar.JarFile$JarEntryIterator.nextElement(JarFile.java:266)
> at java.util.jar.JarFile$JarEntryIterator.nextElement(JarFile.java:247)
> at
> org.codehaus.plexus.resource.loader.JarHolder.getEntries(JarHolder.java:132)
> at
> org.codehaus.plexus.resource.loader.JarResourceLoader.loadJar(JarResourceLoader.java:100)
> at
> org.codehaus.plexus.resource.loader.JarResourceLoader.initialize(JarResourceLoader.java:63)
> at
> org.codehaus.plexus.resource.loader.JarResourceLoader.
[jira] [Commented] (MCHECKSTYLE-333) Intermittent NPE on checkstyle:check
[
https://issues.apache.org/jira/browse/MCHECKSTYLE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822423#comment-15822423
]
Robert Scholte commented on MCHECKSTYLE-333:
See http://maven.apache.org/plugins/maven-checkstyle-plugin/check-mojo.html,
the goal is bound to the {{verify}} phase by default, which means after the
packaging of the jar. IIRC some checkstyle rules require compiled classes.
Would be good the clarify this exactly.
> Intermittent NPE on checkstyle:check
>
>
> Key: MCHECKSTYLE-333
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-333
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.17
> Environment: OSX El Captain, maven 3.x, checkstyle 6.19
>Reporter: James Short
>
> I generally run checkstyle:check manually but I wanted to integrate it into
> the validate phase of my root build.
> After doing this, it will intermittent fail with an NPE:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (checkstyle) on
> project dropwizard-api: Execution checkstyle of goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed.
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (checkstyle)
> on project dropwizard-api: Execution checkstyle of goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> 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:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> checkstyle of goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 20 more
> Caused by: java.lang.NullPointerException
> at java.util.zip.ZipFile.getZipEntry(ZipFile.java:566)
> at java.util.zip.ZipFile.access$900(ZipFile.java:60)
> at java.util.zip.ZipFile$ZipEntryIterator.next(ZipFile.java:524)
> at java.util.zip.ZipFile$ZipEntryIterator.nextElement(ZipFile.java:499)
> at java.util.zip.ZipFile$ZipEntryIterator.nextElement(ZipFile.java:480)
> at java.util.jar.JarFile$JarEntryIterator.next(JarFile.java:257)
> at java.util.jar.JarFile$JarEntryIterator.nextElement(JarFile.java:266)
> at java.util.jar.JarFile$JarEntryIterator.nextElement(JarFile.java:247)
> at
> org.codehaus.plexus.resource.loader.JarHolder.getEntries(JarHolder.java:132)
> at
> org.codehaus.plexus.resource.loader.JarResourceLoader.loadJar(JarResourceLoader.java:100)
> at
> org.codehaus.plexus.resource.loader.JarResourceLoader.initialize(JarResourceLoader.java:63)
> at
> org.codehaus.plexus.resource.loader.JarResourceLoader.getResource(JarResourceLoader.java:141)
[jira] [Updated] (MCHECKSTYLE-333) Intermittent NPE on checkstyle:check
[
https://issues.apache.org/jira/browse/MCHECKSTYLE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MCHECKSTYLE-333:
---
Environment: OSX El Captain, maven 3.x, checkstyle 6.19 (was: OSX El
Captain, maven 3.x, maven checkstyle plugin 2.7, checkstyle 6.19)
> Intermittent NPE on checkstyle:check
>
>
> Key: MCHECKSTYLE-333
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-333
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.17
> Environment: OSX El Captain, maven 3.x, checkstyle 6.19
>Reporter: James Short
>
> I generally run checkstyle:check manually but I wanted to integrate it into
> the validate phase of my root build.
> After doing this, it will intermittent fail with an NPE:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (checkstyle) on
> project dropwizard-api: Execution checkstyle of goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed.
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (checkstyle)
> on project dropwizard-api: Execution checkstyle of goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> 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:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> checkstyle of goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 20 more
> Caused by: java.lang.NullPointerException
> at java.util.zip.ZipFile.getZipEntry(ZipFile.java:566)
> at java.util.zip.ZipFile.access$900(ZipFile.java:60)
> at java.util.zip.ZipFile$ZipEntryIterator.next(ZipFile.java:524)
> at java.util.zip.ZipFile$ZipEntryIterator.nextElement(ZipFile.java:499)
> at java.util.zip.ZipFile$ZipEntryIterator.nextElement(ZipFile.java:480)
> at java.util.jar.JarFile$JarEntryIterator.next(JarFile.java:257)
> at java.util.jar.JarFile$JarEntryIterator.nextElement(JarFile.java:266)
> at java.util.jar.JarFile$JarEntryIterator.nextElement(JarFile.java:247)
> at
> org.codehaus.plexus.resource.loader.JarHolder.getEntries(JarHolder.java:132)
> at
> org.codehaus.plexus.resource.loader.JarResourceLoader.loadJar(JarResourceLoader.java:100)
> at
> org.codehaus.plexus.resource.loader.JarResourceLoader.initialize(JarResourceLoader.java:63)
> at
> org.codehaus.plexus.resource.loader.JarResourceLoader.getResource(JarResourceLoader.java:141)
> at
> org.apache.maven.plugin.checkstyle.resource.LicenseResourceManager.getResource(LicenseResourceManager.java:75)
> at
> org.codehaus.plexus.resource.DefaultResourceManag
[jira] [Updated] (MCHECKSTYLE-333) Intermittent NPE on checkstyle:check
[
https://issues.apache.org/jira/browse/MCHECKSTYLE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MCHECKSTYLE-333:
---
Affects Version/s: 2.17
> Intermittent NPE on checkstyle:check
>
>
> Key: MCHECKSTYLE-333
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-333
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.17
> Environment: OSX El Captain, maven 3.x, maven checkstyle plugin 2.7,
> checkstyle 6.19
>Reporter: James Short
>
> I generally run checkstyle:check manually but I wanted to integrate it into
> the validate phase of my root build.
> After doing this, it will intermittent fail with an NPE:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (checkstyle) on
> project dropwizard-api: Execution checkstyle of goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed.
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (checkstyle)
> on project dropwizard-api: Execution checkstyle of goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> 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:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> checkstyle of goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 20 more
> Caused by: java.lang.NullPointerException
> at java.util.zip.ZipFile.getZipEntry(ZipFile.java:566)
> at java.util.zip.ZipFile.access$900(ZipFile.java:60)
> at java.util.zip.ZipFile$ZipEntryIterator.next(ZipFile.java:524)
> at java.util.zip.ZipFile$ZipEntryIterator.nextElement(ZipFile.java:499)
> at java.util.zip.ZipFile$ZipEntryIterator.nextElement(ZipFile.java:480)
> at java.util.jar.JarFile$JarEntryIterator.next(JarFile.java:257)
> at java.util.jar.JarFile$JarEntryIterator.nextElement(JarFile.java:266)
> at java.util.jar.JarFile$JarEntryIterator.nextElement(JarFile.java:247)
> at
> org.codehaus.plexus.resource.loader.JarHolder.getEntries(JarHolder.java:132)
> at
> org.codehaus.plexus.resource.loader.JarResourceLoader.loadJar(JarResourceLoader.java:100)
> at
> org.codehaus.plexus.resource.loader.JarResourceLoader.initialize(JarResourceLoader.java:63)
> at
> org.codehaus.plexus.resource.loader.JarResourceLoader.getResource(JarResourceLoader.java:141)
> at
> org.apache.maven.plugin.checkstyle.resource.LicenseResourceManager.getResource(LicenseResourceManager.java:75)
> at
> org.codehaus.plexus.resource.DefaultResourceManager.getResourceAsFile(DefaultResourceManager.java:91)
> at
> org.apache.mav
[jira] [Updated] (SCM-840) mvn scm:tag reveals SCM git password if fatal occured during git push
[
https://issues.apache.org/jira/browse/SCM-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated SCM-840:
---
Description: The same error as in SCM-811 but now for {{scm:tag}} command.
(was: The same error as in https://issues.apache.org/jira/browse/SCM-811 but
now for scm:tag command.)
> mvn scm:tag reveals SCM git password if fatal occured during git push
> -
>
> Key: SCM-840
> URL: https://issues.apache.org/jira/browse/SCM-840
> Project: Maven SCM
> Issue Type: Improvement
> Components: maven-scm-provider-gitexe
>Affects Versions: 1.9.5
>Reporter: Evgeni Gordeev
> Labels: Amazon, Linux
>
> The same error as in SCM-811 but now for {{scm:tag}} command.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SCM-840) mvn scm:tag reveals SCM git password if fatal occured during git push
[
https://issues.apache.org/jira/browse/SCM-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated SCM-840:
---
Component/s: (was: maven-scm-client)
maven-scm-provider-gitexe
> mvn scm:tag reveals SCM git password if fatal occured during git push
> -
>
> Key: SCM-840
> URL: https://issues.apache.org/jira/browse/SCM-840
> Project: Maven SCM
> Issue Type: Improvement
> Components: maven-scm-provider-gitexe
>Affects Versions: 1.9.5
>Reporter: Evgeni Gordeev
> Labels: Amazon, Linux
>
> The same error as in SCM-811 but now for {{scm:tag}} command.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MCHECKSTYLE-333) Intermittent NPE on checkstyle:check
[
https://issues.apache.org/jira/browse/MCHECKSTYLE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822339#comment-15822339
]
James Short commented on MCHECKSTYLE-333:
-
Note that if I manually run
{code}mvn checkstyle:check{code}
from the cli, it never exhbits this behavior.
> Intermittent NPE on checkstyle:check
>
>
> Key: MCHECKSTYLE-333
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-333
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
> Environment: OSX El Captain, maven 3.x, maven checkstyle plugin 2.7,
> checkstyle 6.19
>Reporter: James Short
>
> I generally run checkstyle:check manually but I wanted to integrate it into
> the validate phase of my root build.
> After doing this, it will intermittent fail with an NPE:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (checkstyle) on
> project dropwizard-api: Execution checkstyle of goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed.
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (checkstyle)
> on project dropwizard-api: Execution checkstyle of goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> 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:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> checkstyle of goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 20 more
> Caused by: java.lang.NullPointerException
> at java.util.zip.ZipFile.getZipEntry(ZipFile.java:566)
> at java.util.zip.ZipFile.access$900(ZipFile.java:60)
> at java.util.zip.ZipFile$ZipEntryIterator.next(ZipFile.java:524)
> at java.util.zip.ZipFile$ZipEntryIterator.nextElement(ZipFile.java:499)
> at java.util.zip.ZipFile$ZipEntryIterator.nextElement(ZipFile.java:480)
> at java.util.jar.JarFile$JarEntryIterator.next(JarFile.java:257)
> at java.util.jar.JarFile$JarEntryIterator.nextElement(JarFile.java:266)
> at java.util.jar.JarFile$JarEntryIterator.nextElement(JarFile.java:247)
> at
> org.codehaus.plexus.resource.loader.JarHolder.getEntries(JarHolder.java:132)
> at
> org.codehaus.plexus.resource.loader.JarResourceLoader.loadJar(JarResourceLoader.java:100)
> at
> org.codehaus.plexus.resource.loader.JarResourceLoader.initialize(JarResourceLoader.java:63)
> at
> org.codehaus.plexus.resource.loader.JarResourceLoader.getResource(JarResourceLoader.java:141)
> at
> org.apache.maven.plugin.checkstyle.resource.LicenseResourceManager.getResource(LicenseResourceManager.java:75)
> at
> org.codehaus.plexus.resou
[jira] [Updated] (MCHECKSTYLE-333) Intermittent NPE on checkstyle:check
[
https://issues.apache.org/jira/browse/MCHECKSTYLE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Short updated MCHECKSTYLE-333:
Description:
I generally run checkstyle:check manually but I wanted to integrate it into the
validate phase of my root build.
After doing this, it will intermittent fail with an NPE:
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (checkstyle) on
project dropwizard-api: Execution checkstyle of goal
org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed.
NullPointerException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (checkstyle) on
project dropwizard-api: Execution checkstyle of goal
org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
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:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
checkstyle of goal org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check
failed.
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
... 20 more
Caused by: java.lang.NullPointerException
at java.util.zip.ZipFile.getZipEntry(ZipFile.java:566)
at java.util.zip.ZipFile.access$900(ZipFile.java:60)
at java.util.zip.ZipFile$ZipEntryIterator.next(ZipFile.java:524)
at java.util.zip.ZipFile$ZipEntryIterator.nextElement(ZipFile.java:499)
at java.util.zip.ZipFile$ZipEntryIterator.nextElement(ZipFile.java:480)
at java.util.jar.JarFile$JarEntryIterator.next(JarFile.java:257)
at java.util.jar.JarFile$JarEntryIterator.nextElement(JarFile.java:266)
at java.util.jar.JarFile$JarEntryIterator.nextElement(JarFile.java:247)
at
org.codehaus.plexus.resource.loader.JarHolder.getEntries(JarHolder.java:132)
at
org.codehaus.plexus.resource.loader.JarResourceLoader.loadJar(JarResourceLoader.java:100)
at
org.codehaus.plexus.resource.loader.JarResourceLoader.initialize(JarResourceLoader.java:63)
at
org.codehaus.plexus.resource.loader.JarResourceLoader.getResource(JarResourceLoader.java:141)
at
org.apache.maven.plugin.checkstyle.resource.LicenseResourceManager.getResource(LicenseResourceManager.java:75)
at
org.codehaus.plexus.resource.DefaultResourceManager.getResourceAsFile(DefaultResourceManager.java:91)
at
org.apache.maven.plugin.checkstyle.exec.DefaultCheckstyleExecutor.getOverridingProperties(DefaultCheckstyleExecutor.java:564)
at
org.apache.maven.plugin.checkstyle.exec.DefaultCheckstyleExecutor.getConfiguration(DefaultCheckstyleExecutor.java:379)
at
org.apache.maven.plugin.checkstyle.exec.DefaultCheckstyleExecutor.executeCheckstyle(DefaultCheckstyleExecutor.java:217)
at
org.apache.maven.plugin.checkstyle.CheckstyleViolationCheckMojo.execute(CheckstyleViolationCheckMojo.java:538)
at
org.apache.maven
[jira] [Created] (MCHECKSTYLE-333) Intermittent NPE on checkstyle:check
James Short created MCHECKSTYLE-333:
---
Summary: Intermittent NPE on checkstyle:check
Key: MCHECKSTYLE-333
URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-333
Project: Maven Checkstyle Plugin
Issue Type: Bug
Environment: OSX El Captain, maven 3.x, maven checkstyle plugin 2.7,
checkstyle 6.19
Reporter: James Short
I generally run checkstyle:check manually but I wanted to integrate it into the
validate phase of my root build.
After doing this, it will intermittent fail with an NPE:
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (checkstyle) on
project dropwizard-api: Execution checkstyle of goal
org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed.
NullPointerException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (checkstyle) on
project dropwizard-api: Execution checkstyle of goal
org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check failed.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
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:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
checkstyle of goal org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check
failed.
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
... 20 more
Caused by: java.lang.NullPointerException
at java.util.zip.ZipFile.getZipEntry(ZipFile.java:566)
at java.util.zip.ZipFile.access$900(ZipFile.java:60)
at java.util.zip.ZipFile$ZipEntryIterator.next(ZipFile.java:524)
at java.util.zip.ZipFile$ZipEntryIterator.nextElement(ZipFile.java:499)
at java.util.zip.ZipFile$ZipEntryIterator.nextElement(ZipFile.java:480)
at java.util.jar.JarFile$JarEntryIterator.next(JarFile.java:257)
at java.util.jar.JarFile$JarEntryIterator.nextElement(JarFile.java:266)
at java.util.jar.JarFile$JarEntryIterator.nextElement(JarFile.java:247)
at
org.codehaus.plexus.resource.loader.JarHolder.getEntries(JarHolder.java:132)
at
org.codehaus.plexus.resource.loader.JarResourceLoader.loadJar(JarResourceLoader.java:100)
at
org.codehaus.plexus.resource.loader.JarResourceLoader.initialize(JarResourceLoader.java:63)
at
org.codehaus.plexus.resource.loader.JarResourceLoader.getResource(JarResourceLoader.java:141)
at
org.apache.maven.plugin.checkstyle.resource.LicenseResourceManager.getResource(LicenseResourceManager.java:75)
at
org.codehaus.plexus.resource.DefaultResourceManager.getResourceAsFile(DefaultResourceManager.java:91)
at
org.apache.maven.plugin.checkstyle.exec.DefaultCheckstyleExecutor.getOverridingProperties(DefaultCheckstyleExecutor.java:564)
at
org.apache.maven.plugin.checkstyle.exec.DefaultCheckstyleExecutor.getConfiguration(DefaultCheckstyleExecutor.java:379)
at
org.apache.maven.plugin.checkstyle.exec.De
[jira] [Updated] (SCM-840) mvn scm:tag reveals SCM git password if fatal occured during git push
[ https://issues.apache.org/jira/browse/SCM-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeni Gordeev updated SCM-840: --- Labels: Amazon Linux (was: ) > mvn scm:tag reveals SCM git password if fatal occured during git push > - > > Key: SCM-840 > URL: https://issues.apache.org/jira/browse/SCM-840 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-client >Affects Versions: 1.9.5 >Reporter: Evgeni Gordeev > Labels: Amazon, Linux > > The same error as in https://issues.apache.org/jira/browse/SCM-811 but now > for scm:tag command. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SCM-840) mvn scm:tag reveals SCM git password if fatal occured during git push
Evgeni Gordeev created SCM-840: -- Summary: mvn scm:tag reveals SCM git password if fatal occured during git push Key: SCM-840 URL: https://issues.apache.org/jira/browse/SCM-840 Project: Maven SCM Issue Type: Bug Components: maven-scm-client Affects Versions: 1.9.5 Reporter: Evgeni Gordeev The same error as in https://issues.apache.org/jira/browse/SCM-811 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SCM-840) mvn scm:tag reveals SCM git password if fatal occured during git push
[ https://issues.apache.org/jira/browse/SCM-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeni Gordeev updated SCM-840: --- Issue Type: Improvement (was: Bug) > mvn scm:tag reveals SCM git password if fatal occured during git push > - > > Key: SCM-840 > URL: https://issues.apache.org/jira/browse/SCM-840 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-client >Affects Versions: 1.9.5 >Reporter: Evgeni Gordeev > > The same error as in https://issues.apache.org/jira/browse/SCM-811 but now > for scm:tag command. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SCM-840) mvn scm:tag reveals SCM git password if fatal occured during git push
[ https://issues.apache.org/jira/browse/SCM-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeni Gordeev updated SCM-840: --- Description: The same error as in https://issues.apache.org/jira/browse/SCM-811 but now for scm:tag command. (was: The same error as in https://issues.apache.org/jira/browse/SCM-811) > mvn scm:tag reveals SCM git password if fatal occured during git push > - > > Key: SCM-840 > URL: https://issues.apache.org/jira/browse/SCM-840 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-client >Affects Versions: 1.9.5 >Reporter: Evgeni Gordeev > > The same error as in https://issues.apache.org/jira/browse/SCM-811 but now > for scm:tag command. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MPOM-130) Upgrade maven-jar-plugin to version 3.0.2
[ https://issues.apache.org/jira/browse/MPOM-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822024#comment-15822024 ] Julian Hyde commented on MPOM-130: -- Yes indeed. CALCITE-1574 (out of memory) was caused by this problem, and was fixed by upgrading maven-jar-plugin from 3.0 to 3.0.2, and maven-source-plugin to 3.0.1 (see MSOURCES-94). There might be other maven plugins that use the bad version of plexus. Worth checking. > Upgrade maven-jar-plugin to version 3.0.2 > - > > Key: MPOM-130 > URL: https://issues.apache.org/jira/browse/MPOM-130 > Project: Maven POMs > Issue Type: Improvement >Affects Versions: ASF-19 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: ASF-19 > > > Needed to be updated based on some bug in Maven Jar Plugin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MNG-6157) org.codehaus.plexus.component.repository.exception.ComponentLookupException: java.util.NoSuchElementException
[
https://issues.apache.org/jira/browse/MNG-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MNG-6157.
---
Resolution: Not A Problem
Assignee: Robert Scholte
Root cause it not inside Maven.
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> java.util.NoSuchElementException
> -
>
> Key: MNG-6157
> URL: https://issues.apache.org/jira/browse/MNG-6157
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.3.9
>Reporter: Michael Vorburger
>Assignee: Robert Scholte
>Priority: Critical
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=496944 (and
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=510439) report an issue
> encountered in M2E which shows a
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> java.util.NoSuchElementException as the root caused by, so the underlying
> problem may be here in Maven core?
> May be a concurrency issue - could it be made more multi thread safe?
> {code}org.apache.maven.plugin.PluginExecutionException: Execution
> default-testResources of goal
> org.apache.maven.plugins:maven-resources-plugin:3.0.1:testResources failed:
> Unable to load the mojo 'testResources' (or one of its required components)
> from the plugin 'org.apache.maven.plugins:maven-resources-plugin:3.0.1'
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:153)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:331)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1362)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1360)
> at
> org.eclipse.m2e.core.project.configurator.MojoExecutionBuildParticipant.build(MojoExecutionBuildParticipant.java:52)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:137)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:172)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:1)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1$1.call(MavenBuilder.java:115)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:105)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200)
> at
> org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at
> org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
> at
> org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
> at
> org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:142)
> at
> org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:232)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: org.apache.maven.plugin.PluginContainerException: Unable to load
> the mojo 'testResources' (or one of its required components) from the plugin
> 'org.apache.maven.plugins:maven-resources-plugin:3.0.1'
> at
> org.apache.mav
[jira] [Created] (MNG-6158) Duplicate transitive dependency with provided and runtime scopes
Stanislav Spiridonov created MNG-6158: - Summary: Duplicate transitive dependency with provided and runtime scopes Key: MNG-6158 URL: https://issues.apache.org/jira/browse/MNG-6158 Project: Maven Issue Type: Bug Components: Dependencies Affects Versions: 3.3.9 Reporter: Stanislav Spiridonov I have in project duplicate transitive dependency with *provided* and *runtime* scopes (from different direct dependencies). Now the final scope of such dependency are resolved to *runtime*. I sure that resolved scope should be *compile* because by *provided* scope the dependency MUST be in compile classpath and by *runtime* scope the dependency MUST be in runtime -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-6157) org.codehaus.plexus.component.repository.exception.ComponentLookupException: java.util.NoSuchElementException
[
https://issues.apache.org/jira/browse/MNG-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15821933#comment-15821933
]
Michael Vorburger commented on MNG-6157:
> Can you reproduce it when using Maven from commandline?
Nope, never; only in M2E. FYI:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=496944 just updated with a
possible interesting analysis. Feel free to close of course if you're sure that
this is certainly not a problem in Maven core.
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> java.util.NoSuchElementException
> -
>
> Key: MNG-6157
> URL: https://issues.apache.org/jira/browse/MNG-6157
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.3.9
>Reporter: Michael Vorburger
>Priority: Critical
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=496944 (and
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=510439) report an issue
> encountered in M2E which shows a
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> java.util.NoSuchElementException as the root caused by, so the underlying
> problem may be here in Maven core?
> May be a concurrency issue - could it be made more multi thread safe?
> {code}org.apache.maven.plugin.PluginExecutionException: Execution
> default-testResources of goal
> org.apache.maven.plugins:maven-resources-plugin:3.0.1:testResources failed:
> Unable to load the mojo 'testResources' (or one of its required components)
> from the plugin 'org.apache.maven.plugins:maven-resources-plugin:3.0.1'
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:153)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:331)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1362)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1360)
> at
> org.eclipse.m2e.core.project.configurator.MojoExecutionBuildParticipant.build(MojoExecutionBuildParticipant.java:52)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:137)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:172)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:1)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1$1.call(MavenBuilder.java:115)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:105)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200)
> at
> org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at
> org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
> at
> org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
> at
> org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:142)
> at
> org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:232)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: org.a
[jira] [Commented] (MNG-6157) org.codehaus.plexus.component.repository.exception.ComponentLookupException: java.util.NoSuchElementException
[
https://issues.apache.org/jira/browse/MNG-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15821904#comment-15821904
]
Robert Scholte commented on MNG-6157:
-
Can you reproduce it when using Maven from commandline?
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> java.util.NoSuchElementException
> -
>
> Key: MNG-6157
> URL: https://issues.apache.org/jira/browse/MNG-6157
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.3.9
>Reporter: Michael Vorburger
>Priority: Critical
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=496944 (and
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=510439) report an issue
> encountered in M2E which shows a
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> java.util.NoSuchElementException as the root caused by, so the underlying
> problem may be here in Maven core?
> May be a concurrency issue - could it be made more multi thread safe?
> {code}org.apache.maven.plugin.PluginExecutionException: Execution
> default-testResources of goal
> org.apache.maven.plugins:maven-resources-plugin:3.0.1:testResources failed:
> Unable to load the mojo 'testResources' (or one of its required components)
> from the plugin 'org.apache.maven.plugins:maven-resources-plugin:3.0.1'
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:153)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:331)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1362)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1360)
> at
> org.eclipse.m2e.core.project.configurator.MojoExecutionBuildParticipant.build(MojoExecutionBuildParticipant.java:52)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:137)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:172)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:1)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1$1.call(MavenBuilder.java:115)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:105)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200)
> at
> org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at
> org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
> at
> org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
> at
> org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:142)
> at
> org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:232)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: org.apache.maven.plugin.PluginContainerException: Unable to load
> the mojo 'testResources' (or one of its required components) from the plugin
> 'org.apache.maven.plugins:maven-resources-plugin:3.0.1'
> at
> org.apache.maven.plugin.intern
[jira] [Updated] (MNG-6157) org.codehaus.plexus.component.repository.exception.ComponentLookupException: java.util.NoSuchElementException
[
https://issues.apache.org/jira/browse/MNG-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MNG-6157:
Fix Version/s: (was: 3.5.0)
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> java.util.NoSuchElementException
> -
>
> Key: MNG-6157
> URL: https://issues.apache.org/jira/browse/MNG-6157
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.3.9
>Reporter: Michael Vorburger
>Priority: Critical
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=496944 (and
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=510439) report an issue
> encountered in M2E which shows a
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> java.util.NoSuchElementException as the root caused by, so the underlying
> problem may be here in Maven core?
> May be a concurrency issue - could it be made more multi thread safe?
> {code}org.apache.maven.plugin.PluginExecutionException: Execution
> default-testResources of goal
> org.apache.maven.plugins:maven-resources-plugin:3.0.1:testResources failed:
> Unable to load the mojo 'testResources' (or one of its required components)
> from the plugin 'org.apache.maven.plugins:maven-resources-plugin:3.0.1'
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:153)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:331)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1362)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1360)
> at
> org.eclipse.m2e.core.project.configurator.MojoExecutionBuildParticipant.build(MojoExecutionBuildParticipant.java:52)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:137)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:172)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:1)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1$1.call(MavenBuilder.java:115)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:105)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200)
> at
> org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at
> org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
> at
> org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
> at
> org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:142)
> at
> org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:232)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: org.apache.maven.plugin.PluginContainerException: Unable to load
> the mojo 'testResources' (or one of its required components) from the plugin
> 'org.apache.maven.plugins:maven-resources-plugin:3.0.1'
> at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:
[jira] [Assigned] (MNG-6155) MavenITmng3599useHttpProxyForWebDAVMk2Test needs --legacy-local-repository
[
https://issues.apache.org/jira/browse/MNG-6155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly reassigned MNG-6155:
-
Assignee: Stephen Connolly
> MavenITmng3599useHttpProxyForWebDAVMk2Test needs --legacy-local-repository
> --
>
> Key: MNG-6155
> URL: https://issues.apache.org/jira/browse/MNG-6155
> Project: Maven
> Issue Type: Bug
> Components: Integration Tests
>Affects Versions: 3.3.9, 3.5.0
>Reporter: Stephen Connolly
>Assignee: Stephen Connolly
>
> We found an issue with the integration tests after the great reset once we
> had a Jenkinsfile that was running the integration tests against windows and
> linux on both Java 7 and Java 8.
> Namely the {{MavenITmng3599useHttpProxyForWebDAVTest}} was flakey with
> approximately two of the four runs failing with errors like:
> {code}
> [DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10.0 for
> f:\jenkins\jenkins-slave\workspace\maven-jenkinsfile\master@4\test\it-local-repo
> [INFO] Scanning for projects...
> [DEBUG] Using mirror test-mirror (dav://www.example.com/) for central
> (file:target/null).
> [DEBUG] Verifying availability of
> f:\jenkins\jenkins-slave\workspace\maven-jenkinsfile\master@4\test\it-local-repo\org\apache\maven\wagon\wagon-webdav-jackrabbit\2.0\wagon-webdav-jackrabbit-2.0.pom
> from [test-mirror (dav://www.example.com/, default, releases+snapshots)]
> [DEBUG] java.util.NoSuchElementException
> role: org.apache.maven.wagon.Wagon
> roleHint: dav
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> java.util.NoSuchElementException
> role: org.apache.maven.wagon.Wagon
> roleHint: dav
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:267)
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:255)
> at
> org.eclipse.aether.internal.transport.wagon.PlexusWagonProvider.lookup(PlexusWagonProvider.java:58)
> at
> org.eclipse.aether.transport.wagon.WagonTransporter.lookupWagon(WagonTransporter.java:271)
> at
> org.eclipse.aether.transport.wagon.WagonTransporter.(WagonTransporter.java:115)
> at
> org.eclipse.aether.transport.wagon.WagonTransporterFactory.newInstance(WagonTransporterFactory.java:127)
> at
> org.eclipse.aether.internal.impl.DefaultTransporterProvider.newTransporter(DefaultTransporterProvider.java:110)
> at
> org.eclipse.aether.connector.basic.BasicRepositoryConnector.(BasicRepositoryConnector.java:115)
> at
> org.eclipse.aether.connector.basic.BasicRepositoryConnectorFactory.newInstance(BasicRepositoryConnectorFactory.java:180)
> at
> org.eclipse.aether.internal.impl.DefaultRepositoryConnectorProvider.newRepositoryConnector(DefaultRepositoryConnectorProvider.java:113)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:516)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223)
> at
> org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:267)
> at
> org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:198)
> at
> org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:202)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.collectDependencies(DefaultRepositorySystem.java:316)
> at
> org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolveInternal(DefaultPluginDependenciesResolver.java:202)
> at
> org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:149)
> at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.resolveExtensionArtifacts(DefaultMavenPluginManager.java:908)
> at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.setupExtensionsRealm(DefaultMavenPluginManager.java:839)
> at
> org.apache.maven.project.DefaultProjectBuildingHelper.createProjectRealm(DefaultProjectBuildingHelper.java:196)
> at
> org.apache.maven.project.DefaultModelBuildingListener.buildExtensionsAssembled(DefaultModelBuildingListener.java:99)
> at
> org.apache.maven.model.building.ModelBuildingEventCatapult$1.fire(ModelBuildingEventCatapult.java:44)
> at
> org.apache.maven.model.building.DefaultModelBuilder.fireEvent(DefaultModelBuilder.java:1295)
> at
> org.apache.maven.model.building.DefaultMod
[jira] [Resolved] (MNG-6155) MavenITmng3599useHttpProxyForWebDAVMk2Test needs --legacy-local-repository
[
https://issues.apache.org/jira/browse/MNG-6155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly resolved MNG-6155.
---
Resolution: Fixed
6c86dc6fe8bad24950fa76d295910e7d7e145a21
> MavenITmng3599useHttpProxyForWebDAVMk2Test needs --legacy-local-repository
> --
>
> Key: MNG-6155
> URL: https://issues.apache.org/jira/browse/MNG-6155
> Project: Maven
> Issue Type: Bug
> Components: Integration Tests
>Affects Versions: 3.3.9, 3.5.0
>Reporter: Stephen Connolly
>
> We found an issue with the integration tests after the great reset once we
> had a Jenkinsfile that was running the integration tests against windows and
> linux on both Java 7 and Java 8.
> Namely the {{MavenITmng3599useHttpProxyForWebDAVTest}} was flakey with
> approximately two of the four runs failing with errors like:
> {code}
> [DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10.0 for
> f:\jenkins\jenkins-slave\workspace\maven-jenkinsfile\master@4\test\it-local-repo
> [INFO] Scanning for projects...
> [DEBUG] Using mirror test-mirror (dav://www.example.com/) for central
> (file:target/null).
> [DEBUG] Verifying availability of
> f:\jenkins\jenkins-slave\workspace\maven-jenkinsfile\master@4\test\it-local-repo\org\apache\maven\wagon\wagon-webdav-jackrabbit\2.0\wagon-webdav-jackrabbit-2.0.pom
> from [test-mirror (dav://www.example.com/, default, releases+snapshots)]
> [DEBUG] java.util.NoSuchElementException
> role: org.apache.maven.wagon.Wagon
> roleHint: dav
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> java.util.NoSuchElementException
> role: org.apache.maven.wagon.Wagon
> roleHint: dav
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:267)
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:255)
> at
> org.eclipse.aether.internal.transport.wagon.PlexusWagonProvider.lookup(PlexusWagonProvider.java:58)
> at
> org.eclipse.aether.transport.wagon.WagonTransporter.lookupWagon(WagonTransporter.java:271)
> at
> org.eclipse.aether.transport.wagon.WagonTransporter.(WagonTransporter.java:115)
> at
> org.eclipse.aether.transport.wagon.WagonTransporterFactory.newInstance(WagonTransporterFactory.java:127)
> at
> org.eclipse.aether.internal.impl.DefaultTransporterProvider.newTransporter(DefaultTransporterProvider.java:110)
> at
> org.eclipse.aether.connector.basic.BasicRepositoryConnector.(BasicRepositoryConnector.java:115)
> at
> org.eclipse.aether.connector.basic.BasicRepositoryConnectorFactory.newInstance(BasicRepositoryConnectorFactory.java:180)
> at
> org.eclipse.aether.internal.impl.DefaultRepositoryConnectorProvider.newRepositoryConnector(DefaultRepositoryConnectorProvider.java:113)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:516)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)
> at
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223)
> at
> org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:267)
> at
> org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:198)
> at
> org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:202)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.collectDependencies(DefaultRepositorySystem.java:316)
> at
> org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolveInternal(DefaultPluginDependenciesResolver.java:202)
> at
> org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:149)
> at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.resolveExtensionArtifacts(DefaultMavenPluginManager.java:908)
> at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.setupExtensionsRealm(DefaultMavenPluginManager.java:839)
> at
> org.apache.maven.project.DefaultProjectBuildingHelper.createProjectRealm(DefaultProjectBuildingHelper.java:196)
> at
> org.apache.maven.project.DefaultModelBuildingListener.buildExtensionsAssembled(DefaultModelBuildingListener.java:99)
> at
> org.apache.maven.model.building.ModelBuildingEventCatapult$1.fire(ModelBuildingEventCatapult.java:44)
> at
> org.apache.maven.model.building.DefaultModelBuilder.fireEvent(DefaultModelBuilder.java:1295)
> at
> org.apache.maven.model.building.DefaultModelBuilder.bu
[jira] [Closed] (MJAR-232) The MJP doesn't genereate artifact with 'tests' classifier for 'test-jar' goal
[ https://issues.apache.org/jira/browse/MJAR-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Maysyuk closed MJAR-232. --- Resolution: Not A Problem > The MJP doesn't genereate artifact with 'tests' classifier for 'test-jar' goal > -- > > Key: MJAR-232 > URL: https://issues.apache.org/jira/browse/MJAR-232 > Project: Maven JAR Plugin > Issue Type: Bug >Affects Versions: 3.0.0, 3.0.1, 3.0.2 > Environment: Windows 7 >Reporter: Eugene Maysyuk > Labels: build, test > > The new version of maven-jar-plugin doesn't generate artifact with 'tests' > classifier for 'test-jar' goal. > I have prepared sample project on the github. > https://github.com/EugenMaysyuk/test-jar-classifier > You can build it with different maven-jar-plugin versions (2.6 and 3.0.0) to > see the difference in 'test-jar' goal. > The part of build log when I used the maven-jar-plugin:2.6: > [INFO] --- maven-jar-plugin:*2.6:test-jar* (default) @ sample --- > [WARNING] JAR will be empty - no content was marked for inclusion! > [INFO] Building jar: > D:\test-jar-classifier\target\sample-1.0-SNAPSHOT-*tests*.jar > The part of build log when I used the maven-jar-plugin:3.0.2: > [INFO] --- maven-jar-plugin:*3.0.2:test-jar* (default) @ sample --- > [WARNING] JAR will be empty - no content was marked for inclusion! > [INFO] Building jar: > D:\test-jar-classifier\target\sample-1.0-SNAPSHOT-*classes*.jar -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-6157) org.codehaus.plexus.component.repository.exception.ComponentLookupException: java.util.NoSuchElementException
[
https://issues.apache.org/jira/browse/MNG-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15821843#comment-15821843
]
Michael Vorburger commented on MNG-6157:
Sorry for now having opened multiple bugs, but I'm hitting this almost daily
since half a year, so perhaps this will help get it some attention and
traction..
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> java.util.NoSuchElementException
> -
>
> Key: MNG-6157
> URL: https://issues.apache.org/jira/browse/MNG-6157
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.3.9
>Reporter: Michael Vorburger
>Priority: Critical
> Fix For: 3.5.0
>
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=496944 (and
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=510439) report an issue
> encountered in M2E which shows a
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> java.util.NoSuchElementException as the root caused by, so the underlying
> problem may be here in Maven core?
> May be a concurrency issue - could it be made more multi thread safe?
> {code}org.apache.maven.plugin.PluginExecutionException: Execution
> default-testResources of goal
> org.apache.maven.plugins:maven-resources-plugin:3.0.1:testResources failed:
> Unable to load the mojo 'testResources' (or one of its required components)
> from the plugin 'org.apache.maven.plugins:maven-resources-plugin:3.0.1'
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:153)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:331)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1362)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1360)
> at
> org.eclipse.m2e.core.project.configurator.MojoExecutionBuildParticipant.build(MojoExecutionBuildParticipant.java:52)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:137)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:172)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:1)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1$1.call(MavenBuilder.java:115)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:105)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200)
> at
> org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at
> org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
> at
> org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
> at
> org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:142)
> at
> org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:232)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: org.apache.maven.plugin.PluginContainerException: Unable to load
> the mojo 'testResources' (or one of i
[jira] [Updated] (MNG-6157) org.codehaus.plexus.component.repository.exception.ComponentLookupException: java.util.NoSuchElementException
[
https://issues.apache.org/jira/browse/MNG-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Vorburger updated MNG-6157:
---
Fix Version/s: 3.5.0
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> java.util.NoSuchElementException
> -
>
> Key: MNG-6157
> URL: https://issues.apache.org/jira/browse/MNG-6157
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.3.9
>Reporter: Michael Vorburger
>Priority: Critical
> Fix For: 3.5.0
>
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=496944 (and
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=510439) report an issue
> encountered in M2E which shows a
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> java.util.NoSuchElementException as the root caused by, so the underlying
> problem may be here in Maven core?
> May be a concurrency issue - could it be made more multi thread safe?
> {code}org.apache.maven.plugin.PluginExecutionException: Execution
> default-testResources of goal
> org.apache.maven.plugins:maven-resources-plugin:3.0.1:testResources failed:
> Unable to load the mojo 'testResources' (or one of its required components)
> from the plugin 'org.apache.maven.plugins:maven-resources-plugin:3.0.1'
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:153)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:331)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1362)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1360)
> at
> org.eclipse.m2e.core.project.configurator.MojoExecutionBuildParticipant.build(MojoExecutionBuildParticipant.java:52)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:137)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:172)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:1)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1$1.call(MavenBuilder.java:115)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:105)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200)
> at
> org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at
> org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
> at
> org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
> at
> org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:142)
> at
> org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:232)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: org.apache.maven.plugin.PluginContainerException: Unable to load
> the mojo 'testResources' (or one of its required components) from the plugin
> 'org.apache.maven.plugins:maven-resources-plugin:3.0.1'
> at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(Defau
[jira] [Commented] (MNG-6157) org.codehaus.plexus.component.repository.exception.ComponentLookupException: java.util.NoSuchElementException
[
https://issues.apache.org/jira/browse/MNG-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15821840#comment-15821840
]
Michael Vorburger commented on MNG-6157:
Setting Affects Version to 3.3.9 because that's the one embedded in M2E 1.7.0
(Preferences > Maven > Installations).
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> java.util.NoSuchElementException
> -
>
> Key: MNG-6157
> URL: https://issues.apache.org/jira/browse/MNG-6157
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.3.9
>Reporter: Michael Vorburger
>Priority: Critical
> Fix For: 3.5.0
>
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=496944 (and
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=510439) report an issue
> encountered in M2E which shows a
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> java.util.NoSuchElementException as the root caused by, so the underlying
> problem may be here in Maven core?
> May be a concurrency issue - could it be made more multi thread safe?
> {code}org.apache.maven.plugin.PluginExecutionException: Execution
> default-testResources of goal
> org.apache.maven.plugins:maven-resources-plugin:3.0.1:testResources failed:
> Unable to load the mojo 'testResources' (or one of its required components)
> from the plugin 'org.apache.maven.plugins:maven-resources-plugin:3.0.1'
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:153)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:331)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1362)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1360)
> at
> org.eclipse.m2e.core.project.configurator.MojoExecutionBuildParticipant.build(MojoExecutionBuildParticipant.java:52)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:137)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:172)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:1)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1$1.call(MavenBuilder.java:115)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:105)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200)
> at
> org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at
> org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
> at
> org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
> at
> org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:142)
> at
> org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:232)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: org.apache.maven.plugin.PluginContainerException: Unable to load
> the mojo 'testResources' (or one of its required components) from the plugin
> '
[jira] [Updated] (MNG-6157) org.codehaus.plexus.component.repository.exception.ComponentLookupException: java.util.NoSuchElementException
[
https://issues.apache.org/jira/browse/MNG-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Vorburger updated MNG-6157:
---
Affects Version/s: 3.3.9
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> java.util.NoSuchElementException
> -
>
> Key: MNG-6157
> URL: https://issues.apache.org/jira/browse/MNG-6157
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.3.9
>Reporter: Michael Vorburger
>Priority: Critical
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=496944 (and
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=510439) report an issue
> encountered in M2E which shows a
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> java.util.NoSuchElementException as the root caused by, so the underlying
> problem may be here in Maven core?
> May be a concurrency issue - could it be made more multi thread safe?
> {code}org.apache.maven.plugin.PluginExecutionException: Execution
> default-testResources of goal
> org.apache.maven.plugins:maven-resources-plugin:3.0.1:testResources failed:
> Unable to load the mojo 'testResources' (or one of its required components)
> from the plugin 'org.apache.maven.plugins:maven-resources-plugin:3.0.1'
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:153)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:331)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1362)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at
> org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1360)
> at
> org.eclipse.m2e.core.project.configurator.MojoExecutionBuildParticipant.build(MojoExecutionBuildParticipant.java:52)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:137)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:172)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:1)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1$1.call(MavenBuilder.java:115)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:105)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86)
> at
> org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200)
> at
> org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at
> org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
> at
> org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
> at
> org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:142)
> at
> org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:232)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: org.apache.maven.plugin.PluginContainerException: Unable to load
> the mojo 'testResources' (or one of its required components) from the plugin
> 'org.apache.maven.plugins:maven-resources-plugin:3.0.1'
> at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:5
[jira] [Created] (MNG-6157) org.codehaus.plexus.component.repository.exception.ComponentLookupException: java.util.NoSuchElementException
Michael Vorburger created MNG-6157:
--
Summary:
org.codehaus.plexus.component.repository.exception.ComponentLookupException:
java.util.NoSuchElementException
Key: MNG-6157
URL: https://issues.apache.org/jira/browse/MNG-6157
Project: Maven
Issue Type: Bug
Reporter: Michael Vorburger
Priority: Critical
https://bugs.eclipse.org/bugs/show_bug.cgi?id=496944 (and
https://bugs.eclipse.org/bugs/show_bug.cgi?id=510439) report an issue
encountered in M2E which shows a
org.codehaus.plexus.component.repository.exception.ComponentLookupException:
java.util.NoSuchElementException as the root caused by, so the underlying
problem may be here in Maven core?
May be a concurrency issue - could it be made more multi thread safe?
{code}org.apache.maven.plugin.PluginExecutionException: Execution
default-testResources of goal
org.apache.maven.plugins:maven-resources-plugin:3.0.1:testResources failed:
Unable to load the mojo 'testResources' (or one of its required components)
from the plugin 'org.apache.maven.plugins:maven-resources-plugin:3.0.1'
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:153)
at
org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:331)
at
org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1362)
at
org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
at
org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1360)
at
org.eclipse.m2e.core.project.configurator.MojoExecutionBuildParticipant.build(MojoExecutionBuildParticipant.java:52)
at
org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:137)
at
org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:172)
at
org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:1)
at
org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1$1.call(MavenBuilder.java:115)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
at
org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:105)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
at
org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86)
at
org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200)
at
org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
at
org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
at
org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
at
org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
at
org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:142)
at
org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:232)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
Caused by: org.apache.maven.plugin.PluginContainerException: Unable to load the
mojo 'testResources' (or one of its required components) from the plugin
'org.apache.maven.plugins:maven-resources-plugin:3.0.1'
at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:551)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:121)
... 31 more
Caused by:
org.codehaus.plexus.component.repository.exception.ComponentLookupException:
java.util.NoSuchElementException
role: org.apache.maven.plugin.Mojo
roleHint: org.apache.maven.plugins:maven-resources-plugin:3.0.1:testRe
[jira] [Commented] (MDEP-542) dependency:list do not output maven module project to file
[
https://issues.apache.org/jira/browse/MDEP-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15821687#comment-15821687
]
Robert Scholte commented on MDEP-542:
-
I assume there's a {{x.txt}} in the root of every module showing the list of
that module.
> dependency:list do not output maven module project to file
> --
>
> Key: MDEP-542
> URL: https://issues.apache.org/jira/browse/MDEP-542
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve, tree
>Affects Versions: 2.10
>Reporter: Peter Bäckman
>
> I have a simple maven project with two maven module projects:
> AppendTest
> -ModuleA
> -ModuleB
> Listing dependencies to file will only capture the output from the top maven
> project. Nothing from ModuleA or ModuleB is captured.
> {code}mvn dependency:list -DoutputFile=x.txt -DappendOutput=true{code}
> Content of x.txt:
> {code}The following files have been resolved:
>none
> {code}
> Running without outputFile property lists also the sub modules as expected:
> {code}
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] AppendTest
> [INFO] ModuleA
> [INFO] ModuleB
> [INFO]
> [INFO]
>
> [INFO] Building AppendTest 0.0.1-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-dependency-plugin:2.10:list (default-cli) @ AppendTest ---
> [INFO]
> [INFO] The following files have been resolved:
> [INFO]none
> [INFO]
> [INFO]
> [INFO]
>
> [INFO] Building ModuleA 0.0.1-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-dependency-plugin:2.10:list (default-cli) @ ModuleA ---
> [INFO]
> [INFO] The following files have been resolved:
> [INFO]org.apache.commons:commons-lang3:jar:3.4:compile
> [INFO]
> [INFO]
> [INFO]
>
> [INFO] Building ModuleB 0.0.1-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-dependency-plugin:2.10:list (default-cli) @ ModuleB ---
> [INFO]
> [INFO] The following files have been resolved:
> [INFO]org.slf4j:slf4j-api:jar:1.7.21:compile
> [INFO]
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] AppendTest . SUCCESS [ 1.519
> s]
> [INFO] ModuleA SUCCESS [ 0.043
> s]
> [INFO] ModuleB SUCCESS [ 0.031
> s]
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 1.894 s
> [INFO] Finished at: 2016-11-02T12:13:37+01:00
> [INFO] Final Memory: 12M/153M
> [INFO]
> {code}
> Problem is the same for dependency:tree.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (MCOMPILER-230) failOnError doesn't work when set inside an execution
[
https://issues.apache.org/jira/browse/MCOMPILER-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MCOMPILER-230.
Resolution: Cannot Reproduce
Assignee: Robert Scholte
Maven (core) is responsible for correctly parsing the configuration and I don't
see any issue there (running {{mvn compile -X}} shows the plugin configuration
per execution block, all looks fine).
In the code there is this line: {{failOnError && !compilerResult.isSuccess()}}
It could be that this value wasn't set correctly for some reason. However, that
depends on the implementation of the Plexus Compiler API. Also in this case not
an issue of the maven-compiler-plugin.
> failOnError doesn't work when set inside an execution
> -
>
> Key: MCOMPILER-230
> URL: https://issues.apache.org/jira/browse/MCOMPILER-230
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 3.1
> Environment: Linux Mint 17 Cinnamon
>Reporter: Jonathan Ogilvie
>Assignee: Robert Scholte
>
> I have the following plugin configuration in my pom:
> {code:xml}
>
> org.apache.maven.plugins
> maven-compiler-plugin
> ${maven-compiler-plugin.version}
>
>
> annotation-processing
> generate-sources
>
> compile
>
>
> only
> false
>
>
>
> compile-without-generated-source
> compile
>
> compile
>
>
>
> ${project.build.dir}/generated-sources/**
> none
>
>
>
>
> ${java.version}
> ${java.version}
> only
>
>
> {code}
> During the first execution, the build still fails on error. If I move
> to the top-level node or define it on
> the command line instead, the value sticks, but then I can't enable
> failOnError for the second execution.
> Of note: it seems like this works if I negate the whole thing and switch the
> place I'm overriding. If I set it false at the top level configuration, and
> true on an execution, I can get the desired behavior.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (MCOMPILER-233) Default build mode doesn't recompile all dependencies, causing NoSuchMethodError/NoSuchFieldError at runtime
[
https://issues.apache.org/jira/browse/MCOMPILER-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MCOMPILER-233.
Resolution: Incomplete
Assignee: Robert Scholte
> Default build mode doesn't recompile all dependencies, causing
> NoSuchMethodError/NoSuchFieldError at runtime
>
>
> Key: MCOMPILER-233
> URL: https://issues.apache.org/jira/browse/MCOMPILER-233
> Project: Maven Compiler Plugin
> Issue Type: Bug
>Affects Versions: 2.0.2, 3.0
> Environment: Linux amd64
>Reporter: Török Edwin
>Assignee: Robert Scholte
> Attachments: build.log
>
>
> I build a project with 'mvn package', change the type of a field/method in
> one source file, run 'mvn package' again and it only rebuilds the changed
> file, and not the other classes that depend on it.
> This can cause NoSuchMethodError/NoSuchFieldError when/if the code is reached
> at runtime. (at least Java 1.7 didn't detect this at class load time).
> Due to MCOMPILER-209 it is not entirely obvious how to turn off these partial
> builds, for example if I put
> {{true}} in my pom.xml
> then both source files are recompiled and the program works correclty so I
> would think that incremental compilation is NOT used in that case? Confusing.
> It appears that the only reliable way to build a project is to run 'mvn clean
> package' instead of just 'mvn package'.
> Maven should probably print a warning when using the partial builds, and the
> documentation should be updated to warn of these inconsistencies.
> Or perhaps you could run a final checking step after all files are compiled
> that checks whether the .class files are all still consistent (like a linker
> step).
> Self-contained testcase:
> {noformat}
> #!/bin/sh
> set -e
> {noformat}
> \# Setup initial project
> {{mvn archetype:generate -DgroupId=com.example.bug -DartifactId=build-bug
> -DarchetypeArtifactId=maven-archetype-quickstart -DinteractiveMode=false}}
> {{cd build-bug}}
> {code:title=src/main/java/com/example/bug/App.java}
> package com.example.bug;
> public class App
> {
> public static void main( String[] args )
> {
> System.out.println( new Other().foo() );
> }
> }
> {code}
> {code:title=src/main/java/com/example/bug/Other.java }
> package com.example.bug;
> public class Other {
> Integer foo() { return new Integer(42); }
> }
> {code}
> {{mvn package java -cp target/build-bug-1.0-SNAPSHOT.jar com.example.bug.App}}
> \# Make a change
> sed -i -e 's/Integer/Long/g' src/main/java/com/example/bug/Other.java
> \# Watch how incremental compilation breaks everything
> {{mvn -X package >build.log}}
> {{java -cp target/build-bug-1.0-SNAPSHOT.jar com.example.bug.App}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (MCOMPILER-287) Adjust documentation module-info
[ https://issues.apache.org/jira/browse/MCOMPILER-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MCOMPILER-287. Resolution: Fixed Fixed in [r1778530|http://svn.apache.org/viewvc?rev=1778530&view=rev] > Adjust documentation module-info > > > Key: MCOMPILER-287 > URL: https://issues.apache.org/jira/browse/MCOMPILER-287 > Project: Maven Compiler Plugin > Issue Type: Bug >Affects Versions: 3.6.0 >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Minor > Fix For: 3.6.1 > > > The examples of the [module-info > documentation|http://maven.apache.org/plugins/maven-compiler-plugin/examples/module-info.html] > doesn't work in combination with test compilation because it is picking up > the wrong default. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MCOMPILER-287) Adjust documentation module-info
Robert Scholte created MCOMPILER-287: Summary: Adjust documentation module-info Key: MCOMPILER-287 URL: https://issues.apache.org/jira/browse/MCOMPILER-287 Project: Maven Compiler Plugin Issue Type: Bug Affects Versions: 3.6.0 Reporter: Robert Scholte Assignee: Robert Scholte Priority: Minor Fix For: 3.6.1 The examples of the [module-info documentation|http://maven.apache.org/plugins/maven-compiler-plugin/examples/module-info.html] doesn't work in combination with test compilation because it is picking up the wrong default. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MNG-6156) Resolving dependencies is not thread-safe
Roland Illig created MNG-6156:
-
Summary: Resolving dependencies is not thread-safe
Key: MNG-6156
URL: https://issues.apache.org/jira/browse/MNG-6156
Project: Maven
Issue Type: Bug
Components: Artifacts and Repositories
Affects Versions: 3.3.9
Reporter: Roland Illig
Attachments: dependency-list.txt, wagon-not-threadsafe.zip
When building a multi-module project in parallel, Maven updates the local Maven
repository without taking into account that other threads or processes might do
the same at the same time.
To reproduce:
1. unpack the attached project
2. {{mvn dependency:list -U -B -T100}}
See the attached {{dependency-list.txt}} for an example output.
First thing to notice is that the dependency is downloaded 100 times. This is
unexpected, since the Reactor should coordinate all the modules.
Second thing to notice is that the build fails, since a dependency "cannot be
found". This is wrong, since the dependency _can_ be found, it's just not
processed properly.
I suspect the {{legacy.DefaultWagonManager}} to be the cause of this, since the
typical error messages are:
* {{"Downloaded file does not exist: "}}
* {{"Error copying temporary file to the final destination: "}}
* {{"*** CHECKSUM FAILED - RETRYING"}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
