[jira] [Commented] (MDEP-559) Java 9 bytecode cannot be parsed
[
https://issues.apache.org/jira/browse/MDEP-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205321#comment-16205321
]
Mark Raynsford commented on MDEP-559:
-
To clarify: I think the new ASM version would work, it's just that the shared
component doesn't know what to do with the new constants yet.
> Java 9 bytecode cannot be parsed
>
>
> Key: MDEP-559
> URL: https://issues.apache.org/jira/browse/MDEP-559
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Affects Versions: 3.0.0
> Environment: Apache Maven 3.3.9
> (NON-CANONICAL_2015-11-23T13:17:27+03:00_root; 2015-11-23T21:17:27+11:00)
> Maven home: /opt/maven
> Java version: 9-ea, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-9-jdk
> Default locale: en_AU, platform encoding: UTF-8
> OS name: "linux", version: "4.9.11-1-arch", arch: "amd64", family: "unix"
>Reporter: Ben Alex
>Assignee: Robert Scholte
>
> Attempting to run analyze-only against source compiled with Java 9 results in:
> {noformat}
> [INFO] --- maven-dependency-plugin:3.0.0:analyze-only (config-dependency) @
> lmdbjava ---
> [DEBUG] Configuring mojo
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only from
> plugin realm
> ClassRealm[plugin>org.apache.maven.plugins:maven-dependency-plugin:3.0.0,
> parent: jdk.internal.loader.ClassLoaders$AppClassLoader@3b764bce]
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only' with
> basic configurator -->
> [DEBUG] (f) analyzer = default
> [DEBUG] (f) baseDir = /home/bpa/projects/lmdbjava
> [DEBUG] (f) failOnWarning = true
> [DEBUG] (f) ignoreNonCompile = false
> [DEBUG] (f) outputDirectory = /home/bpa/projects/lmdbjava/target
> [DEBUG] (f) outputXML = false
> [DEBUG] (f) project = MavenProject: org.lmdbjava:lmdbjava:0.0.6-SNAPSHOT @
> /home/bpa/projects/lmdbjava/dependency-reduced-pom.xml
> [DEBUG] (f) scriptableFlag = $$%%%
> [DEBUG] (f) scriptableOutput = false
> [DEBUG] (f) skip = false
> [DEBUG] (f) usedDependencies = [org.lmdbjava:lmdbjava-native-linux-x86_64,
> org.lmdbjava:lmdbjava-native-windows-x86_64,
> org.lmdbjava:lmdbjava-native-osx-x86_64]
> [DEBUG] (f) verbose = false
> [DEBUG] -- end configuration --
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 7.256 s
> [INFO] Finished at: 2017-03-17T17:32:20+11:00
> [INFO] Final Memory: 40M/132M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only
> (config-dependency) on project lmdbjava: Execution config-dependency of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only failed.
> IllegalArgumentException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only
> (config-dependency) on project lmdbjava: Execution config-dependency of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only 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
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflec
[jira] [Commented] (MDEP-559) Java 9 bytecode cannot be parsed
[
https://issues.apache.org/jira/browse/MDEP-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205319#comment-16205319
]
Mark Raynsford commented on MDEP-559:
-
I've had a peek at the code, and the code in question is a switch statement
that receives constant pool entries in a loop. It's encountering a
`CONSTANT_Module` value (19) and raising an exception. I'm not sure how much
the two new `CONSTANT_Module` and `CONSTANT_package` values would be used in
dependency analysis. I believe they're only permitted to exist in module
descriptors.
> Java 9 bytecode cannot be parsed
>
>
> Key: MDEP-559
> URL: https://issues.apache.org/jira/browse/MDEP-559
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Affects Versions: 3.0.0
> Environment: Apache Maven 3.3.9
> (NON-CANONICAL_2015-11-23T13:17:27+03:00_root; 2015-11-23T21:17:27+11:00)
> Maven home: /opt/maven
> Java version: 9-ea, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-9-jdk
> Default locale: en_AU, platform encoding: UTF-8
> OS name: "linux", version: "4.9.11-1-arch", arch: "amd64", family: "unix"
>Reporter: Ben Alex
>Assignee: Robert Scholte
>
> Attempting to run analyze-only against source compiled with Java 9 results in:
> {noformat}
> [INFO] --- maven-dependency-plugin:3.0.0:analyze-only (config-dependency) @
> lmdbjava ---
> [DEBUG] Configuring mojo
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only from
> plugin realm
> ClassRealm[plugin>org.apache.maven.plugins:maven-dependency-plugin:3.0.0,
> parent: jdk.internal.loader.ClassLoaders$AppClassLoader@3b764bce]
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only' with
> basic configurator -->
> [DEBUG] (f) analyzer = default
> [DEBUG] (f) baseDir = /home/bpa/projects/lmdbjava
> [DEBUG] (f) failOnWarning = true
> [DEBUG] (f) ignoreNonCompile = false
> [DEBUG] (f) outputDirectory = /home/bpa/projects/lmdbjava/target
> [DEBUG] (f) outputXML = false
> [DEBUG] (f) project = MavenProject: org.lmdbjava:lmdbjava:0.0.6-SNAPSHOT @
> /home/bpa/projects/lmdbjava/dependency-reduced-pom.xml
> [DEBUG] (f) scriptableFlag = $$%%%
> [DEBUG] (f) scriptableOutput = false
> [DEBUG] (f) skip = false
> [DEBUG] (f) usedDependencies = [org.lmdbjava:lmdbjava-native-linux-x86_64,
> org.lmdbjava:lmdbjava-native-windows-x86_64,
> org.lmdbjava:lmdbjava-native-osx-x86_64]
> [DEBUG] (f) verbose = false
> [DEBUG] -- end configuration --
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 7.256 s
> [INFO] Finished at: 2017-03-17T17:32:20+11:00
> [INFO] Final Memory: 40M/132M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only
> (config-dependency) on project lmdbjava: Execution config-dependency of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only failed.
> IllegalArgumentException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only
> (config-dependency) on project lmdbjava: Execution config-dependency of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only 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
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.b
[jira] [Commented] (MJLINK-4) NPE on execution
[
https://issues.apache.org/jira/browse/MJLINK-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205317#comment-16205317
]
Hudson commented on MJLINK-4:
-
SUCCESS: Integrated in Jenkins build maven-plugins #9162 (See
[https://builds.apache.org/job/maven-plugins/9162/])
[MJLINK-4] NPE on execution
Use requiresDependencyResolution instead of requiresDependencyCollection (which
only downloads the poms) (rfscholte:
[http://svn.apache.org/viewvc/?view=rev&rev=1812236])
* (edit) maven-jlink-plugin/pom.xml
* (add) maven-jlink-plugin/src/it
* (add) maven-jlink-plugin/src/it/mrm
* (add) maven-jlink-plugin/src/it/mrm/settings.xml
* (add) maven-jlink-plugin/src/it/projects
* (add) maven-jlink-plugin/src/it/projects/MJLINK-4_dependencyResolution
* (add) maven-jlink-plugin/src/it/projects/MJLINK-4_dependencyResolution/pom.xml
* (edit)
maven-jlink-plugin/src/main/java/org/apache/maven/plugins/jlink/JLinkMojo.java
> NPE on execution
> -
>
> Key: MJLINK-4
> URL: https://issues.apache.org/jira/browse/MJLINK-4
> Project: Maven JLink Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha-1
> Environment: Ubuntu 16.04.3 LTS
> Linux 4.4.0-93-generic
>Reporter: Johannes Boesl
>Assignee: Robert Scholte
> Fix For: 3.0.0-alpha-2
>
>
> When I try to run my maven build I get the following exception:
> {noformat}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink
> (default-jlink) on project jloadr-jre: Execution default-jlink of goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.:
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink
> (default-jlink) on project jloadr-jre: Execution default-jlink of goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:200)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:196)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:514)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
> at java.base/java.lang.Thread.run(Thread.java:844)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-jlink of goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 11 more
> Caused by: java.lang.NullPointerException
> at
> org.codehaus.plexus.languages.java.jpms.ResolvePathsRequest$1.toPath(ResolvePathsRequest.java:52)
> at
> org.codehaus.plexus.languages.java.jpms.ResolvePathsRequest$1.toPath(ResolvePathsRequest.java:48)
> at
> org.codehaus.plexus.languages.java.jpms.LocationManager.resolvePaths(LocationManager.java:109)
> at
> org.apache.maven.plugins.jlink.JLinkMojo.preparePaths(JLinkMojo.java:347)
> at org.apache.maven.plugins.jlink.JLinkMojo.execute(JLinkMojo.java:264)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> ... 12 more{quote}
> {noformat}
> The cause seems to be that the following code in line 337 in JLinkMojo
> returns a collection with only 'null' entries:
> {{Collection dependencyArtifacts = getCompileClasspathElements(
> getProject() );}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (MJLINK-4) NPE on execution
[
https://issues.apache.org/jira/browse/MJLINK-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MJLINK-4.
---
Resolution: Fixed
Fix Version/s: 3.0.0-alpha-2
Fixed in [r1812236| http://svn.apache.org/viewvc?rev=1812236&view=rev]
Key issue was that only the poms were downloaded, without the main artifacts.
I've added an integration test to confirm this.
Thanks for the provided examples and the good intentions for the fix, which n
the end was only a replacement of one word.
> NPE on execution
> -
>
> Key: MJLINK-4
> URL: https://issues.apache.org/jira/browse/MJLINK-4
> Project: Maven JLink Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha-1
> Environment: Ubuntu 16.04.3 LTS
> Linux 4.4.0-93-generic
>Reporter: Johannes Boesl
>Assignee: Robert Scholte
> Fix For: 3.0.0-alpha-2
>
>
> When I try to run my maven build I get the following exception:
> {noformat}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink
> (default-jlink) on project jloadr-jre: Execution default-jlink of goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.:
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink
> (default-jlink) on project jloadr-jre: Execution default-jlink of goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:200)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:196)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:514)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
> at java.base/java.lang.Thread.run(Thread.java:844)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-jlink of goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 11 more
> Caused by: java.lang.NullPointerException
> at
> org.codehaus.plexus.languages.java.jpms.ResolvePathsRequest$1.toPath(ResolvePathsRequest.java:52)
> at
> org.codehaus.plexus.languages.java.jpms.ResolvePathsRequest$1.toPath(ResolvePathsRequest.java:48)
> at
> org.codehaus.plexus.languages.java.jpms.LocationManager.resolvePaths(LocationManager.java:109)
> at
> org.apache.maven.plugins.jlink.JLinkMojo.preparePaths(JLinkMojo.java:347)
> at org.apache.maven.plugins.jlink.JLinkMojo.execute(JLinkMojo.java:264)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> ... 12 more{quote}
> {noformat}
> The cause seems to be that the following code in line 337 in JLinkMojo
> returns a collection with only 'null' entries:
> {{Collection dependencyArtifacts = getCompileClasspathElements(
> getProject() );}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (SUREFIRE-1431) @{argLine} not replaced if undefined
[
https://issues.apache.org/jira/browse/SUREFIRE-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205306#comment-16205306
]
Tibor Digana commented on SUREFIRE-1431:
I think this could be discussed on stackoverflow rather.
I could write a project showcase on Github for you if I had spare time this
week. I am preparing a new release, so I would be busy. Just ping me with that
in a week if I forgot to reply.
> @{argLine} not replaced if undefined
>
>
> Key: SUREFIRE-1431
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1431
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.21.1
> Environment: Maven 3.5.0
>Reporter: Matthieu Fillon
>Assignee: Tibor Digana
> Attachments: maven.log
>
>
> I need to specify argLine for my tests. I also need it to work with Java
> agent Jacoco when a certain Maven profile is activated.
> So I added `@{argLine}` to my argLine property and it works fine when running
> with Jacoco agent activated.
> When running the tests without profile that activates Jacoco agent, the
> surefire plugin fails with following line (relevant maven logs attached) :
> {color:red}Error: Could not find or load main class @\{argLine} {color}
> I guess @{argLine} is only replaced if an argLine has been defined before by
> another plugin but if not it is not replaced at all.
> Should'nt it be replaced in any case and if none defined, just replace with
> empty value?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ARCHETYPE-505) archetype:create-from-project,the .gitignore file not copy to archetype-resources
[
https://issues.apache.org/jira/browse/ARCHETYPE-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205303#comment-16205303
]
justin georgeson commented on ARCHETYPE-505:
I think ignoring such files by default makes sense, especially when using
_create-from-project_. _But_ ... I'm using maven-archetype-plugin 3.0.1 with
the maven-archetype packaging type to build my archetype (ie I have the v2
format archetype-metadata.xml descriptor and the template project contents in
src/main/resources/archetype-resources) and have expressly requested to include
the .gitignore (or any other file that's in the default excludes). It's
silently ignoring what I've configured. It should at least warn me that's it's
not fulfilling my project configuration.
The only current workaround I can think of is to write a post-generation script
(src/main/resources/META-INF/archetype-post-generate.groovy) to generate my
.gitignore and .gitattributes files. Is that my only option with current
release?
> archetype:create-from-project,the .gitignore file not copy to
> archetype-resources
> -
>
> Key: ARCHETYPE-505
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-505
> Project: Maven Archetype
> Issue Type: Bug
> Components: Archetypes
>Affects Versions: 2.4
> Environment: maven 3.3 ,maven-archetype-plugin 2.4
>Reporter: feilong
> Attachments: webapp-springmvc32.zip
>
>
> I have a very simple maven test project for {{archetype:create-from-project}}
> such as :(you can download from the Attachment)
> {noformat}
> | .gitignore
> | pom.xml
> |
> \---src
> +---main
> | \---java
> | overview.html
> |
> \---test
> {noformat}
> only {{.gitignore}} and {{pom.xml}}, and {{overview.html}} files
> and I excute the command line in the root folder:
> {code:xml}
> mvn -X archetype:create-from-project
> {code}
> I see ,in the
> {{target\generated-sources\archetype\src\main\resources\archetype-resources}}
> folder, only
> {noformat}
> | pom.xml
> |
> \---src
> \---main
> \---java
> overview.html
> {noformat}
> no {{.gitignore}} file
>
> first , I search the same issue in jira, there is #ARCHETYPE-474 , but not as
> my scene
>
> I search some solution in stackoverflow
> http://stackoverflow.com/questions/7981060/maven-archetype-plugin-doesnt-let-resources-in-archetype-resources-through#answer-37322323
> In pom.xml,I have also configed that
> {code:xml}
>
> maven-resources-plugin
> 3.0.1
>
> utf-8
> true
> false
>
>
>
> default-resources
> process-resources
>
> resources
>
>
> true
>
>
>
> default-testResources
> process-test-resources
>
> testResources
>
>
>
>
> {code}
> {{maven-resources-plugin}} set {{addDefaultExcludes}} attribute to {{false}}
> but does't work
>
> so, I look for the maven-archetype source code in github
> https://github.com/apache/maven-archetype
> the
> org.apache.maven.archetype.creator.FilesetArchetypeCreator.*createArchetypeFiles*(Properties,
> List, String, File, File, String) method
> line 796 show that:
> {code:title=FilesetArchetypeCreator.java|borderStyle=solid}
> private void createArchetypeFiles( Properties reverseProperties,
> List fileSets, String packageName,
>File basedir, File
> archetypeFilesDirectory, String defaultEncoding )
> throws IOException
> {
> getLogger().debug( "Creating Archetype/Module files from " + basedir
> + " to " + archetypeFilesDirectory );
> for ( FileSet fileSet : fileSets )
> {
> DirectoryScanner scanner = new DirectoryScanner();
> scanner.setBasedir( basedir );
> scanner.setIncludes( (String[]) concatenateToList(
> fileSet.getIncludes(), fileSet.getDirectory() ).toArray(
> new String[fileSet.getIncludes().size()] ) );
> scanner.setExcludes( (String[]) fileSet.getExcludes().toArray(
> new String[fileSet.getExcludes().size()] ) );
> scanner.addDefaultExcludes();
> getLogger().debug( "Using fileset " + fileSet );
> scanner.scan();
> List fileSetResources = Arrays.asList(
> scanner.getIncludedFiles() );
> getLogger().debug( "Scanned " + fileSetResources.size() + "
> resources" );
>
> .
> {code}
> here is {{scanner.addDefaultExcludes();}}
> So , the result log show that :
> {noformat}
> [DEBUG] Creating Archetype/Module files f
[jira] [Assigned] (MJLINK-4) NPE on execution
[
https://issues.apache.org/jira/browse/MJLINK-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte reassigned MJLINK-4:
---
Assignee: Robert Scholte
> NPE on execution
> -
>
> Key: MJLINK-4
> URL: https://issues.apache.org/jira/browse/MJLINK-4
> Project: Maven JLink Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha-1
> Environment: Ubuntu 16.04.3 LTS
> Linux 4.4.0-93-generic
>Reporter: Johannes Boesl
>Assignee: Robert Scholte
>
> When I try to run my maven build I get the following exception:
> {noformat}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink
> (default-jlink) on project jloadr-jre: Execution default-jlink of goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.:
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink
> (default-jlink) on project jloadr-jre: Execution default-jlink of goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:200)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:196)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:514)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
> at java.base/java.lang.Thread.run(Thread.java:844)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-jlink of goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 11 more
> Caused by: java.lang.NullPointerException
> at
> org.codehaus.plexus.languages.java.jpms.ResolvePathsRequest$1.toPath(ResolvePathsRequest.java:52)
> at
> org.codehaus.plexus.languages.java.jpms.ResolvePathsRequest$1.toPath(ResolvePathsRequest.java:48)
> at
> org.codehaus.plexus.languages.java.jpms.LocationManager.resolvePaths(LocationManager.java:109)
> at
> org.apache.maven.plugins.jlink.JLinkMojo.preparePaths(JLinkMojo.java:347)
> at org.apache.maven.plugins.jlink.JLinkMojo.execute(JLinkMojo.java:264)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> ... 12 more{quote}
> {noformat}
> The cause seems to be that the following code in line 337 in JLinkMojo
> returns a collection with only 'null' entries:
> {{Collection dependencyArtifacts = getCompileClasspathElements(
> getProject() );}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Issue Comment Deleted] (SUREFIRE-1431) @{argLine} not replaced if undefined
[
https://issues.apache.org/jira/browse/SUREFIRE-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michal Domagala updated SUREFIRE-1431:
--
Comment: was deleted
(was: [~tibor17], could clarify your answer?
I understand that:
# I can setup argument line with *$*, but I have to know final settings before
I call Maven. It is problem because the settings is decided by jacoco plugin
during build
# To solve that issue *@* was introduced, but it fails without Jacoco plugin
As a solution I expect hint how to configure surefire to work without Jacoco
plugin but at the same time "consume" argLine produced by Jacoco (if jacoco
plugin is part of build)
)
> @{argLine} not replaced if undefined
>
>
> Key: SUREFIRE-1431
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1431
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.21.1
> Environment: Maven 3.5.0
>Reporter: Matthieu Fillon
>Assignee: Tibor Digana
> Attachments: maven.log
>
>
> I need to specify argLine for my tests. I also need it to work with Java
> agent Jacoco when a certain Maven profile is activated.
> So I added `@{argLine}` to my argLine property and it works fine when running
> with Jacoco agent activated.
> When running the tests without profile that activates Jacoco agent, the
> surefire plugin fails with following line (relevant maven logs attached) :
> {color:red}Error: Could not find or load main class @\{argLine} {color}
> I guess @{argLine} is only replaced if an argLine has been defined before by
> another plugin but if not it is not replaced at all.
> Should'nt it be replaced in any case and if none defined, just replace with
> empty value?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (MJLINK-4) NPE on execution
[
https://issues.apache.org/jira/browse/MJLINK-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MJLINK-4:
Description:
When I try to run my maven build I get the following exception:
{noformat}[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink (default-jlink)
on project jloadr-jre: Execution default-jlink of goal
org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.:
NullPointerException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink (default-jlink)
on project jloadr-jre: Execution default-jlink of goal
org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:200)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:196)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:514)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.base/java.lang.Thread.run(Thread.java:844)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
default-jlink of goal
org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 11 more
Caused by: java.lang.NullPointerException
at
org.codehaus.plexus.languages.java.jpms.ResolvePathsRequest$1.toPath(ResolvePathsRequest.java:52)
at
org.codehaus.plexus.languages.java.jpms.ResolvePathsRequest$1.toPath(ResolvePathsRequest.java:48)
at
org.codehaus.plexus.languages.java.jpms.LocationManager.resolvePaths(LocationManager.java:109)
at
org.apache.maven.plugins.jlink.JLinkMojo.preparePaths(JLinkMojo.java:347)
at org.apache.maven.plugins.jlink.JLinkMojo.execute(JLinkMojo.java:264)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
... 12 more{quote}
{noformat}
The cause seems to be that the following code in line 337 in JLinkMojo returns
a collection with only 'null' entries:
{{Collection dependencyArtifacts = getCompileClasspathElements(
getProject() );}}
was:
When I try to run my maven build I get the following exception:
{quote}[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink (default-jlink)
on project jloadr-jre: Execution default-jlink of goal
org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.:
NullPointerException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink (default-jlink)
on project jloadr-jre: Execution default-jlink of goal
org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:200)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:196)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:514)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at
java.base/java.util.concurrent.ThreadPoolExecutor$
[jira] [Commented] (SUREFIRE-1374) std/in stream corrupted error
[
https://issues.apache.org/jira/browse/SUREFIRE-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205090#comment-16205090
]
Tibor Digana commented on SUREFIRE-1374:
[~dan.berindei]
It seems you have different problem.
Can you tell me how could Karaf expect it working in Surefire environment.
Even if we wrapped STDIN, as you said via {{System.setIn()}}, this still would
not solve your problem because Karaf would receive unexpected stream. Our
stream from Surefire plugin.
I think this is conceptual problem with either Karaf or the test. If it is the
test then you should maybe talk with Christial from Karaf about this issue and
somehow come over reading STDIN or mock it on your side in tests with data that
the Karaf or PAX would expect.
> std/in stream corrupted error
> -
>
> Key: SUREFIRE-1374
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1374
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.20
>Reporter: matteo rulli
>Assignee: Tibor Digana
>
> We bumbed surefire version to 2.20 (from 2.19.1) and our tests started
> generating this kind of errors:
> {code}
> # Created on 2017-05-26T10:24:04.032
> [SUREFIRE] std/in stream corrupted
> java.io.IOException: Command BYE_ACK unexpectedly read Void data with length
> 4.
> at
> org.apache.maven.surefire.booter.MasterProcessCommand.decode(MasterProcessCommand.java:130)
> at
> org.apache.maven.surefire.booter.CommandReader$CommandRunnable.run(CommandReader.java:386)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Related stacktrace:
> {code}
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: Error
> occurred in starting fork, check output in log
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:634)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:533)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:279)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:243)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1077)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:907)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:785)
> [ERROR] at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR] at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR] at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> [ERROR] at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> [ERROR] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> [ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> [ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [ERROR] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR] at java.lang.reflect.Method.invoke(Method.java:498)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> [
> {code}
> Everythi
[jira] [Comment Edited] (SUREFIRE-1374) std/in stream corrupted error
[
https://issues.apache.org/jira/browse/SUREFIRE-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205089#comment-16205089
]
Tibor Digana edited comment on SUREFIRE-1374 at 10/15/17 10:42 AM:
---
[~matteor]
Can you attach your POM and Maven debug logs (mvn -X install) in Jira?
Do you use these configuration parameters {{forkedProcessTimeoutInSeconds}} and
{{forkedProcessExitTimeoutInSeconds}}?
Are your tests consuming a lot memory and is the GC period long?
I want to investigate initiator which caused that JVM started {{System.exit}}
between events {{BYE}} and {{BYE_ACK}}.
It could be anything like {{System.exit}}, any ShutdownHooks, timeout.
I am asking this because it is obvious that something sent {{CTRL+C}}.
It could be shutdown hook or CI machine which is more probable to happen.
Does it happen always?
was (Author: tibor17):
[~matteor]
Can you attach your POM and Maven debug logs (mvn -X install) in Jira?
Do you use theseconfiguration parameters {{forkedProcessTimeoutInSeconds}} and
{{forkedProcessExitTimeoutInSeconds}}?
Are your tests consuming a lot memory and is the GC period long?
I want to investigate initiator which caused that JVM started {{System.exit}}
between events {{BYE}} and {{BYE_ACK}}.
It could be anything like {{System.exit}}, any ShutdownHooks, timeout.
I am asking this because it is obvious that something sent {{CTRL+C}}.
It could be shutdown hook or CI machine which is more probable to happen.
Does it happen always?
> std/in stream corrupted error
> -
>
> Key: SUREFIRE-1374
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1374
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.20
>Reporter: matteo rulli
>Assignee: Tibor Digana
>
> We bumbed surefire version to 2.20 (from 2.19.1) and our tests started
> generating this kind of errors:
> {code}
> # Created on 2017-05-26T10:24:04.032
> [SUREFIRE] std/in stream corrupted
> java.io.IOException: Command BYE_ACK unexpectedly read Void data with length
> 4.
> at
> org.apache.maven.surefire.booter.MasterProcessCommand.decode(MasterProcessCommand.java:130)
> at
> org.apache.maven.surefire.booter.CommandReader$CommandRunnable.run(CommandReader.java:386)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Related stacktrace:
> {code}
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: Error
> occurred in starting fork, check output in log
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:634)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:533)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:279)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:243)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1077)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:907)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:785)
> [ERROR] at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR] at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR] at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> [ERROR] at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> [ERROR] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> [ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> [ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> [ERROR] at sun.reflect.NativeMe
[jira] [Commented] (SUREFIRE-1374) std/in stream corrupted error
[
https://issues.apache.org/jira/browse/SUREFIRE-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205089#comment-16205089
]
Tibor Digana commented on SUREFIRE-1374:
[~matteor]
Can you attach your POM and Maven debug logs (mvn -X install) in Jira?
Do you use theseconfiguration parameters {{forkedProcessTimeoutInSeconds}} and
{{forkedProcessExitTimeoutInSeconds}}?
Are your tests consuming a lot memory and is the GC period long?
I want to investigate initiator which caused that JVM started {{System.exit}}
between events {{BYE}} and {{BYE_ACK}}.
It could be anything like {{System.exit}}, any ShutdownHooks, timeout.
I am asking this because it is obvious that something sent {{CTRL+C}}.
It could be shutdown hook or CI machine which is more probable to happen.
Does it happen always?
> std/in stream corrupted error
> -
>
> Key: SUREFIRE-1374
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1374
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.20
>Reporter: matteo rulli
>Assignee: Tibor Digana
>
> We bumbed surefire version to 2.20 (from 2.19.1) and our tests started
> generating this kind of errors:
> {code}
> # Created on 2017-05-26T10:24:04.032
> [SUREFIRE] std/in stream corrupted
> java.io.IOException: Command BYE_ACK unexpectedly read Void data with length
> 4.
> at
> org.apache.maven.surefire.booter.MasterProcessCommand.decode(MasterProcessCommand.java:130)
> at
> org.apache.maven.surefire.booter.CommandReader$CommandRunnable.run(CommandReader.java:386)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Related stacktrace:
> {code}
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: Error
> occurred in starting fork, check output in log
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:634)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:533)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:279)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:243)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1077)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:907)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:785)
> [ERROR] at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR] at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR] at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> [ERROR] at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> [ERROR] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> [ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> [ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [ERROR] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR] at java.lang.reflect.Method.invoke(Method.java:498)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(
[jira] [Comment Edited] (SUREFIRE-1374) std/in stream corrupted error
[
https://issues.apache.org/jira/browse/SUREFIRE-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16204771#comment-16204771
]
Tibor Digana edited comment on SUREFIRE-1374 at 10/15/17 10:16 AM:
---
[~binkley]
Your problem is totally root cause different from [~matteor]'s. The one who can
fix it is you and your dependencies e.g. Spring. See the colors [[34m in the
dump file - find the dependency which does this and switch it off. Simply do
not use Jansi, {{System.setOut()}}, {{FileDescriptor.out}}, nor {{Console}}.
In some later version I want to use TCP sockets instead of native standard
pipes, but there are more important features to do in prior.
was (Author: tibor17):
[~binkley]
Your problem is totally root cause different from [~dan.berindei]'s. The one
who can fix it is you and your dependencies e.g. Spring. See the colors [[34m
in the dump file - find the dependency which does this and switch it off.
Simply do not use Jansi, {{System.setOut()}}, {{FileDescriptor.out}}, nor
{{Console}}.
In some later version I want to use TCP sockets instead of native standard
pipes, but there are more important features to do in prior.
> std/in stream corrupted error
> -
>
> Key: SUREFIRE-1374
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1374
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.20
>Reporter: matteo rulli
>Assignee: Tibor Digana
>
> We bumbed surefire version to 2.20 (from 2.19.1) and our tests started
> generating this kind of errors:
> {code}
> # Created on 2017-05-26T10:24:04.032
> [SUREFIRE] std/in stream corrupted
> java.io.IOException: Command BYE_ACK unexpectedly read Void data with length
> 4.
> at
> org.apache.maven.surefire.booter.MasterProcessCommand.decode(MasterProcessCommand.java:130)
> at
> org.apache.maven.surefire.booter.CommandReader$CommandRunnable.run(CommandReader.java:386)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Related stacktrace:
> {code}
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: Error
> occurred in starting fork, check output in log
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:634)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:533)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:279)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:243)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1077)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:907)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:785)
> [ERROR] at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR] at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR] at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> [ERROR] at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> [ERROR] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> [ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> [ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [ERROR] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR] at java.lang.reflect.Method.invoke(Method.java:498)
> [ERRO
[jira] [Commented] (MNG-6282) Console output has no colors in shell (both Git Bash and Cygwin) [regression in Jansi 1.16 / Maven 3.5.1]
[ https://issues.apache.org/jira/browse/MNG-6282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205076#comment-16205076 ] Hervé Boutemy commented on MNG-6282: workaround from MNG-6242 integrated to make its path to Maven 3.5.2 this issue will track the final fix, done by improving jansi-native Windows isatty() https://github.com/fusesource/jansi-native/issues/11 > Console output has no colors in shell (both Git Bash and Cygwin) [regression > in Jansi 1.16 / Maven 3.5.1] > - > > Key: MNG-6282 > URL: https://issues.apache.org/jira/browse/MNG-6282 > Project: Maven > Issue Type: Bug > Components: Logging >Affects Versions: 3.5.1 >Reporter: Dejan Stojadinović > Labels: regression, windows > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png, > screenshot-4.png, screenshot-5-Cygwin.png, screenshot-6.png, screenshot-7.png > > > See > [screenshot|https://issues.apache.org/jira/secure/attachment/12886398/screenshot-1.png] > for more details. > _*Environment:*_ > * Windows 10, 64 bit > * Oracle Java, version: *1.8.0_144* > * Git Bash shell (MINGW64), Cygwin -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (MNG-6196) Update slf4j and simplify its color integration
[ https://issues.apache.org/jira/browse/MNG-6196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MNG-6196. -- Resolution: Fixed Assignee: Hervé Boutemy > Update slf4j and simplify its color integration > --- > > Key: MNG-6196 > URL: https://issues.apache.org/jira/browse/MNG-6196 > Project: Maven > Issue Type: Improvement > Components: Dependencies >Affects Versions: 3.5.0-beta-1 >Reporter: Sylwester Lachiewicz >Assignee: Hervé Boutemy >Priority: Minor > Fix For: 3.5.2 > > > Update dependences for maven build > Slf4j 1.7.22 -> 1.7.25 ([SLF4J-394|https://jira.qos.ch/browse/SLF4J-394] and > [SLF4J-395|https://jira.qos.ch/browse/SLF4J-395] for > [SLF4J-389|https://jira.qos.ch/browse/SLF4J-389]) > With slf4j update we can simplify maven-slf4j-provider implementation given > [SLF4J-394|https://jira.qos.ch/browse/SLF4J-394] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (MNG-6242) No color for maven on Cygwin
[
https://issues.apache.org/jira/browse/MNG-6242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy closed MNG-6242.
--
Resolution: Fixed
thank you for the great help
> No color for maven on Cygwin
>
>
> Key: MNG-6242
> URL: https://issues.apache.org/jira/browse/MNG-6242
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.5.0
> Environment: Cygwin. For example, my uname currently says:
> CYGWIN_NT-10.0 Beren 2.8.0(0.309/5/3) 2017-04-01 20:47 x86_64 Cygwin
>Reporter: Brian Oxley
>Assignee: Hervé Boutemy
>Priority: Minor
> Fix For: 3.5.2
>
>
> Full description and workaround here:
> https://binkley.blogspot.com/2017/04/maven-color-logging-on-cygwin.html
> In short: the JANSI library used in Maven 3.5.0 does not detect Cygwin, and
> falls back to no color. There is a workaround (Zart Colwing): Add
> {{-Djansi.passthrough=true}} to {{MAVEN_OPTS}}.
> As the mvn script understands Cygwin, it would be helpful to add the
> passthrough flag automatically. (Of course, there may need to be some smarts
> about batch and logging modes, and checking if stdout is a console vs
> pipeline.)
> Apologies: I'm unsure how to issue a PR for the maven repo.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MNG-6196) Update slf4j and simplify its color integration
[ https://issues.apache.org/jira/browse/MNG-6196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205067#comment-16205067 ] Hudson commented on MNG-6196: - SUCCESS: Integrated in Jenkins build maven-3.x #1671 (See [https://builds.apache.org/job/maven-3.x/1671/]) [MNG-6196] updated slf4j to 1.7.25 (hboutemy: [http://git-wip-us.apache.org/repos/asf/?p=maven.git&a=commit&h=eb2db7b28664dbaac6a59a2189c70d92e455dcea]) * (edit) apache-maven/src/conf/logging/simplelogger.properties * (edit) maven-slf4j-provider/src/main/java/org/slf4j/impl/MavenSimpleLogger.java * (edit) pom.xml * (edit) maven-slf4j-provider/src/main/script/patch-slf4j-simple.groovy [MNG-6196] removed remaining Monkey patching, not really necessary (hboutemy: [http://git-wip-us.apache.org/repos/asf/?p=maven.git&a=commit&h=4f530c4f006b8d22da90d968a1d32797280804b9]) * (add) maven-slf4j-provider/src/main/java/org/slf4j/impl/StaticLoggerBinder.java * (delete) maven-slf4j-provider/src/main/script/patch-slf4j-simple.groovy * (edit) maven-slf4j-provider/pom.xml > Update slf4j and simplify its color integration > --- > > Key: MNG-6196 > URL: https://issues.apache.org/jira/browse/MNG-6196 > Project: Maven > Issue Type: Improvement > Components: Dependencies >Affects Versions: 3.5.0-beta-1 >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.5.2 > > > Update dependences for maven build > Slf4j 1.7.22 -> 1.7.25 ([SLF4J-394|https://jira.qos.ch/browse/SLF4J-394] and > [SLF4J-395|https://jira.qos.ch/browse/SLF4J-395] for > [SLF4J-389|https://jira.qos.ch/browse/SLF4J-389]) > With slf4j update we can simplify maven-slf4j-provider implementation given > [SLF4J-394|https://jira.qos.ch/browse/SLF4J-394] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MNG-6242) No color for maven on Cygwin
[
https://issues.apache.org/jira/browse/MNG-6242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205068#comment-16205068
]
Hudson commented on MNG-6242:
-
SUCCESS: Integrated in Jenkins build maven-3.x #1671 (See
[https://builds.apache.org/job/maven-3.x/1671/])
[MNG-6242] detect Cygwin/Mingw pseudo terminal for Jansi (hboutemy:
[http://git-wip-us.apache.org/repos/asf/?p=maven.git&a=commit&h=c19e9dcac3d200094c770521b9b1b10df76f26c4])
* (edit) apache-maven/src/bin/mvn
> No color for maven on Cygwin
>
>
> Key: MNG-6242
> URL: https://issues.apache.org/jira/browse/MNG-6242
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.5.0
> Environment: Cygwin. For example, my uname currently says:
> CYGWIN_NT-10.0 Beren 2.8.0(0.309/5/3) 2017-04-01 20:47 x86_64 Cygwin
>Reporter: Brian Oxley
>Assignee: Hervé Boutemy
>Priority: Minor
> Fix For: 3.5.2
>
>
> Full description and workaround here:
> https://binkley.blogspot.com/2017/04/maven-color-logging-on-cygwin.html
> In short: the JANSI library used in Maven 3.5.0 does not detect Cygwin, and
> falls back to no color. There is a workaround (Zart Colwing): Add
> {{-Djansi.passthrough=true}} to {{MAVEN_OPTS}}.
> As the mvn script understands Cygwin, it would be helpful to add the
> passthrough flag automatically. (Of course, there may need to be some smarts
> about batch and logging modes, and checking if stdout is a console vs
> pipeline.)
> Apologies: I'm unsure how to issue a PR for the maven repo.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (MNG-6242) No color for maven on Cygwin
[
https://issues.apache.org/jira/browse/MNG-6242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MNG-6242:
---
Fix Version/s: (was: 3.5.2-candidate)
3.5.2
> No color for maven on Cygwin
>
>
> Key: MNG-6242
> URL: https://issues.apache.org/jira/browse/MNG-6242
> Project: Maven
> Issue Type: Bug
> Components: Command Line
>Affects Versions: 3.5.0
> Environment: Cygwin. For example, my uname currently says:
> CYGWIN_NT-10.0 Beren 2.8.0(0.309/5/3) 2017-04-01 20:47 x86_64 Cygwin
>Reporter: Brian Oxley
>Assignee: Hervé Boutemy
>Priority: Minor
> Fix For: 3.5.2
>
>
> Full description and workaround here:
> https://binkley.blogspot.com/2017/04/maven-color-logging-on-cygwin.html
> In short: the JANSI library used in Maven 3.5.0 does not detect Cygwin, and
> falls back to no color. There is a workaround (Zart Colwing): Add
> {{-Djansi.passthrough=true}} to {{MAVEN_OPTS}}.
> As the mvn script understands Cygwin, it would be helpful to add the
> passthrough flag automatically. (Of course, there may need to be some smarts
> about batch and logging modes, and checking if stdout is a console vs
> pipeline.)
> Apologies: I'm unsure how to issue a PR for the maven repo.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (MNG-6196) Update slf4j and simplify its color integration
[ https://issues.apache.org/jira/browse/MNG-6196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MNG-6196: --- Fix Version/s: (was: 3.5.2-candidate) 3.5.2 > Update slf4j and simplify its color integration > --- > > Key: MNG-6196 > URL: https://issues.apache.org/jira/browse/MNG-6196 > Project: Maven > Issue Type: Improvement > Components: Dependencies >Affects Versions: 3.5.0-beta-1 >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.5.2 > > > Update dependences for maven build > Slf4j 1.7.22 -> 1.7.25 ([SLF4J-394|https://jira.qos.ch/browse/SLF4J-394] and > [SLF4J-395|https://jira.qos.ch/browse/SLF4J-395] for > [SLF4J-389|https://jira.qos.ch/browse/SLF4J-389]) > With slf4j update we can simplify maven-slf4j-provider implementation given > [SLF4J-394|https://jira.qos.ch/browse/SLF4J-394] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
