[jira] (MSHARED-410) Verifier mishandles systemProperties
Igor Fedorenko created MSHARED-410: -- Summary: Verifier mishandles systemProperties Key: MSHARED-410 URL: https://jira.codehaus.org/browse/MSHARED-410 Project: Maven Shared Components Issue Type: Bug Components: maven-verifier Reporter: Igor Fedorenko Verifier#setSystemProperties are not passed as system properties but as maven regular -D command line arguments. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSHARED-410) Verifier mishandles systemProperties
[ https://jira.codehaus.org/browse/MSHARED-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Fedorenko closed MSHARED-410. -- Resolution: Fixed Fix Version/s: maven-verifier-1.6 Assignee: Igor Fedorenko http://svn.apache.org/viewvc?view=revisionrevision=1662485 Verifier mishandles systemProperties Key: MSHARED-410 URL: https://jira.codehaus.org/browse/MSHARED-410 Project: Maven Shared Components Issue Type: Bug Components: maven-verifier Reporter: Igor Fedorenko Assignee: Igor Fedorenko Fix For: maven-verifier-1.6 Verifier#setSystemProperties are not passed as system properties but as maven regular -D command line arguments. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-288) NullPointerException during building a multi-module project
[ https://jira.codehaus.org/browse/MCHECKSTYLE-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=364151#comment-364151 ] Kristian Rosenvold commented on MCHECKSTYLE-288: Please add the stacktrace of the NPE here. Run with mvn -e if necessary NullPointerException during building a multi-module project --- Key: MCHECKSTYLE-288 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-288 Project: Maven Checkstyle Plugin Issue Type: Bug Affects Versions: 2.13, 2.14 Environment: Apache Maven 3.2.5 Reporter: Peter Jeszenszky Attachments: geocoder-parent.zip A NullPointerException is thrown during the execution of mvn site in a multi-module project, that is clearly caused by the Maven Checkstyle Plugin. The problem occurs when version 2.13 or 2.14 of the plugin is used, everything works fine when the plugin version is downgraded to version 2.12. I have attached a project in which the problem occurs. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-288) NullPointerException during building a multi-module project
[ https://jira.codehaus.org/browse/MCHECKSTYLE-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=364152#comment-364152 ] Peter Jeszenszky commented on MCHECKSTYLE-288: -- Stack trace: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on project geocoder-parent: Execution default-site of goal org.apache.maven.plugins:maven-site-plugin:3.4:site failed. NullPointerException - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on project geocoder-parent: Execution default-site of goal org.apache.maven.plugins:maven-site-plugin:3.4:site failed. at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224) 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:120) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216) at org.apache.maven.cli.MavenCli.main(MavenCli.java:160) 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:483) 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 default-site of goal org.apache.maven.plugins:maven-site-plugin:3.4:site failed. at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:143) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) ... 19 more Caused by: java.lang.NullPointerException at org.codehaus.plexus.resource.loader.JarHolder.getEntries(JarHolder.java:126) 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:527) at org.apache.maven.plugin.checkstyle.exec.DefaultCheckstyleExecutor.getConfiguration(DefaultCheckstyleExecutor.java:355) at org.apache.maven.plugin.checkstyle.exec.DefaultCheckstyleExecutor.executeCheckstyle(DefaultCheckstyleExecutor.java:218) at org.apache.maven.plugin.checkstyle.AbstractCheckstyleReport.executeReport(AbstractCheckstyleReport.java:474) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:255) at org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:224) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:311) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:129) at org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:182) at org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:141) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132) ... 20 more NullPointerException during building a multi-module project
[jira] (MNG-5775) Provide extension point for alternate implementations to construct build graph
Jason van Zyl created MNG-5775: -- Summary: Provide extension point for alternate implementations to construct build graph Key: MNG-5775 URL: https://jira.codehaus.org/browse/MNG-5775 Project: Maven Issue Type: Bug Reporter: Jason van Zyl -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-288) NullPointerException during building a multi-module project
[ https://jira.codehaus.org/browse/MCHECKSTYLE-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=364186#comment-364186 ] Robert Scholte commented on MCHECKSTYLE-288: Duplicate of MCHECKSTYLE-250? NullPointerException during building a multi-module project --- Key: MCHECKSTYLE-288 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-288 Project: Maven Checkstyle Plugin Issue Type: Bug Affects Versions: 2.13, 2.14 Environment: Apache Maven 3.2.5 Reporter: Peter Jeszenszky Attachments: geocoder-parent.zip A NullPointerException is thrown during the execution of mvn site in a multi-module project, that is clearly caused by the Maven Checkstyle Plugin. The problem occurs when version 2.13 or 2.14 of the plugin is used, everything works fine when the plugin version is downgraded to version 2.12. I have attached a project in which the problem occurs. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-288) NullPointerException during building a multi-module project
Peter Jeszenszky created MCHECKSTYLE-288: Summary: NullPointerException during building a multi-module project Key: MCHECKSTYLE-288 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-288 Project: Maven Checkstyle Plugin Issue Type: Bug Affects Versions: 2.14, 2.13 Environment: Apache Maven 3.2.5 Reporter: Peter Jeszenszky Attachments: geocoder-parent.zip A NullPointerException is thrown during the execution of mvn site in a multi-module project, that is clearly caused by the Maven Checkstyle Plugin. The problem occurs when version 2.13 or 2.14 of the plugin is used, everything works fine when the plugin version is downgraded to version 2.12. I have attached a project in which the problem occurs. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] [Commented] (MPOM-47) Source release assembly can't do tar.gz only
[ https://issues.apache.org/jira/browse/MPOM-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14339363#comment-14339363 ] Christopher Tubbs commented on MPOM-47: --- Saw you got this done. Thanks! Source release assembly can't do tar.gz only Key: MPOM-47 URL: https://issues.apache.org/jira/browse/MPOM-47 Project: Maven POMs Issue Type: Improvement Components: asf Reporter: Christopher Tubbs Fix For: ASF-17 The source-release-assembly execution of the maven-assembly-plugin doesn't offer any way to specify to build a tarball (tar.gz) only. By default, it builds a zip file. One can override the plugin execution to force it to build both a zip and a tarball, by setting sourceReleaseAssemblyDescriptor to source-release-zip-tar. However, there's no way to get it to build only the tarball, unless you do convoluted things like in [this example|http://search.maven.org/remotecontent?filepath=org/apache/accumulo/accumulo-project/1.5.0/accumulo-project-1.5.0.pom], or if you override the apache-release profile entirely. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] (MDEP-480) There should be an option to prevent files overwrite for unpack-dependencies and unpack
Duong Nguyen created MDEP-480: - Summary: There should be an option to prevent files overwrite for unpack-dependencies and unpack Key: MDEP-480 URL: https://jira.codehaus.org/browse/MDEP-480 Project: Maven Dependency Plugin Issue Type: Improvement Reporter: Duong Nguyen There should be a options to prevent file overwrite when extracting files. This option is very helpful when unpack or unpack-dependencies happens after process-resouce phase. Currently, there is overwriteRelease, overwriteSnapshot, overwriteIfNewer. But they all work on the artifact scope (that means decide if a whole artifact should overwrite), not files scope (files should be overwrite an existing file). -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-480) There should be an option to prevent files overwrite for unpack-dependencies and unpack
[ https://jira.codehaus.org/browse/MDEP-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duong Nguyen updated MDEP-480: -- Description: There should be an option to prevent file overwrite when extracting files. This option is very helpful when unpack or unpack-dependencies happens after process-resouce phase. Currently, there is overwriteRelease, overwriteSnapshot, overwriteIfNewer. But they all work on the artifact scope (that means decide if a whole artifact should overwrite), not files scope (files should be overwrite an existing file). was: There should be a options to prevent file overwrite when extracting files. This option is very helpful when unpack or unpack-dependencies happens after process-resouce phase. Currently, there is overwriteRelease, overwriteSnapshot, overwriteIfNewer. But they all work on the artifact scope (that means decide if a whole artifact should overwrite), not files scope (files should be overwrite an existing file). There should be an option to prevent files overwrite for unpack-dependencies and unpack --- Key: MDEP-480 URL: https://jira.codehaus.org/browse/MDEP-480 Project: Maven Dependency Plugin Issue Type: Improvement Reporter: Duong Nguyen Attachments: patch-maven-dependency-2.9-overwriteFiles.patch There should be an option to prevent file overwrite when extracting files. This option is very helpful when unpack or unpack-dependencies happens after process-resouce phase. Currently, there is overwriteRelease, overwriteSnapshot, overwriteIfNewer. But they all work on the artifact scope (that means decide if a whole artifact should overwrite), not files scope (files should be overwrite an existing file). -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-480) There should be an option to prevent files overwrite for unpack-dependencies and unpack
[ https://jira.codehaus.org/browse/MDEP-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duong Nguyen updated MDEP-480: -- Attachment: patch-maven-dependency-2.9-overwriteFiles.patch There should be an option to prevent files overwrite for unpack-dependencies and unpack --- Key: MDEP-480 URL: https://jira.codehaus.org/browse/MDEP-480 Project: Maven Dependency Plugin Issue Type: Improvement Reporter: Duong Nguyen Attachments: patch-maven-dependency-2.9-overwriteFiles.patch There should be a options to prevent file overwrite when extracting files. This option is very helpful when unpack or unpack-dependencies happens after process-resouce phase. Currently, there is overwriteRelease, overwriteSnapshot, overwriteIfNewer. But they all work on the artifact scope (that means decide if a whole artifact should overwrite), not files scope (files should be overwrite an existing file). -- This message was sent by Atlassian JIRA (v6.1.6#6162)
