[jira] [Commented] (MASSEMBLY-851) "Unextractable" JAR files created by assembly:single
[
https://issues.apache.org/jira/browse/MASSEMBLY-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15960453#comment-15960453
]
Tom Wieczorek commented on MASSEMBLY-851:
-
Okay, spent some time debugging: The behavior is triggered when the Assembly
Plugin directly repackages JAR files into the assembly JAR.
Apache Commons Compress is used to read the source JAR file. When reading the
external attributes of the directory entries from the source JAR file, for some
reason, the symlink flag is {{true}} for the entries below {{META-INF/}}. That
triggers, of course, special treatment in the Plexus Archiver, which removes
the trailing slash from the direcory entry names in the destination JAR file.
This, in turn, triggers the error in the jar binary, because it treats the
trailing slash as indicator if a ZIP file entry is a file or a directory.
This explains why this issue doesn't show up on Windows, since the Windows
filesystems don't support symlinks and the code paths in question aren't used.
So the question is: Is it a bug inside Commons Compress when reading the
external attributes or is it already wrong inside the source JAR file, which
means that I'd need to dig through the Maven Jar Plugin, probably landing again
inside Plexus Archiver and Commons Compress...
This is getting somewhat tricky...
> "Unextractable" JAR files created by assembly:single
>
>
> Key: MASSEMBLY-851
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-851
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0
> Environment: Apache Maven 3.3.9
> (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
> Java version: 1.8.0_121, vendor: Oracle Corporation
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "linux", version: "4.8.0-41-generic", arch: "amd64", family: "unix"
>Reporter: Tom Wieczorek
> Attachments: mvn.log
>
>
> Under certain circumstances, {{assembly:single}} generates "unextractable"
> JAR files, because of some directory entries in the JAR file are not ending
> with a slash, hence they're treated as file entries.
> If such a JAR file is tried to be extracted via the {{jar}} executable, an
> Exception is thrown and extraction is aborted:
> {code}
> java.io.FileNotFoundException: META-INF/maven (Is a directory)
> at java.io.FileOutputStream.open0(Native Method)
> at java.io.FileOutputStream.open(FileOutputStream.java:270)
> at java.io.FileOutputStream.(FileOutputStream.java:213)
> at java.io.FileOutputStream.(FileOutputStream.java:162)
> at sun.tools.jar.Main.copy(Main.java:909)
> at sun.tools.jar.Main.extractFile(Main.java:1069)
> at sun.tools.jar.Main.extract(Main.java:981)
> at sun.tools.jar.Main.run(Main.java:311)
> at sun.tools.jar.Main.main(Main.java:1288)
> {code}
> A [sample project|https://github.com/twz123/broken-assembly] is on GitHub.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (MJAVADOC-479) module-info.java error: too many module declarations found
Ceki Gülcü created MJAVADOC-479:
---
Summary: module-info.java error: too many module declarations
found
Key: MJAVADOC-479
URL: https://issues.apache.org/jira/browse/MJAVADOC-479
Project: Maven Javadoc Plugin
Issue Type: Bug
Components: javadoc
Affects Versions: 2.10.4
Environment: Java HotSpot(TM) 64-Bit Server VM warning: ignoring
option MaxPermSize=128m; support was removed in 8.0
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T17:41:47+01:00)
Maven home: C:\java\maven-3.3.9
Java version: 1.8.0_121, vendor: Oracle Corporation
Java home: C:\java\jdk1.8.0_121\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "dos"
Reporter: Ceki Gülcü
Priority: Blocker
While attempting to release [SLF4J
1.8.0-alpha0|https://github.com/qos-ch/slf4j/tree/1_8_0-SNAPSHOT], the "mvn
site:site" command failed with the following error.
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.3:site (default-cli) on project
slf4j-parent: Error during page generation
: Error rendering Maven report:
[ERROR] Exit code: 1 -
C:\home\ceki\slf4j\slf4j-simple\src\main\java\module-info.java:1: error: too
many module declarations found
[ERROR] module org.slf4j.simple {
[ERROR] ^
[ERROR] C:\home\ceki\slf4j\slf4j-nop\src\main\java\module-info.java:1: error:
too many module declarations found
[ERROR] module org.slf4j.nop {
[ERROR] ^
[ERROR] C:\home\ceki\slf4j\slf4j-jdk14\src\main\java\module-info.java:1: error:
too many module declarations found
[ERROR] module org.slf4j.jul {
[ERROR] ^
[ERROR] C:\home\ceki\slf4j\jcl-over-slf4j\src\main\java\module-info.java:1:
error: too many module declarations found
[ERROR] module org.slf4j.jcl_over_slf4j {
[ERROR] ^
[ERROR] C:\home\ceki\slf4j\log4j-over-slf4j\src\main\java\module-info.java:1:
error: too many module declarations found
[ERROR] module org.slf4j.log4j_over_slf4j {
[ERROR] ^
[ERROR]
[ERROR] Command line was: C:\java\jdk-9EA162\bin\javadoc.exe @options @packages
@argfile
[ERROR]
[ERROR] Refer to the generated Javadoc files in
'C:\home\ceki\slf4j\target\site\apidocs' dir.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MJAVADOC-479) module-info.java error: too many module declarations found
[
https://issues.apache.org/jira/browse/MJAVADOC-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ceki Gülcü updated MJAVADOC-479:
Attachment: output.txt
Output of "mvn site:site -X > output.txt"
> module-info.java error: too many module declarations found
> ---
>
> Key: MJAVADOC-479
> URL: https://issues.apache.org/jira/browse/MJAVADOC-479
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 2.10.4
> Environment: Java HotSpot(TM) 64-Bit Server VM warning: ignoring
> option MaxPermSize=128m; support was removed in 8.0
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-10T17:41:47+01:00)
> Maven home: C:\java\maven-3.3.9
> Java version: 1.8.0_121, vendor: Oracle Corporation
> Java home: C:\java\jdk1.8.0_121\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "dos"
>Reporter: Ceki Gülcü
>Priority: Blocker
> Attachments: output.txt
>
>
> While attempting to release [SLF4J
> 1.8.0-alpha0|https://github.com/qos-ch/slf4j/tree/1_8_0-SNAPSHOT], the "mvn
> site:site" command failed with the following error.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.3:site (default-cli) on project
> slf4j-parent: Error during page generation
> : Error rendering Maven report:
> [ERROR] Exit code: 1 -
> C:\home\ceki\slf4j\slf4j-simple\src\main\java\module-info.java:1: error: too
> many module declarations found
> [ERROR] module org.slf4j.simple {
> [ERROR] ^
> [ERROR] C:\home\ceki\slf4j\slf4j-nop\src\main\java\module-info.java:1: error:
> too many module declarations found
> [ERROR] module org.slf4j.nop {
> [ERROR] ^
> [ERROR] C:\home\ceki\slf4j\slf4j-jdk14\src\main\java\module-info.java:1:
> error: too many module declarations found
> [ERROR] module org.slf4j.jul {
> [ERROR] ^
> [ERROR] C:\home\ceki\slf4j\jcl-over-slf4j\src\main\java\module-info.java:1:
> error: too many module declarations found
> [ERROR] module org.slf4j.jcl_over_slf4j {
> [ERROR] ^
> [ERROR] C:\home\ceki\slf4j\log4j-over-slf4j\src\main\java\module-info.java:1:
> error: too many module declarations found
> [ERROR] module org.slf4j.log4j_over_slf4j {
> [ERROR] ^
> [ERROR]
> [ERROR] Command line was: C:\java\jdk-9EA162\bin\javadoc.exe @options
> @packages @argfile
> [ERROR]
> [ERROR] Refer to the generated Javadoc files in
> 'C:\home\ceki\slf4j\target\site\apidocs' dir.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (MJAVADOC-479) module-info.java error: too many module declarations found
[
https://issues.apache.org/jira/browse/MJAVADOC-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15960515#comment-15960515
]
Ceki Gülcü edited comment on MJAVADOC-479 at 4/7/17 9:07 AM:
-
Output of "mvn site:site -X > output.txt" added as an attachment.
Upgrading the site plugin from 3.3 to 3.6 did not seem to help.
was (Author: c...@qos.ch):
Output of "mvn site:site -X > output.txt"
> module-info.java error: too many module declarations found
> ---
>
> Key: MJAVADOC-479
> URL: https://issues.apache.org/jira/browse/MJAVADOC-479
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 2.10.4
> Environment: Java HotSpot(TM) 64-Bit Server VM warning: ignoring
> option MaxPermSize=128m; support was removed in 8.0
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-10T17:41:47+01:00)
> Maven home: C:\java\maven-3.3.9
> Java version: 1.8.0_121, vendor: Oracle Corporation
> Java home: C:\java\jdk1.8.0_121\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "dos"
>Reporter: Ceki Gülcü
>Priority: Blocker
> Attachments: output.txt
>
>
> While attempting to release [SLF4J
> 1.8.0-alpha0|https://github.com/qos-ch/slf4j/tree/1_8_0-SNAPSHOT], the "mvn
> site:site" command failed with the following error.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.3:site (default-cli) on project
> slf4j-parent: Error during page generation
> : Error rendering Maven report:
> [ERROR] Exit code: 1 -
> C:\home\ceki\slf4j\slf4j-simple\src\main\java\module-info.java:1: error: too
> many module declarations found
> [ERROR] module org.slf4j.simple {
> [ERROR] ^
> [ERROR] C:\home\ceki\slf4j\slf4j-nop\src\main\java\module-info.java:1: error:
> too many module declarations found
> [ERROR] module org.slf4j.nop {
> [ERROR] ^
> [ERROR] C:\home\ceki\slf4j\slf4j-jdk14\src\main\java\module-info.java:1:
> error: too many module declarations found
> [ERROR] module org.slf4j.jul {
> [ERROR] ^
> [ERROR] C:\home\ceki\slf4j\jcl-over-slf4j\src\main\java\module-info.java:1:
> error: too many module declarations found
> [ERROR] module org.slf4j.jcl_over_slf4j {
> [ERROR] ^
> [ERROR] C:\home\ceki\slf4j\log4j-over-slf4j\src\main\java\module-info.java:1:
> error: too many module declarations found
> [ERROR] module org.slf4j.log4j_over_slf4j {
> [ERROR] ^
> [ERROR]
> [ERROR] Command line was: C:\java\jdk-9EA162\bin\javadoc.exe @options
> @packages @argfile
> [ERROR]
> [ERROR] Refer to the generated Javadoc files in
> 'C:\home\ceki\slf4j\target\site\apidocs' dir.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (MJAVADOC-479) module-info.java error: too many module declarations found
[
https://issues.apache.org/jira/browse/MJAVADOC-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15960539#comment-15960539
]
Robert Scholte commented on MJAVADOC-479:
-
The handling of artifacts with modulepath hasn't been implemented yet for this
plugin. There are probably 2 workarounds for now: 1. ignore the module-info
file 2. manually add the required arguments.
Anyhow, we should pick this up soon.
> module-info.java error: too many module declarations found
> ---
>
> Key: MJAVADOC-479
> URL: https://issues.apache.org/jira/browse/MJAVADOC-479
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 2.10.4
> Environment: Java HotSpot(TM) 64-Bit Server VM warning: ignoring
> option MaxPermSize=128m; support was removed in 8.0
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-10T17:41:47+01:00)
> Maven home: C:\java\maven-3.3.9
> Java version: 1.8.0_121, vendor: Oracle Corporation
> Java home: C:\java\jdk1.8.0_121\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "dos"
>Reporter: Ceki Gülcü
>Priority: Blocker
> Attachments: output.txt
>
>
> While attempting to release [SLF4J
> 1.8.0-alpha0|https://github.com/qos-ch/slf4j/tree/1_8_0-SNAPSHOT], the "mvn
> site:site" command failed with the following error.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.3:site (default-cli) on project
> slf4j-parent: Error during page generation
> : Error rendering Maven report:
> [ERROR] Exit code: 1 -
> C:\home\ceki\slf4j\slf4j-simple\src\main\java\module-info.java:1: error: too
> many module declarations found
> [ERROR] module org.slf4j.simple {
> [ERROR] ^
> [ERROR] C:\home\ceki\slf4j\slf4j-nop\src\main\java\module-info.java:1: error:
> too many module declarations found
> [ERROR] module org.slf4j.nop {
> [ERROR] ^
> [ERROR] C:\home\ceki\slf4j\slf4j-jdk14\src\main\java\module-info.java:1:
> error: too many module declarations found
> [ERROR] module org.slf4j.jul {
> [ERROR] ^
> [ERROR] C:\home\ceki\slf4j\jcl-over-slf4j\src\main\java\module-info.java:1:
> error: too many module declarations found
> [ERROR] module org.slf4j.jcl_over_slf4j {
> [ERROR] ^
> [ERROR] C:\home\ceki\slf4j\log4j-over-slf4j\src\main\java\module-info.java:1:
> error: too many module declarations found
> [ERROR] module org.slf4j.log4j_over_slf4j {
> [ERROR] ^
> [ERROR]
> [ERROR] Command line was: C:\java\jdk-9EA162\bin\javadoc.exe @options
> @packages @argfile
> [ERROR]
> [ERROR] Refer to the generated Javadoc files in
> 'C:\home\ceki\slf4j\target\site\apidocs' dir.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (MJAVADOC-479) module-info.java error: too many module declarations found
[
https://issues.apache.org/jira/browse/MJAVADOC-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15960568#comment-15960568
]
Ceki Gülcü commented on MJAVADOC-479:
-
Excluding the module-info.java files within the javadoc-plugin helped. Thank
you.
> module-info.java error: too many module declarations found
> ---
>
> Key: MJAVADOC-479
> URL: https://issues.apache.org/jira/browse/MJAVADOC-479
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 2.10.4
> Environment: Java HotSpot(TM) 64-Bit Server VM warning: ignoring
> option MaxPermSize=128m; support was removed in 8.0
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-10T17:41:47+01:00)
> Maven home: C:\java\maven-3.3.9
> Java version: 1.8.0_121, vendor: Oracle Corporation
> Java home: C:\java\jdk1.8.0_121\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "dos"
>Reporter: Ceki Gülcü
>Priority: Blocker
> Attachments: output.txt
>
>
> While attempting to release [SLF4J
> 1.8.0-alpha0|https://github.com/qos-ch/slf4j/tree/1_8_0-SNAPSHOT], the "mvn
> site:site" command failed with the following error.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.3:site (default-cli) on project
> slf4j-parent: Error during page generation
> : Error rendering Maven report:
> [ERROR] Exit code: 1 -
> C:\home\ceki\slf4j\slf4j-simple\src\main\java\module-info.java:1: error: too
> many module declarations found
> [ERROR] module org.slf4j.simple {
> [ERROR] ^
> [ERROR] C:\home\ceki\slf4j\slf4j-nop\src\main\java\module-info.java:1: error:
> too many module declarations found
> [ERROR] module org.slf4j.nop {
> [ERROR] ^
> [ERROR] C:\home\ceki\slf4j\slf4j-jdk14\src\main\java\module-info.java:1:
> error: too many module declarations found
> [ERROR] module org.slf4j.jul {
> [ERROR] ^
> [ERROR] C:\home\ceki\slf4j\jcl-over-slf4j\src\main\java\module-info.java:1:
> error: too many module declarations found
> [ERROR] module org.slf4j.jcl_over_slf4j {
> [ERROR] ^
> [ERROR] C:\home\ceki\slf4j\log4j-over-slf4j\src\main\java\module-info.java:1:
> error: too many module declarations found
> [ERROR] module org.slf4j.log4j_over_slf4j {
> [ERROR] ^
> [ERROR]
> [ERROR] Command line was: C:\java\jdk-9EA162\bin\javadoc.exe @options
> @packages @argfile
> [ERROR]
> [ERROR] Refer to the generated Javadoc files in
> 'C:\home\ceki\slf4j\target\site\apidocs' dir.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MJAVADOC-479) module-info.java error: too many module declarations found
[
https://issues.apache.org/jira/browse/MJAVADOC-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ceki Gülcü updated MJAVADOC-479:
Priority: Major (was: Blocker)
> module-info.java error: too many module declarations found
> ---
>
> Key: MJAVADOC-479
> URL: https://issues.apache.org/jira/browse/MJAVADOC-479
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 2.10.4
> Environment: Java HotSpot(TM) 64-Bit Server VM warning: ignoring
> option MaxPermSize=128m; support was removed in 8.0
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-10T17:41:47+01:00)
> Maven home: C:\java\maven-3.3.9
> Java version: 1.8.0_121, vendor: Oracle Corporation
> Java home: C:\java\jdk1.8.0_121\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "dos"
>Reporter: Ceki Gülcü
> Attachments: output.txt
>
>
> While attempting to release [SLF4J
> 1.8.0-alpha0|https://github.com/qos-ch/slf4j/tree/1_8_0-SNAPSHOT], the "mvn
> site:site" command failed with the following error.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.3:site (default-cli) on project
> slf4j-parent: Error during page generation
> : Error rendering Maven report:
> [ERROR] Exit code: 1 -
> C:\home\ceki\slf4j\slf4j-simple\src\main\java\module-info.java:1: error: too
> many module declarations found
> [ERROR] module org.slf4j.simple {
> [ERROR] ^
> [ERROR] C:\home\ceki\slf4j\slf4j-nop\src\main\java\module-info.java:1: error:
> too many module declarations found
> [ERROR] module org.slf4j.nop {
> [ERROR] ^
> [ERROR] C:\home\ceki\slf4j\slf4j-jdk14\src\main\java\module-info.java:1:
> error: too many module declarations found
> [ERROR] module org.slf4j.jul {
> [ERROR] ^
> [ERROR] C:\home\ceki\slf4j\jcl-over-slf4j\src\main\java\module-info.java:1:
> error: too many module declarations found
> [ERROR] module org.slf4j.jcl_over_slf4j {
> [ERROR] ^
> [ERROR] C:\home\ceki\slf4j\log4j-over-slf4j\src\main\java\module-info.java:1:
> error: too many module declarations found
> [ERROR] module org.slf4j.log4j_over_slf4j {
> [ERROR] ^
> [ERROR]
> [ERROR] Command line was: C:\java\jdk-9EA162\bin\javadoc.exe @options
> @packages @argfile
> [ERROR]
> [ERROR] Refer to the generated Javadoc files in
> 'C:\home\ceki\slf4j\target\site\apidocs' dir.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (MNG-6209) inconsistent activation of components from multiple extensions=true plugins
Igor Fedorenko created MNG-6209: --- Summary: inconsistent activation of components from multiple extensions=true plugins Key: MNG-6209 URL: https://issues.apache.org/jira/browse/MNG-6209 Project: Maven Issue Type: Bug Components: Class Loading Affects Versions: 3.3.9, 3.3.3, 3.3.1 Reporter: Igor Fedorenko This is a regression introduced by the fix for MNG-5742. When multiple extensions=true plugins configured in the build, when mojos from one such plugin are executed, components from other extensions are ignored. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MSITE-210) DoxiaFilter does not set output encoding
[
https://issues.apache.org/jira/browse/MSITE-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Thistlethwaite updated MSITE-210:
---
Reporter: Daniel H. Peger (was: Daniel)
> DoxiaFilter does not set output encoding
>
>
> Key: MSITE-210
> URL: https://issues.apache.org/jira/browse/MSITE-210
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: encoding, site:run
>Affects Versions: 2.0-beta-5, 2.0-beta-6
>Reporter: Daniel H. Peger
>Assignee: Lukas Theussl
> Fix For: 2.1
>
> Attachments: MSITE-DoxiaFilter-patch.txt
>
>
> As mentioned in MSITE-19 DoxiaFilter does not set any output encoding. In my
> situation this makes {{site:run}} goal pretty much useless.
> Attaching a patch for trunk.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (MNG-6210) can't load @SessionScoped/@MojoExecutionScoped components from .mvn/extensions.xml
Igor Fedorenko created MNG-6210:
---
Summary: can't load @SessionScoped/@MojoExecutionScoped components
from .mvn/extensions.xml
Key: MNG-6210
URL: https://issues.apache.org/jira/browse/MNG-6210
Project: Maven
Issue Type: Bug
Components: Class Loading
Reporter: Igor Fedorenko
The build fails with the exception below if Maven core extensions defined in
.mvn/extensions.xml includes any @SessionScoped or MojoExecutionScoped
components
{code}
[WARNING]
ClassRealm[coreExtension>io.takari.maven:takari-workspace-reader:0.3.31-SNAPSHOT,
parent: ClassRealm[plexus.core, parent: null]]
com.google.inject.CreationException: Unable to create injector, see the
following errors:
1) No scope is bound to org.apache.maven.SessionScoped.
at io.takari.maven.workspace.GenerationsWorkspaceReader.class(Unknown Source)
at
ClassRealm[coreExtension>io.takari.maven:takari-workspace-reader:0.3.31-SNAPSHOT,
parent: ClassRealm[plexus.core, parent: null]] (via modules:
org.eclipse.sisu.wire.WireModule -> org.eclipse.sisu.plexus.PlexusBindingModule)
1 error
at
com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:466)
at
com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:155)
at
com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:107)
at com.google.inject.Guice.createInjector(Guice.java:96)
at com.google.inject.Guice.createInjector(Guice.java:73)
at com.google.inject.Guice.createInjector(Guice.java:62)
at
org.codehaus.plexus.DefaultPlexusContainer.addPlexusInjector(DefaultPlexusContainer.java:481)
at
org.codehaus.plexus.DefaultPlexusContainer.discoverComponents(DefaultPlexusContainer.java:460)
at
org.codehaus.plexus.DefaultPlexusContainer.discoverComponents(DefaultPlexusContainer.java:435)
at org.apache.maven.cli.MavenCli.container(MavenCli.java:568)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:287)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:205)
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)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (MNG-6210) can't load @SessionScoped/@MojoExecutionScoped components from .mvn/extensions.xml
[
https://issues.apache.org/jira/browse/MNG-6210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Fedorenko reassigned MNG-6210:
---
Assignee: Igor Fedorenko
> can't load @SessionScoped/@MojoExecutionScoped components from
> .mvn/extensions.xml
> --
>
> Key: MNG-6210
> URL: https://issues.apache.org/jira/browse/MNG-6210
> Project: Maven
> Issue Type: Bug
> Components: Class Loading
>Reporter: Igor Fedorenko
>Assignee: Igor Fedorenko
>
> The build fails with the exception below if Maven core extensions defined in
> .mvn/extensions.xml includes any @SessionScoped or MojoExecutionScoped
> components
> {code}
> [WARNING]
> ClassRealm[coreExtension>io.takari.maven:takari-workspace-reader:0.3.31-SNAPSHOT,
> parent: ClassRealm[plexus.core, parent: null]]
> com.google.inject.CreationException: Unable to create injector, see the
> following errors:
> 1) No scope is bound to org.apache.maven.SessionScoped.
> at io.takari.maven.workspace.GenerationsWorkspaceReader.class(Unknown
> Source)
> at
> ClassRealm[coreExtension>io.takari.maven:takari-workspace-reader:0.3.31-SNAPSHOT,
> parent: ClassRealm[plexus.core, parent: null]] (via modules:
> org.eclipse.sisu.wire.WireModule ->
> org.eclipse.sisu.plexus.PlexusBindingModule)
> 1 error
> at
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:466)
> at
> com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:155)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:107)
> at com.google.inject.Guice.createInjector(Guice.java:96)
> at com.google.inject.Guice.createInjector(Guice.java:73)
> at com.google.inject.Guice.createInjector(Guice.java:62)
> at
> org.codehaus.plexus.DefaultPlexusContainer.addPlexusInjector(DefaultPlexusContainer.java:481)
> at
> org.codehaus.plexus.DefaultPlexusContainer.discoverComponents(DefaultPlexusContainer.java:460)
> at
> org.codehaus.plexus.DefaultPlexusContainer.discoverComponents(DefaultPlexusContainer.java:435)
> at org.apache.maven.cli.MavenCli.container(MavenCli.java:568)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:287)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:205)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (MNG-6209) inconsistent activation of components from multiple extensions=true plugins
[ https://issues.apache.org/jira/browse/MNG-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Fedorenko reassigned MNG-6209: --- Assignee: Igor Fedorenko > inconsistent activation of components from multiple extensions=true plugins > --- > > Key: MNG-6209 > URL: https://issues.apache.org/jira/browse/MNG-6209 > Project: Maven > Issue Type: Bug > Components: Class Loading >Affects Versions: 3.3.1, 3.3.3, 3.3.9 >Reporter: Igor Fedorenko >Assignee: Igor Fedorenko > > This is a regression introduced by the fix for MNG-5742. When multiple > extensions=true plugins configured in the build, when mojos from one such > plugin are executed, components from other extensions are ignored. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (SUREFIRE-1357) PING scheduler kills JVM in debug mode
Tibor Digana created SUREFIRE-1357:
--
Summary: PING scheduler kills JVM in debug mode
Key: SUREFIRE-1357
URL: https://issues.apache.org/jira/browse/SUREFIRE-1357
Project: Maven Surefire
Issue Type: Bug
Components: Maven Failsafe Plugin, Maven Surefire Plugin
Reporter: Tibor Digana
Assignee: Tibor Digana
Fix For: 2.20
This issue was found during second Vote of Version 2.20.
Configuration parameter {{debugForkedProcess=true}} kills the JVM because all
threads are disabled for scheduling purposes and PING scheduler suggested
killing JVM when developer stepped into a break point after 20 seconds.
The dump file contains error
{{Corrupted stdin stream in forked JVM 1. Stream 'Listening for transport
dt_socket at address: 5005'.}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (SUREFIRE-1357) PING scheduler kills JVM in debug mode
[
https://issues.apache.org/jira/browse/SUREFIRE-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-1357.
--
Resolution: Fixed
https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=eed317207695e3174d2f283390dd0386fc09f3e4
> PING scheduler kills JVM in debug mode
> --
>
> Key: SUREFIRE-1357
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1357
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
>Reporter: Tibor Digana
>Assignee: Tibor Digana
> Fix For: 2.20
>
>
> This issue was found during second Vote of Version 2.20.
> Configuration parameter {{debugForkedProcess=true}} kills the JVM because all
> threads are disabled for scheduling purposes and PING scheduler suggested
> killing JVM when developer stepped into a break point after 20 seconds.
> The dump file contains error
> {{Corrupted stdin stream in forked JVM 1. Stream 'Listening for transport
> dt_socket at address: 5005'.}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (MLINKCHECK-30) https link does not exists and redirected by website to another url
Roman Ivanov created MLINKCHECK-30: -- Summary: https link does not exists and redirected by website to another url Key: MLINKCHECK-30 URL: https://issues.apache.org/jira/browse/MLINKCHECK-30 Project: Maven Linkcheck Plugin Issue Type: Bug Reporter: Roman Ivanov there is during site creation of checkstyle project (https://github.com/checkstyle/checkstyle) - "mvn site" there is url - http://downloads.sourceforge.net/project/checkstyle/checkstyle/7.7-SNAPSHOT/checkstyle-7.7-SNAPSHOT-all.jar it does not exists on sourceforge, as we publish only released jars, http://wheregoes.com/retracer.php for "http://downloads.sourceforge.net/project/checkstyle/checkstyle/7.7-SNAPSHOT/checkstyle-7.7-SNAPSHOT-all.jar"; show a problem(404) but in browser this link is redirected to https://sourceforge.net/projects/checkstyle/files/ Redirections are not allowed in config. Previously validation worked fine so that we have this link in excludes. Now it does not generate a error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (SUREFIRE-1358) Directory in Class-Path in manifest of forked jvm ends with two slashes //
Tibor Digana created SUREFIRE-1358: -- Summary: Directory in Class-Path in manifest of forked jvm ends with two slashes // Key: SUREFIRE-1358 URL: https://issues.apache.org/jira/browse/SUREFIRE-1358 Project: Maven Surefire Issue Type: Bug Components: Maven Failsafe Plugin, Maven Surefire Plugin Reporter: Tibor Digana Assignee: Tibor Digana Fix For: 2.20 This issue was found during the second Vote of release Version 2.20. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (SUREFIRE-1358) Directory in Class-Path in manifest of forked jvm ends with two slashes //
[ https://issues.apache.org/jira/browse/SUREFIRE-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1358. -- Resolution: Fixed https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=6fd0a3e7ca7c27234dab67be27efc10875d7a2e6 > Directory in Class-Path in manifest of forked jvm ends with two slashes // > -- > > Key: SUREFIRE-1358 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1358 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Failsafe Plugin, Maven Surefire Plugin >Reporter: Tibor Digana >Assignee: Tibor Digana > Fix For: 2.20 > > > This issue was found during the second Vote of release Version 2.20. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SUREFIRE-1357) PING scheduler kills JVM in debug mode
[
https://issues.apache.org/jira/browse/SUREFIRE-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961484#comment-15961484
]
Hudson commented on SUREFIRE-1357:
--
UNSTABLE: Integrated in Jenkins build maven-surefire #1690 (See
[https://builds.apache.org/job/maven-surefire/1690/])
[SUREFIRE-1357] PING scheduler kills JVM in debug mode (tibor17:
[http://git-wip-us.apache.org/repos/asf/?p=maven-surefire.git&a=commit&h=eed317207695e3174d2f283390dd0386fc09f3e4])
* (edit)
surefire-booter/src/main/java/org/apache/maven/surefire/booter/ForkedBooter.java
* (edit)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/output/ForkClient.java
> PING scheduler kills JVM in debug mode
> --
>
> Key: SUREFIRE-1357
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1357
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
>Reporter: Tibor Digana
>Assignee: Tibor Digana
> Fix For: 2.20
>
>
> This issue was found during second Vote of Version 2.20.
> Configuration parameter {{debugForkedProcess=true}} kills the JVM because all
> threads are disabled for scheduling purposes and PING scheduler suggested
> killing JVM when developer stepped into a break point after 20 seconds.
> The dump file contains error
> {{Corrupted stdin stream in forked JVM 1. Stream 'Listening for transport
> dt_socket at address: 5005'.}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (SUREFIRE-1358) Directory in Class-Path in manifest of forked jvm ends with two slashes //
[ https://issues.apache.org/jira/browse/SUREFIRE-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961543#comment-15961543 ] Hudson commented on SUREFIRE-1358: -- UNSTABLE: Integrated in Jenkins build maven-surefire #1691 (See [https://builds.apache.org/job/maven-surefire/1691/]) [SUREFIRE-1358] Directory in Class-Path in manifest of forked jvm ends (tibor17: [http://git-wip-us.apache.org/repos/asf/?p=maven-surefire.git&a=commit&h=6fd0a3e7ca7c27234dab67be27efc10875d7a2e6]) * (edit) maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/ForkConfiguration.java > Directory in Class-Path in manifest of forked jvm ends with two slashes // > -- > > Key: SUREFIRE-1358 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1358 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Failsafe Plugin, Maven Surefire Plugin >Reporter: Tibor Digana >Assignee: Tibor Digana > Fix For: 2.20 > > > This issue was found during the second Vote of release Version 2.20. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
