[jira] (MSHADE-147) Failure to shade without explanation when signature is invalid
[
https://jira.codehaus.org/browse/MSHADE-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neeme Praks updated MSHADE-147:
---
Attachment: patch.txt
Attached a patch to:
* print a nice error message when there is an error while reading JAR file
contents (includes JAR entry path and JAR file path)
* add a "disableJarFileVerification" configuration option for DefaultShader --
when enabled, dependency JAR file verification is turned off
> Failure to shade without explanation when signature is invalid
> --
>
> Key: MSHADE-147
> URL: https://jira.codehaus.org/browse/MSHADE-147
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 2.0
> Environment: JDK 7u21, Linux, Maven 3.0.5
>Reporter: Jesse Glick
>Priority: Minor
> Attachments: patch.txt, stuff.zip
>
>
> If there is a signature error in a shaded dependency, you can get a build
> error like this:
> {code:none}
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-shade-plugin:2.0:shade (shade) on project
> stuff: Error creating shaded jar: Invalid signature file digest for Manifest
> main attributes
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
> 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:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at
> org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
> at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
> at hudson.maven.Maven3Builder.call(Maven3Builder.java:100)
> at hudson.maven.Maven3Builder.call(Maven3Builder.java:66)
> at hudson.remoting.UserRequest.perform(UserRequest.java:118)
> at hudson.remoting.UserRequest.perform(UserRequest.java:48)
> at hudson.remoting.Request$2.run(Request.java:326)
> at
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:722)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: Invalid signature file digest for Manifest main attributes
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:551)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 27 more
> Caused by: java.lang.SecurityException: Invalid signature file digest for
> Manifest main attributes
> at
> sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:240)
> at
> sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:193)
> at java.util.jar.JarVerifier.processEntry(JarVerifier.java:305)
> at java.util.jar.JarVerifier.update(JarVerifier.java:216)
> at java.util.jar.JarFile.initializeVerifier(JarFile.java:345)
> at java.util.jar.JarFile.getInputStream(JarFile.java:412)
> at
> org.apache.maven.plugins.shade.DefaultShader.shade(DefaultShader.java:134)
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:484)
> ... 29 more
> {code}
> Apparently {{De
[jira] (MSHADE-147) Failure to shade without explanation when signature is invalid
[
https://jira.codehaus.org/browse/MSHADE-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=347269#comment-347269
]
Neeme Praks edited comment on MSHADE-147 at 5/29/14 2:38 AM:
-
Attached a patch to:
* print a nice error message when there is an error while reading JAR file
contents (includes JAR entry path and JAR file path)
* add a "disableJarFileVerification" configuration option for DefaultShader --
when enabled, dependency JAR file verification is turned off
The base version for the patch is 2.3.
was (Author: nemecec):
Attached a patch to:
* print a nice error message when there is an error while reading JAR file
contents (includes JAR entry path and JAR file path)
* add a "disableJarFileVerification" configuration option for DefaultShader --
when enabled, dependency JAR file verification is turned off
The base version for the patch is 2.3.
> Failure to shade without explanation when signature is invalid
> --
>
> Key: MSHADE-147
> URL: https://jira.codehaus.org/browse/MSHADE-147
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 2.0
> Environment: JDK 7u21, Linux, Maven 3.0.5
>Reporter: Jesse Glick
>Priority: Minor
> Attachments: patch.txt, stuff.zip
>
>
> If there is a signature error in a shaded dependency, you can get a build
> error like this:
> {code:none}
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-shade-plugin:2.0:shade (shade) on project
> stuff: Error creating shaded jar: Invalid signature file digest for Manifest
> main attributes
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
> 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:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at
> org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
> at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
> at hudson.maven.Maven3Builder.call(Maven3Builder.java:100)
> at hudson.maven.Maven3Builder.call(Maven3Builder.java:66)
> at hudson.remoting.UserRequest.perform(UserRequest.java:118)
> at hudson.remoting.UserRequest.perform(UserRequest.java:48)
> at hudson.remoting.Request$2.run(Request.java:326)
> at
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:722)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: Invalid signature file digest for Manifest main attributes
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:551)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 27 more
> Caused by: java.lang.SecurityException: Invalid signature file digest for
> Manifest main attributes
> at
> sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:240)
> at
> sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:193)
> at java.util.jar.Ja
[jira] (MSHADE-147) Failure to shade without explanation when signature is invalid
[
https://jira.codehaus.org/browse/MSHADE-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=347269#comment-347269
]
Neeme Praks edited comment on MSHADE-147 at 5/29/14 2:38 AM:
-
Attached a patch to:
* print a nice error message when there is an error while reading JAR file
contents (includes JAR entry path and JAR file path)
* add a "disableJarFileVerification" configuration option for DefaultShader --
when enabled, dependency JAR file verification is turned off
The base version for the patch is 2.3.
was (Author: nemecec):
Attached a patch to:
* print a nice error message when there is an error while reading JAR file
contents (includes JAR entry path and JAR file path)
* add a "disableJarFileVerification" configuration option for DefaultShader --
when enabled, dependency JAR file verification is turned off
> Failure to shade without explanation when signature is invalid
> --
>
> Key: MSHADE-147
> URL: https://jira.codehaus.org/browse/MSHADE-147
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 2.0
> Environment: JDK 7u21, Linux, Maven 3.0.5
>Reporter: Jesse Glick
>Priority: Minor
> Attachments: patch.txt, stuff.zip
>
>
> If there is a signature error in a shaded dependency, you can get a build
> error like this:
> {code:none}
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-shade-plugin:2.0:shade (shade) on project
> stuff: Error creating shaded jar: Invalid signature file digest for Manifest
> main attributes
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
> 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:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at
> org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
> at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
> at hudson.maven.Maven3Builder.call(Maven3Builder.java:100)
> at hudson.maven.Maven3Builder.call(Maven3Builder.java:66)
> at hudson.remoting.UserRequest.perform(UserRequest.java:118)
> at hudson.remoting.UserRequest.perform(UserRequest.java:48)
> at hudson.remoting.Request$2.run(Request.java:326)
> at
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:722)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: Invalid signature file digest for Manifest main attributes
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:551)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 27 more
> Caused by: java.lang.SecurityException: Invalid signature file digest for
> Manifest main attributes
> at
> sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:240)
> at
> sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:193)
> at java.util.jar.JarVerifier.processEntry(JarVerifier.java:
[jira] (MSITE-712) maven-site-plugin generates incorrect git -tag command
[
https://jira.codehaus.org/browse/MSITE-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MSITE-712.
---
Resolution: Incomplete
I don't understand what you are doing that is making m-site-p doing a git
command, you don't give use any command executed, any log
please reopen with more information
> maven-site-plugin generates incorrect git -tag command
> --
>
> Key: MSITE-712
> URL: https://jira.codehaus.org/browse/MSITE-712
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: multi module
>Affects Versions: 3.3
> Environment: maven 3.0.2
> jdk 1.7
>Reporter: Martin Gainty
>Priority: Trivial
>
> /*commit pom.xml */
> Executing: /bin/sh -c cd "/opt/jenkins-home/jobs/Section
> 4362/workspace/section4362-parent" && git commit --verbose -F
> /tmp/maven-scm-217365030.commit '/opt/jenkins-home/jobs/Section
> 4362/workspace/section4362-services/pom.xml' '/opt/jenkins-home/jobs/Section
> 4362/workspace/section4362-webapp/pom.xml' '/opt/jenkins-home/jobs/Section
> 4362/workspace/section4362-static/pom.xml' pom.xml
> /*commit to HEAD */
> > [INFO] Working directory: /opt/jenkins-home/jobs/Section
> > 4362/workspace/section4362-parent
> > [INFO] Executing: /bin/sh -c cd "/opt/jenkins-home/jobs/Section
> > 4362/workspace/section4362-parent" && git symbolic-ref HEAD
> > [INFO] Working directory: /opt/jenkins-home/jobs/Section
> > 4362/workspace/section4362-parent
> > [INFO] Executing: /bin/sh -c cd "/opt/jenkins-home/jobs/Section
> > 4362/workspace/section4362-parent" && git push
> > ssh://g...@github.com/{org}/Section4362.git
> > maven-release-test:maven-release-test
> > [INFO] Working directory: /opt/jenkins-home/jobs/Section
> > 4362/workspace/section4362-parent
> > [INFO] Tagging release with the label section4362-parent-0.3...
> > [INFO] Executing: /bin/sh -c cd "/opt/jenkins-home/jobs/Section
> > 4362/workspace" && git tag -F /tmp/maven-scm-882610155.commit
> > section4362-parent-0.3
> /*-a, -s, and -u are absent, -a is implied. so -a should have been
> supplied but was not so we'll bypass this for now */
> /*
> The name of the tag to create, delete, or describe. The new tag name must
> pass ALL checks defined by git-check-ref-format(1). Some of these checks may
> restrict the characters allowed in a tag name.
> */
> since tagname is missing
> the generated git tag command doesnt know the name of what to commit to in
> refs/tags/
> (refs/tags/$tagname is used unless -d/-l/-v is given to delete, list or
> verify tags.)
> temp workaround is to commit everything at command line to git
> then use maven-site-plugin
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MSITE-713) improve "Error during page generation" error message
Herve Boutemy created MSITE-713:
---
Summary: improve "Error during page generation" error message
Key: MSITE-713
URL: https://jira.codehaus.org/browse/MSITE-713
Project: Maven Site Plugin
Issue Type: Improvement
Affects Versions: 3.3
Reporter: Herve Boutemy
the actual error message doesn't tell which report plugin caused a failure:
{noformat}[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 3.649s
[INFO] Finished at: Thu May 29 15:48:19 CEST 2014
[INFO] Final Memory: 20M/491M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.4-SNAPSHOT:site (default-site) on
project failure-it: Error during page generation: Error rendering Maven report:
Cannot run changelog command : Can't load the scm provider. SCM Connection is
not set. -> [Help 1]{noformat}
then people report m-site-p failed, which is wrong, and we need to guess from
error message which report plugin failed
this should be enhanced with information on the report which failed
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCOMPILER-66) Compiler swallows messages from annotation processors
[ https://jira.codehaus.org/browse/MCOMPILER-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MCOMPILER-66. --- Resolution: Fixed Assignee: Robert Scholte > Compiler swallows messages from annotation processors > - > > Key: MCOMPILER-66 > URL: https://jira.codehaus.org/browse/MCOMPILER-66 > Project: Maven Compiler Plugin > Issue Type: Bug >Affects Versions: 2.0.2, 2.1 >Reporter: Evan Cowden >Assignee: Robert Scholte > Attachments: AnnotationProcessorMessagerBug.zip > > > When using the annotation processor API to print messages through the > javax.annotation.processing.Messager object, only messagesspecified by levels > javax.tools.Diagnostic.Kind.ERROR and > javax.tools.Diagnostic.Kind.MANDATORY_WARNING are displayed (and cause the > build to fail). All other messages are swallowed. > Note that while the attached JUnit test case is necessary to help expose the > problem, passing it will not imply that the bug is fixed. The only way to > confirm the fix (that I know of) is to examine console output. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCOMPILER-66) Compiler swallows messages from annotation processors
[ https://jira.codehaus.org/browse/MCOMPILER-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reopened MCOMPILER-66: - > Compiler swallows messages from annotation processors > - > > Key: MCOMPILER-66 > URL: https://jira.codehaus.org/browse/MCOMPILER-66 > Project: Maven Compiler Plugin > Issue Type: Bug >Affects Versions: 2.0.2, 2.1 >Reporter: Evan Cowden >Assignee: Robert Scholte > Attachments: AnnotationProcessorMessagerBug.zip > > > When using the annotation processor API to print messages through the > javax.annotation.processing.Messager object, only messagesspecified by levels > javax.tools.Diagnostic.Kind.ERROR and > javax.tools.Diagnostic.Kind.MANDATORY_WARNING are displayed (and cause the > build to fail). All other messages are swallowed. > Note that while the attached JUnit test case is necessary to help expose the > problem, passing it will not imply that the bug is fixed. The only way to > confirm the fix (that I know of) is to examine console output. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCOMPILER-66) Compiler swallows messages from annotation processors
[ https://jira.codehaus.org/browse/MCOMPILER-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MCOMPILER-66. --- Resolution: Duplicate > Compiler swallows messages from annotation processors > - > > Key: MCOMPILER-66 > URL: https://jira.codehaus.org/browse/MCOMPILER-66 > Project: Maven Compiler Plugin > Issue Type: Bug >Affects Versions: 2.0.2, 2.1 >Reporter: Evan Cowden >Assignee: Robert Scholte > Attachments: AnnotationProcessorMessagerBug.zip > > > When using the annotation processor API to print messages through the > javax.annotation.processing.Messager object, only messagesspecified by levels > javax.tools.Diagnostic.Kind.ERROR and > javax.tools.Diagnostic.Kind.MANDATORY_WARNING are displayed (and cause the > build to fail). All other messages are swallowed. > Note that while the attached JUnit test case is necessary to help expose the > problem, passing it will not imply that the bug is fixed. The only way to > confirm the fix (that I know of) is to examine console output. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSITE-713) improve "Error during page generation" error message
[
https://jira.codehaus.org/browse/MSITE-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=347291#comment-347291
]
Herve Boutemy commented on MSITE-713:
-
failure IT added to reproduce failing site generation easily
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-site-plugin/src/it/failure/
> improve "Error during page generation" error message
>
>
> Key: MSITE-713
> URL: https://jira.codehaus.org/browse/MSITE-713
> Project: Maven Site Plugin
> Issue Type: Improvement
>Affects Versions: 3.3
>Reporter: Herve Boutemy
>
> the actual error message doesn't tell which report plugin caused a failure:
> {noformat}[INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 3.649s
> [INFO] Finished at: Thu May 29 15:48:19 CEST 2014
> [INFO] Final Memory: 20M/491M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.4-SNAPSHOT:site (default-site)
> on project failure-it: Error during page generation: Error rendering Maven
> report: Cannot run changelog command : Can't load the scm provider. SCM
> Connection is not set. -> [Help 1]{noformat}
> then people report m-site-p failed, which is wrong, and we need to guess from
> error message which report plugin failed
> this should be enhanced with information on the report which failed
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MSITE-713) improve "Error during page generation" error message
[
https://jira.codehaus.org/browse/MSITE-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=347292#comment-347292
]
Herve Boutemy commented on MSITE-713:
-
done in [r1598319|http://svn.apache.org/r1598319]
> improve "Error during page generation" error message
>
>
> Key: MSITE-713
> URL: https://jira.codehaus.org/browse/MSITE-713
> Project: Maven Site Plugin
> Issue Type: Improvement
>Affects Versions: 3.3
>Reporter: Herve Boutemy
> Fix For: 3.4
>
>
> the actual error message doesn't tell which report plugin caused a failure:
> {noformat}[INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 3.649s
> [INFO] Finished at: Thu May 29 15:48:19 CEST 2014
> [INFO] Final Memory: 20M/491M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.4-SNAPSHOT:site (default-site)
> on project failure-it: Error during page generation: Error rendering Maven
> report: Cannot run changelog command : Can't load the scm provider. SCM
> Connection is not set. -> [Help 1]{noformat}
> then people report m-site-p failed, which is wrong, and we need to guess from
> error message which report plugin failed
> this should be enhanced with information on the report which failed
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MSITE-713) improve "Error during page generation" error message
[
https://jira.codehaus.org/browse/MSITE-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MSITE-713.
---
Resolution: Fixed
Fix Version/s: 3.4
Assignee: Herve Boutemy
> improve "Error during page generation" error message
>
>
> Key: MSITE-713
> URL: https://jira.codehaus.org/browse/MSITE-713
> Project: Maven Site Plugin
> Issue Type: Improvement
>Affects Versions: 3.3
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
> Fix For: 3.4
>
>
> the actual error message doesn't tell which report plugin caused a failure:
> {noformat}[INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 3.649s
> [INFO] Finished at: Thu May 29 15:48:19 CEST 2014
> [INFO] Final Memory: 20M/491M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.4-SNAPSHOT:site (default-site)
> on project failure-it: Error during page generation: Error rendering Maven
> report: Cannot run changelog command : Can't load the scm provider. SCM
> Connection is not set. -> [Help 1]{noformat}
> then people report m-site-p failed, which is wrong, and we need to guess from
> error message which report plugin failed
> this should be enhanced with information on the report which failed
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MSITE-713) improve "Error during page generation" error message
[
https://jira.codehaus.org/browse/MSITE-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=347292#comment-347292
]
Herve Boutemy edited comment on MSITE-713 at 5/29/14 10:34 AM:
---
done in [r1598319|http://svn.apache.org/r1598319]
now we have
{noformat}[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 3.502s
[INFO] Finished at: Thu May 29 17:20:04 CEST 2014
[INFO] Final Memory: 20M/491M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.4-SNAPSHOT:site (default-site) on
project failure-it: Error generating maven-changelog-plugin:2.2:dev-activity:
Cannot run changelog command : Can't load the scm provider. SCM Connection is
not set. -> [Help 1]{noformat}
was (Author: hboutemy):
done in [r1598319|http://svn.apache.org/r1598319]
> improve "Error during page generation" error message
>
>
> Key: MSITE-713
> URL: https://jira.codehaus.org/browse/MSITE-713
> Project: Maven Site Plugin
> Issue Type: Improvement
>Affects Versions: 3.3
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
> Fix For: 3.4
>
>
> the actual error message doesn't tell which report plugin caused a failure:
> {noformat}[INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 3.649s
> [INFO] Finished at: Thu May 29 15:48:19 CEST 2014
> [INFO] Final Memory: 20M/491M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.4-SNAPSHOT:site (default-site)
> on project failure-it: Error during page generation: Error rendering Maven
> report: Cannot run changelog command : Can't load the scm provider. SCM
> Connection is not set. -> [Help 1]{noformat}
> then people report m-site-p failed, which is wrong, and we need to guess from
> error message which report plugin failed
> this should be enhanced with information on the report which failed
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MSITE-714) display info on Doxia documents rendered
Herve Boutemy created MSITE-714: --- Summary: display info on Doxia documents rendered Key: MSITE-714 URL: https://jira.codehaus.org/browse/MSITE-714 Project: Maven Site Plugin Issue Type: Improvement Components: doxia integration Affects Versions: 3.3 Reporter: Herve Boutemy there is info on reports generation, but nothing on Doxia document parsed -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSITE-714) display info on Doxia documents rendered
[
https://jira.codehaus.org/browse/MSITE-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MSITE-714.
---
Resolution: Fixed
Fix Version/s: 3.4
Assignee: Herve Boutemy
done in [r1598416|http://svn.apache.org/r1598416]
"mvn site" on Maven site now displays
{noformat}[INFO] --- maven-site-plugin:3.4-SNAPSHOT:site (default-site) @
maven-site ---
[INFO] configuring report plugin
org.apache.maven.plugins:maven-project-info-reports-plugin:2.7
[INFO] Parent project loaded from repository: org.apache:apache:pom:14
[INFO] Relativizing decoration links with respect to project URL:
http://maven.apache.org/
[INFO] Rendering site with org.apache.maven.skins:maven-stylus-skin:jar:1.5
skin.
[INFO] Skipped "About" report (maven-project-info-reports-plugin:2.7:index),
file "index.html" already exists for the English version.
[INFO] Skipped "Source Repository" report
(maven-project-info-reports-plugin:2.7:scm), file "source-repository.html"
already exists for the English version.
[INFO] Skipped "Issue Tracking" report
(maven-project-info-reports-plugin:2.7:issue-tracking), file
"issue-tracking.html" already exists for the English version.
[INFO] Rendering 190 Doxia documents: 6 markdown, 9 xdoc, 171 apt, 4 fml
[WARNING] was already defined in , ignored in
.
[INFO] Generating "Continuous Integration" report---
maven-project-info-reports-plugin:2.7:cim
[INFO] Generating "Mailing Lists" report---
maven-project-info-reports-plugin:2.7:mailing-list
[INFO] Generating "Project License" report---
maven-project-info-reports-plugin:2.7:license
[INFO] Generating "Project Team" report---
maven-project-info-reports-plugin:2.7:project-team
[INFO] Generating "Project Summary" report---
maven-project-info-reports-plugin:2.7:summary
[INFO] Generating "Dependency Information" report---
maven-project-info-reports-plugin:2.7:dependency-info
[INFO] Generating "Project Modules" report---
maven-project-info-reports-plugin:2.7:modules
[INFO] Generating "Dependency Management" report---
maven-project-info-reports-plugin:2.7:dependency-management
[INFO] Generating "Dependencies" report---
maven-project-info-reports-plugin:2.7:dependencies
[INFO] Generating "Dependency Convergence" report---
maven-project-info-reports-plugin:2.7:dependency-convergence
[INFO] Generating "Plugin Management" report---
maven-project-info-reports-plugin:2.7:plugin-management
[INFO] Generating "Project Plugins" report---
maven-project-info-reports-plugin:2.7:plugins
[INFO] Generating "Distribution Management" report---
maven-project-info-reports-plugin:2.7:distribution-management
{noformat}
> display info on Doxia documents rendered
>
>
> Key: MSITE-714
> URL: https://jira.codehaus.org/browse/MSITE-714
> Project: Maven Site Plugin
> Issue Type: Improvement
> Components: doxia integration
>Affects Versions: 3.3
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
> Fix For: 3.4
>
>
> there is info on reports generation, but nothing on Doxia document parsed
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MSITE-714) display info on Doxia documents rendered
[
https://jira.codehaus.org/browse/MSITE-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=347301#comment-347301
]
Herve Boutemy edited comment on MSITE-714 at 5/29/14 4:52 PM:
--
done in [r1598416|http://svn.apache.org/r1598416]
"mvn site" on Maven site now displays
{noformat}[INFO] --- maven-site-plugin:3.4-SNAPSHOT:site (default-site) @
maven-site ---
[INFO] configuring report plugin
org.apache.maven.plugins:maven-project-info-reports-plugin:2.7
[INFO] Parent project loaded from repository: org.apache:apache:pom:14
[INFO] Relativizing decoration links with respect to project URL:
http://maven.apache.org/
[INFO] Rendering site with org.apache.maven.skins:maven-stylus-skin:jar:1.5
skin.
[INFO] Skipped "About" report (maven-project-info-reports-plugin:2.7:index),
file "index.html" already exists for the English version.
[INFO] Skipped "Source Repository" report
(maven-project-info-reports-plugin:2.7:scm), file "source-repository.html"
already exists for the English version.
[INFO] Skipped "Issue Tracking" report
(maven-project-info-reports-plugin:2.7:issue-tracking), file
"issue-tracking.html" already exists for the English version.
[INFO] Rendering 190 Doxia documents: 171 apt, 4 fml, 6 markdown, 9 xdoc
[WARNING] was already defined in , ignored in
.
[INFO] Generating "Continuous Integration" report---
maven-project-info-reports-plugin:2.7:cim
[INFO] Generating "Mailing Lists" report---
maven-project-info-reports-plugin:2.7:mailing-list
[INFO] Generating "Project License" report---
maven-project-info-reports-plugin:2.7:license
[INFO] Generating "Project Team" report---
maven-project-info-reports-plugin:2.7:project-team
[INFO] Generating "Project Summary" report---
maven-project-info-reports-plugin:2.7:summary
[INFO] Generating "Dependency Information" report---
maven-project-info-reports-plugin:2.7:dependency-info
[INFO] Generating "Project Modules" report---
maven-project-info-reports-plugin:2.7:modules
[INFO] Generating "Dependency Management" report---
maven-project-info-reports-plugin:2.7:dependency-management
[INFO] Generating "Dependencies" report---
maven-project-info-reports-plugin:2.7:dependencies
[INFO] Generating "Dependency Convergence" report---
maven-project-info-reports-plugin:2.7:dependency-convergence
[INFO] Generating "Plugin Management" report---
maven-project-info-reports-plugin:2.7:plugin-management
[INFO] Generating "Project Plugins" report---
maven-project-info-reports-plugin:2.7:plugins
[INFO] Generating "Distribution Management" report---
maven-project-info-reports-plugin:2.7:distribution-management
{noformat}
was (Author: hboutemy):
done in [r1598416|http://svn.apache.org/r1598416]
"mvn site" on Maven site now displays
{noformat}[INFO] --- maven-site-plugin:3.4-SNAPSHOT:site (default-site) @
maven-site ---
[INFO] configuring report plugin
org.apache.maven.plugins:maven-project-info-reports-plugin:2.7
[INFO] Parent project loaded from repository: org.apache:apache:pom:14
[INFO] Relativizing decoration links with respect to project URL:
http://maven.apache.org/
[INFO] Rendering site with org.apache.maven.skins:maven-stylus-skin:jar:1.5
skin.
[INFO] Skipped "About" report (maven-project-info-reports-plugin:2.7:index),
file "index.html" already exists for the English version.
[INFO] Skipped "Source Repository" report
(maven-project-info-reports-plugin:2.7:scm), file "source-repository.html"
already exists for the English version.
[INFO] Skipped "Issue Tracking" report
(maven-project-info-reports-plugin:2.7:issue-tracking), file
"issue-tracking.html" already exists for the English version.
[INFO] Rendering 190 Doxia documents: 6 markdown, 9 xdoc, 171 apt, 4 fml
[WARNING] was already defined in , ignored in
.
[INFO] Generating "Continuous Integration" report---
maven-project-info-reports-plugin:2.7:cim
[INFO] Generating "Mailing Lists" report---
maven-project-info-reports-plugin:2.7:mailing-list
[INFO] Generating "Project License" report---
maven-project-info-reports-plugin:2.7:license
[INFO] Generating "Project Team" report---
maven-project-info-reports-plugin:2.7:project-team
[INFO] Generating "Project Summary" report---
maven-project-info-reports-plugin:2.7:summary
[INFO] Generating "Dependency Information" report---
maven-project-info-reports-plugin:2.7:dependency-info
[INFO] Generating "Project Modules" report---
maven-project-info-reports-plugin:2.7:modules
[INFO] Generating "Dependency Management" report---
maven-project-info-reports-plugin:2.7:dependency-management
[INFO] Generating "Dependencies" report---
maven-project-info-reports-plugin:2.7:dependencies
[INFO] Generating "Dependency Convergence" report---
maven-project-info-reports-plugin:2.7:dependency-convergence
[INFO] Generating "Plugin Management" report---
maven-p
[jira] (MEAR-189) fileNameMapping set to no-version breaks skinnyWars feature
David Hoffer created MEAR-189: - Summary: fileNameMapping set to no-version breaks skinnyWars feature Key: MEAR-189 URL: https://jira.codehaus.org/browse/MEAR-189 Project: Maven Ear Plugin Issue Type: Bug Affects Versions: 2.9, 2.8, 2.7 Reporter: David Hoffer I have my plugin configured as: maven-ear-plugin 2.9 lib/ true no-version And the inclusion of no-version which I need, causes all the wars to fat. Is this a known bug? This is a major problem for me, is there any workaround? -- This message was sent by Atlassian JIRA (v6.1.6#6162)
