[GitHub] [maven-surefire] Tibor17 commented on issue #240: [SUREFIRE-1658] TCP/IP Channel for forked Surefire JVM. Extensions API and SPI. Polymorphism for remote and local process communication.
Tibor17 commented on issue #240: [SUREFIRE-1658] TCP/IP Channel for forked Surefire JVM. Extensions API and SPI. Polymorphism for remote and local process communication. URL: https://github.com/apache/maven-surefire/pull/240#issuecomment-552061820 @rpdai Currently we use `java.nio.channels.AsynchronousServerSocketChannel` but we need to have 2 blocking operations `client.write( bb ).get()` and `client.read( bb ).get()`, and one non-blocking `accept`. The read and write uses another thread in the background. I think using `java.nio.channels.ServerSocketChannel` the number of used threads would be smaller by those two running in the background in JVM. We still need to have another two application threads in both alternatives. So with `AsynchronousServerSocketChannel` there will be 4 threads. And only 2 threads with the `ServerSocketChannel`. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-surefire] Tibor17 commented on issue #240: [SUREFIRE-1658] TCP/IP Channel for forked Surefire JVM. Extensions API and SPI. Polymorphism for remote and local process communication.
Tibor17 commented on issue #240: [SUREFIRE-1658] TCP/IP Channel for forked Surefire JVM. Extensions API and SPI. Polymorphism for remote and local process communication. URL: https://github.com/apache/maven-surefire/pull/240#issuecomment-552056505 @eolivelli @jon-bell @Col-E @rpdai The TCP server is complete. Can you pls make a review? Can you help us with writing the unit test as well? I know it should be written beforehand but we are quite in hurry! This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Comment Edited] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition in pom.xml
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970683#comment-16970683
]
Fan Guogang edited comment on MNG-6397 at 11/9/19 2:02 AM:
---
mirrorOf * is not a good option, for example if you use a hosted repository
server, such as nexus or artifactory, you need to create a group contains all
repositories,that will cause slow performance when resloving dependencies,
because nexus will need to contact all repositories to get metadata.
was (Author: westfamer):
mirrorOf * is not a good option, for example if you use a hosted repository
server, such as nexus or artifactory, you need to create a group contains all
repositories
that will cause slow performance when resloving dependencies, because nexus
will need to contact all repositories to get metadata.
> Maven Transitive Dependency Resolution Does Not Respect Repository Definition
> in pom.xml
>
>
> Key: MNG-6397
> URL: https://issues.apache.org/jira/browse/MNG-6397
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories, Dependencies, POM
>Affects Versions: 3.5.0, 3.5.2, 3.5.3, 3.6.0, 3.6.1
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /usr/local/share/maven
> Java version: 1.8.0_161, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.10.5", arch: "x86_64", family: "mac"
>Reporter: Alan Czajkowski
>Priority: Critical
> Labels: maven
>
> _*Note:* I am trying to do a build behind a firewall which means I cannot
> access the Internet, I can only access my internal Maven repository inside my
> network, so:_
> - _grabbing artifacts from https://artifacts.example.com/repository/maven/
> works fine_
> - _grabbing artifacts from anywhere fails due to firewall restrictions_
> Let's begin:
> My {{pom.xml}} has the following:
> {code:xml}
> ...
>
> ...
>
> org.springframework.boot
> spring-boot-starter-web
> 2.0.0.RELEASE
>
> ...
>
> ...
>
> ...
>
> central
> Public
> https://artifacts.example.com/repository/maven/
>
> true
>
>
> true
>
>
> ...
>
> ...
> {code}
> The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
> {code:java}
> +- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
> | +-
> org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
> | | \-
> com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
> | +-
> org.springframework.boot:spring-boot-starter-tomcat:jar:2.0.0.RELEASE:compile
> | | \- org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.5.28:compile
> | +- org.hibernate.validator:hibernate-validator:jar:6.0.7.Final:compile
> | | +- javax.validation:validation-api:jar:2.0.1.Final:compile
> | | +- org.jboss.logging:jboss-logging:jar:3.3.0.Final:compile
> | | \- com.fasterxml:classmate:jar:1.3.1:compile
> | \- org.springframework:spring-web:jar:5.0.4.RELEASE:compile
> {code}
> How is it that the build fails as such:
> {code:java}
> ...
> Downloading:
> https://repo.spring.io/milestone/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://repo.spring.io/snapshot/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://dl.bintray.com/rabbitmq/maven-milestones/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://repo.maven.apache.org/maven2/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> ...
> [ERROR] Failed to execute goal on project maven-multi-module-demo-backend:
> Could not resolve dependencies for project
> com.example.pipe:maven-multi-module-demo-backend:war:1.0.0-SNAPSHOT: Failed
> to collect dependencies at
> org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE ->
> org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Failed to read
> artifact descriptor for
> org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Could not
> transfer artifact org.jboss.shrinkwrap:shrinkwrap-bom:pom:1.2.3 from/to
> spring-milestone (https://repo.spring.io/milestone): Connection reset ->
> [Help 1]
> ...
> {code}
> when I
[jira] [Commented] (MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition in pom.xml
[
https://issues.apache.org/jira/browse/MNG-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970683#comment-16970683
]
Fan Guogang commented on MNG-6397:
--
mirrorOf * is not a good option, for example if you use a hosted repository
server, such as nexus or artifactory, you need to create a group contains all
repositories
that will cause slow performance when resloving dependencies, because nexus
will need to contact all repositories to get metadata.
> Maven Transitive Dependency Resolution Does Not Respect Repository Definition
> in pom.xml
>
>
> Key: MNG-6397
> URL: https://issues.apache.org/jira/browse/MNG-6397
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories, Dependencies, POM
>Affects Versions: 3.5.0, 3.5.2, 3.5.3, 3.6.0, 3.6.1
> Environment: Apache Maven 3.5.0
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /usr/local/share/maven
> Java version: 1.8.0_161, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.10.5", arch: "x86_64", family: "mac"
>Reporter: Alan Czajkowski
>Priority: Critical
> Labels: maven
>
> _*Note:* I am trying to do a build behind a firewall which means I cannot
> access the Internet, I can only access my internal Maven repository inside my
> network, so:_
> - _grabbing artifacts from https://artifacts.example.com/repository/maven/
> works fine_
> - _grabbing artifacts from anywhere fails due to firewall restrictions_
> Let's begin:
> My {{pom.xml}} has the following:
> {code:xml}
> ...
>
> ...
>
> org.springframework.boot
> spring-boot-starter-web
> 2.0.0.RELEASE
>
> ...
>
> ...
>
> ...
>
> central
> Public
> https://artifacts.example.com/repository/maven/
>
> true
>
>
> true
>
>
> ...
>
> ...
> {code}
> The {{dependency:tree}} for the {{spring-boot-starter-web}} is as follows:
> {code:java}
> +- org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE:compile
> | +-
> org.springframework.boot:spring-boot-starter-json:jar:2.0.0.RELEASE:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jdk8:jar:2.9.4:compile
> | | +-
> com.fasterxml.jackson.datatype:jackson-datatype-jsr310:jar:2.9.4:compile
> | | \-
> com.fasterxml.jackson.module:jackson-module-parameter-names:jar:2.9.4:compile
> | +-
> org.springframework.boot:spring-boot-starter-tomcat:jar:2.0.0.RELEASE:compile
> | | \- org.apache.tomcat.embed:tomcat-embed-websocket:jar:8.5.28:compile
> | +- org.hibernate.validator:hibernate-validator:jar:6.0.7.Final:compile
> | | +- javax.validation:validation-api:jar:2.0.1.Final:compile
> | | +- org.jboss.logging:jboss-logging:jar:3.3.0.Final:compile
> | | \- com.fasterxml:classmate:jar:1.3.1:compile
> | \- org.springframework:spring-web:jar:5.0.4.RELEASE:compile
> {code}
> How is it that the build fails as such:
> {code:java}
> ...
> Downloading:
> https://repo.spring.io/milestone/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://repo.spring.io/snapshot/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://dl.bintray.com/rabbitmq/maven-milestones/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> Downloading:
> https://repo.maven.apache.org/maven2/org/jboss/shrinkwrap/shrinkwrap-bom/1.2.3/shrinkwrap-bom-1.2.3.pom
> ...
> [ERROR] Failed to execute goal on project maven-multi-module-demo-backend:
> Could not resolve dependencies for project
> com.example.pipe:maven-multi-module-demo-backend:war:1.0.0-SNAPSHOT: Failed
> to collect dependencies at
> org.springframework.boot:spring-boot-starter-web:jar:2.0.0.RELEASE ->
> org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Failed to read
> artifact descriptor for
> org.hibernate.validator:hibernate-validator:jar:6.0.7.Final: Could not
> transfer artifact org.jboss.shrinkwrap:shrinkwrap-bom:pom:1.2.3 from/to
> spring-milestone (https://repo.spring.io/milestone): Connection reset ->
> [Help 1]
> ...
> {code}
> when I did not even reference this repo {{spring-milestone
> ([https://repo.spring.io/milestone])}} anywhere in my {{pom.xml}}?
> When you go down the Spring Boot rabbit hole (go into the
> {{spring-boot-starter-web}}'s {{pom.xml}} and then traverse up its parent-pom
> structure a few jumps) you'll eventually get to a parent-pom
> {{spring-boot-dependencies}} with this
[GitHub] [maven] michael-o commented on issue #299: [MNG-6778] - Use https for maven schemaLocations
michael-o commented on issue #299: [MNG-6778] - Use https for maven schemaLocations URL: https://github.com/apache/maven/pull/299#issuecomment-552005796 Please note that parts of this work will be destroyed likely next time when the release plugin is run. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-archetype] rfscholte commented on issue #32: ARCHETYPE-548 Filter files with no extension.
rfscholte commented on issue #32: ARCHETYPE-548 Filter files with no extension. URL: https://github.com/apache/maven-archetype/pull/32#issuecomment-552004185 I would love to see an integration test to see it work, just to confirm we're on the same page. I hope we can solve this by auto-prefixing extensions with a dot, so we don't need a new parameter. But again, a test should confirm this. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-wagon] michael-o commented on issue #60: [WAGON-574] advertise jsoup license for shaded jar
michael-o commented on issue #60: [WAGON-574] advertise jsoup license for shaded jar URL: https://github.com/apache/maven-wagon/pull/60#issuecomment-551985282 @hboutemy First of all, Maven Core does not rely on that. Can you search for method in our code case?! Second, HTTP does not provide any listing of files. The implementation is highly coupled to a 10+ y/o Apache HTTPd mod_userdir output. It was a misconception from the beginning. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (SUREFIRE-1713) Another "The forked VM terminated without..." type of issue
[
https://issues.apache.org/jira/browse/SUREFIRE-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adolfo Cia updated SUREFIRE-1713:
-
Description:
Hi,
I have a recurrent and intermittent error on the same test class of one project
from the company I work for.
It only happens in this test class, so if I annotate with @Disabled, all tests
classes run successfully every time.
Relevant configuration from my pom:
{code:java}
1.8
1.48
5.5.2
org.junit
junit-bom
${junit.version}
pom
import
org.jmockit
jmockit
${jmockit.version}
test
org.junit.jupiter
junit-jupiter-engine
test
org.junit.platform
junit-platform-launcher
test
maven-surefire-plugin
2.22.2
-javaagent:${settings.localRepository}/org/jmockit/jmockit/${jmockit.version}/jmockit-${jmockit.version}.jar
true
{code}
from target/surefire-reports the dump file 2019-11-08T16-58-51_793-jvmRun1.dump
has:
{code:java}
# Created at 2019-11-08T16:58:56.656
Killing self fork JVM. Maven process died.
{code}
and the output from mvn:
{code:java}
[INFO] --- maven-surefire-plugin:2.22.2:test (default-test) @
ltl-java-linehauloperations-ensemble ---
[INFO]
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Running
com.xpo.ltl.linehauloperations.service.ejb.v1.GetImageThumbnailMinuetTest
ERROR StatusLogger No Log4j 2 configuration file found. Using default
configuration (logging only errors to the console), or user programmatically
provided configurations. Set system property 'log4j2.debug' to show Log4j 2
internal initialization logging. See
https://logging.apache.org/log4j/2.x/manual/configuration.html for instructions
on how to configure Log4j 2
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 12.833 s
[INFO] Finished at: 2019-11-08T16:58:56-03:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.22.2:test (default-test) on
project ltl-java-linehauloperations-ensemble: There are test failures.
[ERROR]
[ERROR] Please refer to
C:\liberty_development\workspaces\services\ltl-java-linehauloperations-ensemble\target\surefire-reports
for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date].dump,
[date]-jvmRun[N].dump and [date].dumpstream.
[ERROR] The forked VM terminated without properly saying goodbye. VM crash or
System.exit called?
[ERROR] Command was cmd.exe /X /C
"C:\liberty_development\wlp\java\java\jre\bin\java
-javaagent:C:\Users\adolfo.cia\.m2\repository/org/jmockit/jmockit/1.48/jmockit-1.48.jar
-jar
C:\Users\adolfo.cia\AppData\Local\Temp\surefire6652798836079593172\surefirebooter6928406549506356470.jar
C:\Users\adolfo.cia\AppData\Local\Temp\surefire6652798836079593172
2019-11-08T16-58-51_793-jvmRun1 surefire4400063069909447928tmp
surefire_03777119448075675073tmp"
[ERROR] Error occurred in starting fork, check output in log
[ERROR] Process Exit Code: 1
[ERROR] Crashed tests:
[ERROR]
com.xpo.ltl.linehauloperations.service.ejb.v1.GetImageThumbnailMinuetTest
[ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The
forked VM terminated without properly saying goodbye. VM crash or System.exit
called?
[ERROR] Command was cmd.exe /X /C
"C:\liberty_development\wlp\java\java\jre\bin\java
-javaagent:C:\Users\adolfo.cia\.m2\repository/org/jmockit/jmockit/1.48/jmockit-1.48.jar
-jar
C:\Users\adolfo.cia\AppData\Local\Temp\surefire6652798836079593172\surefirebooter6928406549506356470.jar
C:\Users\adolfo.cia\AppData\Local\Temp\surefire6652798836079593172
2019-11-08T16-58-51_793-jvmRun1 surefire4400063069909447928tmp
surefire_03777119448075675073tmp"
[ERROR] Error occurred in starting fork, check output in log
[ERROR] Process Exit Code: 1
[ERROR] Crashed tests:
[ERROR]
com.xpo.ltl.linehauloperations.service.ejb.v1.GetImageThumbnailMinuetTest
[ERROR] at
[jira] [Updated] (SUREFIRE-1713) Another "The forked VM terminated without..." type of issue
[
https://issues.apache.org/jira/browse/SUREFIRE-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adolfo Cia updated SUREFIRE-1713:
-
Description:
Hi,
I have a recurrent and intermittent error on the same test class of one project
from the company I work for.
It only happens in this test class, so if I annotate with @Disabled, all tests
classes run successfully every time.
Relevant configuration from my pom:
{code:java}
1.8
1.48
5.5.2
org.junit
junit-bom
${junit.version}
pom
import
org.jmockit
jmockit
${jmockit.version}
test
org.junit.jupiter
junit-jupiter-engine
test
org.junit.platform
junit-platform-launcher
test
maven-surefire-plugin
2.22.2
-javaagent:${settings.localRepository}/org/jmockit/jmockit/${jmockit.version}/jmockit-${jmockit.version}.jar
true
{code}
from target/surefire-reports the dump file 2019-11-08T16-58-51_793-jvmRun1.dump
has:
{code:java}
# Created at 2019-11-08T16:58:56.656
Killing self fork JVM. Maven process died.
{code}
and the output from mvn:
{code:java}
[INFO] --- maven-surefire-plugin:2.22.2:test (default-test) @
ltl-java-linehauloperations-ensemble ---
[INFO]
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Running
com.xpo.ltl.linehauloperations.service.ejb.v1.GetImageThumbnailMinuetTest
ERROR StatusLogger No Log4j 2 configuration file found. Using default
configuration (logging only errors to the console), or user programmatically
provided configurations. Set system property 'log4j2.debug' to show Log4j 2
internal initialization logging. See
https://logging.apache.org/log4j/2.x/manual/configuration.html for instructions
on how to configure Log4j 2
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 12.833 s
[INFO] Finished at: 2019-11-08T16:58:56-03:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.22.2:test (default-test) on
project ltl-java-linehauloperations-ensemble: There are test failures.
[ERROR]
[ERROR] Please refer to
C:\liberty_development\workspaces\services\ltl-java-linehauloperations-ensemble\target\surefire-reports
for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date].dump,
[date]-jvmRun[N].dump and [date].dumpstream.
[ERROR] The forked VM terminated without properly saying goodbye. VM crash or
System.exit called?
[ERROR] Command was cmd.exe /X /C
"C:\liberty_development\wlp\java\java\jre\bin\java
-javaagent:C:\Users\adolfo.cia\.m2\repository/org/jmockit/jmockit/1.48/jmockit-1.48.jar
-jar
C:\Users\adolfo.cia\AppData\Local\Temp\surefire6652798836079593172\surefirebooter6928406549506356470.jar
C:\Users\adolfo.cia\AppData\Local\Temp\surefire6652798836079593172
2019-11-08T16-58-51_793-jvmRun1 surefire4400063069909447928tmp
surefire_03777119448075675073tmp"
[ERROR] Error occurred in starting fork, check output in log
[ERROR] Process Exit Code: 1
[ERROR] Crashed tests:
[ERROR]
com.xpo.ltl.linehauloperations.service.ejb.v1.GetImageThumbnailMinuetTest
[ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The
forked VM terminated without properly saying goodbye. VM crash or System.exit
called?
[ERROR] Command was cmd.exe /X /C
"C:\liberty_development\wlp\java\java\jre\bin\java
-javaagent:C:\Users\adolfo.cia\.m2\repository/org/jmockit/jmockit/1.48/jmockit-1.48.jar
-jar
C:\Users\adolfo.cia\AppData\Local\Temp\surefire6652798836079593172\surefirebooter6928406549506356470.jar
C:\Users\adolfo.cia\AppData\Local\Temp\surefire6652798836079593172
2019-11-08T16-58-51_793-jvmRun1 surefire4400063069909447928tmp
surefire_03777119448075675073tmp"
[ERROR] Error occurred in starting fork, check output in log
[ERROR] Process Exit Code: 1
[ERROR] Crashed tests:
[ERROR]
com.xpo.ltl.linehauloperations.service.ejb.v1.GetImageThumbnailMinuetTest
[ERROR] at
[jira] [Updated] (SUREFIRE-1713) Another "The forked VM terminated without..." type of issue
[
https://issues.apache.org/jira/browse/SUREFIRE-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adolfo Cia updated SUREFIRE-1713:
-
Description:
Hi,
I have a recurrent and intermittent error on the same test class of one project
from the company I work for.
It only happens in this test class, so if I annotate with @Disabled, all tests
classes run successfully every time.
Relevant configuration from my pom:
{code:java}
1.8
1.48
5.5.2
org.junit
junit-bom
${junit.version}
pom
import
org.jmockit
jmockit
${jmockit.version}
test
org.junit.jupiter
junit-jupiter-engine
test
org.junit.platform
junit-platform-launcher
test
maven-surefire-plugin
2.22.2
-javaagent:${settings.localRepository}/org/jmockit/jmockit/${jmockit.version}/jmockit-${jmockit.version}.jar
true
{code}
from target/surefire-reports the dump file 2019-11-08T16-58-51_793-jvmRun1.dump
has:
{code:java}
# Created at 2019-11-08T16:58:56.656
Killing self fork JVM. Maven process died.
{code}
and the output from mvn:
{code:java}
[INFO] --- maven-surefire-plugin:2.22.2:test (default-test) @
ltl-java-linehauloperations-ensemble ---
[INFO]
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Running
com.xpo.ltl.linehauloperations.service.ejb.v1.GetImageThumbnailMinuetTest
ERROR StatusLogger No Log4j 2 configuration file found. Using default
configuration (logging only errors to the console), or user programmatically
provided configurations. Set system property 'log4j2.debug' to show Log4j 2
internal initialization logging. See
https://logging.apache.org/log4j/2.x/manual/configuration.html for instructions
on how to configure Log4j 2
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 12.833 s
[INFO] Finished at: 2019-11-08T16:58:56-03:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.22.2:test (default-test) on
project ltl-java-linehauloperations-ensemble: There are test failures.
[ERROR]
[ERROR] Please refer to
C:\liberty_development\workspaces\services\ltl-java-linehauloperations-ensemble\target\surefire-reports
for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date].dump,
[date]-jvmRun[N].dump and [date].dumpstream.
[ERROR] The forked VM terminated without properly saying goodbye. VM crash or
System.exit called?
[ERROR] Command was cmd.exe /X /C
"C:\liberty_development\wlp\java\java\jre\bin\java
-javaagent:C:\Users\adolfo.cia\.m2\repository/org/jmockit/jmockit/1.48/jmockit-1.48.jar
-jar
C:\Users\adolfo.cia\AppData\Local\Temp\surefire6652798836079593172\surefirebooter6928406549506356470.jar
C:\Users\adolfo.cia\AppData\Local\Temp\surefire6652798836079593172
2019-11-08T16-58-51_793-jvmRun1 surefire4400063069909447928tmp
surefire_03777119448075675073tmp"
[ERROR] Error occurred in starting fork, check output in log
[ERROR] Process Exit Code: 1
[ERROR] Crashed tests:
[ERROR]
com.xpo.ltl.linehauloperations.service.ejb.v1.GetImageThumbnailMinuetTest
[ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The
forked VM terminated without properly saying goodbye. VM crash or System.exit
called?
[ERROR] Command was cmd.exe /X /C
"C:\liberty_development\wlp\java\java\jre\bin\java
-javaagent:C:\Users\adolfo.cia\.m2\repository/org/jmockit/jmockit/1.48/jmockit-1.48.jar
-jar
C:\Users\adolfo.cia\AppData\Local\Temp\surefire6652798836079593172\surefirebooter6928406549506356470.jar
C:\Users\adolfo.cia\AppData\Local\Temp\surefire6652798836079593172
2019-11-08T16-58-51_793-jvmRun1 surefire4400063069909447928tmp
surefire_03777119448075675073tmp"
[ERROR] Error occurred in starting fork, check output in log
[ERROR] Process Exit Code: 1
[ERROR] Crashed tests:
[ERROR]
com.xpo.ltl.linehauloperations.service.ejb.v1.GetImageThumbnailMinuetTest
[ERROR] at
[jira] [Updated] (SUREFIRE-1713) Another "The forked VM terminated without..." type of issue
[
https://issues.apache.org/jira/browse/SUREFIRE-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adolfo Cia updated SUREFIRE-1713:
-
Description:
Hi,
I have a recurrent and intermittent error on the same test class of one project
from the company I work for.
It only happens in this test class, so if I annotate with @Disabled, all tests
classes run successfully every time.
Relevant configuration from my pom:
{code:java}
1.8
1.48
5.5.2
org.junit
junit-bom
${junit.version}
pom
import
org.jmockit
jmockit
${jmockit.version}
test
org.junit.jupiter
junit-jupiter-engine
test
org.junit.platform
junit-platform-launcher
test
maven-surefire-plugin
2.22.2
-javaagent:${settings.localRepository}/org/jmockit/jmockit/${jmockit.version}/jmockit-${jmockit.version}.jar
true
{code}
from target/surefire-reports the dump file 2019-11-08T16-58-51_793-jvmRun1.dump
has:
{code:java}
# Created at 2019-11-08T16:58:56.656
Killing self fork JVM. Maven process died.
{code}
and the output from mvn:
{code:java}
[INFO] --- maven-surefire-plugin:2.22.2:test (default-test) @
ltl-java-linehauloperations-ensemble ---
[INFO]
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Running
com.xpo.ltl.linehauloperations.service.ejb.v1.GetImageThumbnailMinuetTest
ERROR StatusLogger No Log4j 2 configuration file found. Using default
configuration (logging only errors to the console), or user programmatically
provided configurations. Set system property 'log4j2.debug' to show Log4j 2
internal initialization logging. See
https://logging.apache.org/log4j/2.x/manual/configuration.html for instructions
on how to configure Log4j 2
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 12.833 s
[INFO] Finished at: 2019-11-08T16:58:56-03:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.22.2:test (default-test) on
project ltl-java-linehauloperations-ensemble: There are test failures.
[ERROR]
[ERROR] Please refer to
C:\liberty_development\workspaces\services\ltl-java-linehauloperations-ensemble\target\surefire-reports
for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date].dump,
[date]-jvmRun[N].dump and [date].dumpstream.
[ERROR] The forked VM terminated without properly saying goodbye. VM crash or
System.exit called?
[ERROR] Command was cmd.exe /X /C
"C:\liberty_development\wlp\java\java\jre\bin\java
-javaagent:C:\Users\adolfo.cia\.m2\repository/org/jmockit/jmockit/1.48/jmockit-1.48.jar
-jar
C:\Users\adolfo.cia\AppData\Local\Temp\surefire6652798836079593172\surefirebooter6928406549506356470.jar
C:\Users\adolfo.cia\AppData\Local\Temp\surefire6652798836079593172
2019-11-08T16-58-51_793-jvmRun1 surefire4400063069909447928tmp
surefire_03777119448075675073tmp"
[ERROR] Error occurred in starting fork, check output in log
[ERROR] Process Exit Code: 1
[ERROR] Crashed tests:
[ERROR]
com.xpo.ltl.linehauloperations.service.ejb.v1.GetImageThumbnailMinuetTest
[ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The
forked VM terminated without properly saying goodbye. VM crash or System.exit
called?
[ERROR] Command was cmd.exe /X /C
"C:\liberty_development\wlp\java\java\jre\bin\java
-javaagent:C:\Users\adolfo.cia\.m2\repository/org/jmockit/jmockit/1.48/jmockit-1.48.jar
-jar
C:\Users\adolfo.cia\AppData\Local\Temp\surefire6652798836079593172\surefirebooter6928406549506356470.jar
C:\Users\adolfo.cia\AppData\Local\Temp\surefire6652798836079593172
2019-11-08T16-58-51_793-jvmRun1 surefire4400063069909447928tmp
surefire_03777119448075675073tmp"
[ERROR] Error occurred in starting fork, check output in log
[ERROR] Process Exit Code: 1
[ERROR] Crashed tests:
[ERROR]
com.xpo.ltl.linehauloperations.service.ejb.v1.GetImageThumbnailMinuetTest
[ERROR] at
[jira] [Created] (SUREFIRE-1713) Another "The forked VM terminated without..." type of issue
Adolfo Cia created SUREFIRE-1713:
Summary: Another "The forked VM terminated without..." type of
issue
Key: SUREFIRE-1713
URL: https://issues.apache.org/jira/browse/SUREFIRE-1713
Project: Maven Surefire
Issue Type: Bug
Components: JUnit 5.x support, Maven Surefire Plugin
Affects Versions: 2.22.2
Environment: Windows 10
Maven 3.6.2
Maven SureFire 2.22.2
JUnit5 5.5.2
Jmockit 1.48
JDK 1.8.0_191
Reporter: Adolfo Cia
Hi,
I have a recurrent and intermittent error on the same test class of one project
from the company I work for.
It only happens in this test class, so if I annotate with @Disabled, all tests
classes run successfully every time.
Relevant configuration from my pom:
{code:java}
1.8
1.48
5.5.2
org.junit
junit-bom
${junit.version}
pom
import
org.jmockit
jmockit
${jmockit.version}
test
org.junit.jupiter
junit-jupiter-engine
test
org.junit.platform
junit-platform-launcher
test
maven-surefire-plugin
2.22.2
-javaagent:${settings.localRepository}/org/jmockit/jmockit/${jmockit.version}/jmockit-${jmockit.version}.jar
true
{code}
from target/surefire-reports the dump file 2019-11-08T16-58-51_793-jvmRun1.dump
has:
{code:java}
# Created at 2019-11-08T16:58:56.656
Killing self fork JVM. Maven process died.
{code}
and the output from mvn:
{code:java}
[INFO] --- maven-surefire-plugin:2.22.2:test (default-test) @
ltl-java-linehauloperations-ensemble ---
[INFO]
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Running
com.xpo.ltl.linehauloperations.service.ejb.v1.GetImageThumbnailMinuetTest
ERROR StatusLogger No Log4j 2 configuration file found. Using default
configuration (logging only errors to the console), or user programmatically
provided configurations. Set system property 'log4j2.debug' to show Log4j 2
internal initialization logging. See
https://logging.apache.org/log4j/2.x/manual/configuration.html for instructions
on how to configure Log4j 2
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 12.833 s
[INFO] Finished at: 2019-11-08T16:58:56-03:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.22.2:test (default-test) on
project ltl-java-linehauloperations-ensemble: There are test failures.
[ERROR]
[ERROR] Please refer to
C:\liberty_development\workspaces\services\ltl-java-linehauloperations-ensemble\target\surefire-reports
for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date].dump,
[date]-jvmRun[N].dump and [date].dumpstream.
[ERROR] The forked VM terminated without properly saying goodbye. VM crash or
System.exit called?
[ERROR] Command was cmd.exe /X /C
"C:\liberty_development\wlp\java\java\jre\bin\java
-javaagent:C:\Users\adolfo.cia\.m2\repository/org/jmockit/jmockit/1.48/jmockit-1.48.jar
-jar
C:\Users\adolfo.cia\AppData\Local\Temp\surefire6652798836079593172\surefirebooter6928406549506356470.jar
C:\Users\adolfo.cia\AppData\Local\Temp\surefire6652798836079593172
2019-11-08T16-58-51_793-jvmRun1 surefire4400063069909447928tmp
surefire_03777119448075675073tmp"
[ERROR] Error occurred in starting fork, check output in log
[ERROR] Process Exit Code: 1
[ERROR] Crashed tests:
[ERROR]
com.xpo.ltl.linehauloperations.service.ejb.v1.GetImageThumbnailMinuetTest
[ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The
forked VM terminated without properly saying goodbye. VM crash or System.exit
called?
[ERROR] Command was cmd.exe /X /C
"C:\liberty_development\wlp\java\java\jre\bin\java
-javaagent:C:\Users\adolfo.cia\.m2\repository/org/jmockit/jmockit/1.48/jmockit-1.48.jar
-jar
C:\Users\adolfo.cia\AppData\Local\Temp\surefire6652798836079593172\surefirebooter6928406549506356470.jar
C:\Users\adolfo.cia\AppData\Local\Temp\surefire6652798836079593172
[jira] [Commented] (MPIR-383) Error when generation site with dependency build with Java 9+
[
https://issues.apache.org/jira/browse/MPIR-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970375#comment-16970375
]
Antoine Tran commented on MPIR-383:
---
Nevermind, it seems this is fixed with
https://issues.apache.org/jira/browse/MPIR-370
(Even if 3.0.0 has some serious regression
https://issues.apache.org/jira/browse/MPIR-373 so we will just use 2.9 and
force update bcel)
> Error when generation site with dependency build with Java 9+
> -
>
> Key: MPIR-383
> URL: https://issues.apache.org/jira/browse/MPIR-383
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 2.9, 3.0.0
>Reporter: Alexander Gängel
>Priority: Minor
>
> When building a site with a dependency to log4j-api greather than {{2.9.1}}
> the used the following error occurs.
> {code:java}
> [INFO] Generating "Dependencies" report ---
> maven-project-info-reports-plugin:2.9:dependencies
> [WARNING] Unable to process class META-INF/versions/9/module-info.class in
> JarAnalyzer File
> /Users/username/.m2/repository/org/apache/logging/log4j/log4j-api/2.11.2/log4j-api-2.11.2.jar
> org.apache.bcel.classfile.ClassFormatException: Invalid byte tag in constant
> pool: 19
> at org.apache.bcel.classfile.Constant.readConstant (Constant.java:161)
> at org.apache.bcel.classfile.ConstantPool. (ConstantPool.java:69)
> at org.apache.bcel.classfile.ClassParser.readConstantPool
> (ClassParser.java:235)
> at org.apache.bcel.classfile.ClassParser.parse (ClassParser.java:143)
> at org.apache.maven.shared.jar.classes.JarClassesAnalysis.analyze
> (JarClassesAnalysis.java:96)
> at
> org.apache.maven.report.projectinfo.dependencies.Dependencies.getJarDependencyDetails
> (Dependencies.java:259)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.hasSealed
> (DependenciesRenderer.java:1542)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyFileDetails
> (DependenciesRenderer.java:545)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:240)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:83)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:201)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:255)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
> (ReportDocumentRenderer.java:230)
> at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
> (DefaultSiteRenderer.java:349)
> at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
> (SiteMojo.java:198)
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:147)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:567)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at
[GitHub] [maven-wagon] eolivelli commented on issue #60: [WAGON-574] advertise jsoup license for shaded jar
eolivelli commented on issue #60: [WAGON-574] advertise jsoup license for shaded jar URL: https://github.com/apache/maven-wagon/pull/60#issuecomment-551892159 > I don't want to have a Maven 3.6.4 release because of some edge case. fair This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-wagon] eolivelli commented on a change in pull request #60: [WAGON-574] advertise jsoup license for shaded jar
eolivelli commented on a change in pull request #60: [WAGON-574] advertise jsoup license for shaded jar URL: https://github.com/apache/maven-wagon/pull/60#discussion_r344237067 ## File path: wagon-providers/wagon-http/pom.xml ## @@ -33,6 +33,19 @@ under the License. Wagon provider that gets and puts artifacts through HTTP(S) using Apache HttpClient-4.x. + + + Apache License, Version 2.0 + https://www.apache.org/licenses/LICENSE-2.0.txt + repo Review comment: Here I would add: shaded jar is bundled with jsoup that it MIT licensed, Copyright (c) 2009-2019 Jonathan Hedley (jonat...@hedley.net), see https://raw.githubusercontent.com/jhy/jsoup/jsoup-1.12.1/LICENSE This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (MPIR-383) Error when generation site with dependency build with Java 9+
[
https://issues.apache.org/jira/browse/MPIR-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970318#comment-16970318
]
Antoine Tran commented on MPIR-383:
---
Hi, just FYI, even if a project use Jdk7, some JAR (like jaxb-api-2.3.0.jar or
log4j-api-2.11.1.jar) uses Java9 Multi-release JAR (there are multiples classes
depending on the Java version). Combined with bytecode instrumentation like
JaCoCo, this makes this error.
If a project need to stay in Java7 and use some Multi-Release JAR, it does not
seem possible. So maybe the solution for this issue is to allow an excludes in
the plugin configuration like this:
{code:java}
org.apache.maven.plugins
maven-project-info-reports-plugin
2.9
META-INF/**
{code}
> Error when generation site with dependency build with Java 9+
> -
>
> Key: MPIR-383
> URL: https://issues.apache.org/jira/browse/MPIR-383
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 2.9, 3.0.0
>Reporter: Alexander Gängel
>Priority: Minor
>
> When building a site with a dependency to log4j-api greather than {{2.9.1}}
> the used the following error occurs.
> {code:java}
> [INFO] Generating "Dependencies" report ---
> maven-project-info-reports-plugin:2.9:dependencies
> [WARNING] Unable to process class META-INF/versions/9/module-info.class in
> JarAnalyzer File
> /Users/username/.m2/repository/org/apache/logging/log4j/log4j-api/2.11.2/log4j-api-2.11.2.jar
> org.apache.bcel.classfile.ClassFormatException: Invalid byte tag in constant
> pool: 19
> at org.apache.bcel.classfile.Constant.readConstant (Constant.java:161)
> at org.apache.bcel.classfile.ConstantPool. (ConstantPool.java:69)
> at org.apache.bcel.classfile.ClassParser.readConstantPool
> (ClassParser.java:235)
> at org.apache.bcel.classfile.ClassParser.parse (ClassParser.java:143)
> at org.apache.maven.shared.jar.classes.JarClassesAnalysis.analyze
> (JarClassesAnalysis.java:96)
> at
> org.apache.maven.report.projectinfo.dependencies.Dependencies.getJarDependencyDetails
> (Dependencies.java:259)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.hasSealed
> (DependenciesRenderer.java:1542)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyFileDetails
> (DependenciesRenderer.java:545)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:240)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:83)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:201)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:255)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
> (ReportDocumentRenderer.java:230)
> at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
> (DefaultSiteRenderer.java:349)
> at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
> (SiteMojo.java:198)
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:147)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at
[GitHub] [maven-wagon] hboutemy edited a comment on issue #60: [WAGON-574] advertise jsoup license for shaded jar
hboutemy edited a comment on issue #60: [WAGON-574] advertise jsoup license for shaded jar URL: https://github.com/apache/maven-wagon/pull/60#issuecomment-551853492 how can you be affirmative that removing jsoup, then the listing feature, won't break any case for Maven or for anybody else? I don't want to have a Maven 3.6.4 release because of some edge case. After some research, the feature was added in WAGON-58 https://issues.apache.org/jira/browse/WAGON-58 last but not least: no feature removal in 3.3.x branch This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-wagon] hboutemy edited a comment on issue #60: [WAGON-574] advertise jsoup license for shaded jar
hboutemy edited a comment on issue #60: [WAGON-574] advertise jsoup license for shaded jar URL: https://github.com/apache/maven-wagon/pull/60#issuecomment-551855817 > This project is not MIT Licensed the shaded jar has multiple licences This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-wagon] hboutemy commented on issue #60: [WAGON-574] advertise jsoup license for shaded jar
hboutemy commented on issue #60: [WAGON-574] advertise jsoup license for shaded jar URL: https://github.com/apache/maven-wagon/pull/60#issuecomment-551855817 > This project is not MIT Licensed the shaded jar has many licences This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (WAGON-574) improve license management when distributing Wagon binaries
[ https://issues.apache.org/jira/browse/WAGON-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated WAGON-574: Affects Version/s: (was: 2.4) 2.5 > improve license management when distributing Wagon binaries > --- > > Key: WAGON-574 > URL: https://issues.apache.org/jira/browse/WAGON-574 > Project: Maven Wagon > Issue Type: New Feature > Components: wagon-http >Affects Versions: 2.5, 3.0.0, 3.3.4 >Reporter: Herve Boutemy >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > as discussed during Wagon 3.3.4 release vote > https://lists.apache.org/thread.html/7526295d1eb080d8d573cfcc2fe4c006c0d948287da7163cc85eadff@%3Cdev.maven.apache.org%3E > , > wagon-http-3.3.4-shaded.jar includes jsoup, which is MIT licensed > this should be advertised -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-wagon] hboutemy edited a comment on issue #60: [WAGON-574] advertise jsoup license for shaded jar
hboutemy edited a comment on issue #60: [WAGON-574] advertise jsoup license for shaded jar URL: https://github.com/apache/maven-wagon/pull/60#issuecomment-551853492 how can you be affirmative that removing jsoup, then the listing feature, won't break any case for Maven or for anybody else? I don't want to have a Maven 3.6.4 release because of some edge case. After some research, the feature was added in WAGON-58 https://issues.apache.org/jira/browse/WAGON-58 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-wagon] hboutemy commented on issue #60: [WAGON-574] advertise jsoup license for shaded jar
hboutemy commented on issue #60: [WAGON-574] advertise jsoup license for shaded jar URL: https://github.com/apache/maven-wagon/pull/60#issuecomment-551853492 how can you be affirmative that removing jsoup won't break any case? I don't want to have a Maven 3.6.4 release because of some edge case the feature was added in WAGON-58 https://issues.apache.org/jira/browse/WAGON-58 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-wagon] hboutemy commented on a change in pull request #60: [WAGON-574] advertise jsoup license for shaded jar
hboutemy commented on a change in pull request #60: [WAGON-574] advertise jsoup license for shaded jar URL: https://github.com/apache/maven-wagon/pull/60#discussion_r344199503 ## File path: wagon-providers/wagon-http/pom.xml ## @@ -33,6 +33,19 @@ under the License. Wagon provider that gets and puts artifacts through HTTP(S) using Apache HttpClient-4.x. + + + Apache License, Version 2.0 + https://www.apache.org/licenses/LICENSE-2.0.txt + repo + + Review comment: Maven defined the format, with following documentation https://maven.apache.org/ref/3.6.2/maven-model/maven.html#class_license if you want to add a comment, just propose a content This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-wagon] eolivelli commented on issue #60: [WAGON-574] advertise jsoup license for shaded jar
eolivelli commented on issue #60: [WAGON-574] advertise jsoup license for shaded jar URL: https://github.com/apache/maven-wagon/pull/60#issuecomment-551846970 @michael-o I missed your mail. Dropping jsoup will be very nice! This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (MNGSITE-372) Profile activation documentation is out of date
[ https://issues.apache.org/jira/browse/MNGSITE-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970223#comment-16970223 ] Hudson commented on MNGSITE-372: Build succeeded in Jenkins: Maven TLP » maven-site » master #131 See https://builds.apache.org/job/maven-box/job/maven-site/job/master/131/ > Profile activation documentation is out of date > --- > > Key: MNGSITE-372 > URL: https://issues.apache.org/jira/browse/MNGSITE-372 > Project: Maven Project Web Site > Issue Type: Bug >Reporter: Gili >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Per > https://issues.apache.org/jira/browse/MNG-4565?focusedCommentId=16844101=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16844101: > http://maven.apache.org/pom.html#Activation needs to be updated to indicate > that *all* activation conditions must be true for a profile to activate. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-wagon] michael-o commented on issue #60: [WAGON-574] advertise jsoup license for shaded jar
michael-o commented on issue #60: [WAGON-574] advertise jsoup license for shaded jar URL: https://github.com/apache/maven-wagon/pull/60#issuecomment-551841799 I'd rather drop JSoup usage because of the reasons I have described on the mailing list. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-dependency-plugin] S4n60w3n commented on issue #24: [MDEP-435] Added xml outputType to dependency tree
S4n60w3n commented on issue #24: [MDEP-435] Added xml outputType to dependency tree URL: https://github.com/apache/maven-dependency-plugin/pull/24#issuecomment-551838009 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-dependency-plugin] S4n60w3n removed a comment on issue #24: [MDEP-435] Added xml outputType to dependency tree
S4n60w3n removed a comment on issue #24: [MDEP-435] Added xml outputType to dependency tree URL: https://github.com/apache/maven-dependency-plugin/pull/24#issuecomment-551837931 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-dependency-plugin] S4n60w3n removed a comment on issue #24: [MDEP-435] Added xml outputType to dependency tree
S4n60w3n removed a comment on issue #24: [MDEP-435] Added xml outputType to dependency tree URL: https://github.com/apache/maven-dependency-plugin/pull/24#issuecomment-551838009 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-dependency-plugin] S4n60w3n commented on issue #24: [MDEP-435] Added xml outputType to dependency tree
S4n60w3n commented on issue #24: [MDEP-435] Added xml outputType to dependency tree URL: https://github.com/apache/maven-dependency-plugin/pull/24#issuecomment-551838194 ``` ``` This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-dependency-plugin] S4n60w3n commented on issue #24: [MDEP-435] Added xml outputType to dependency tree
S4n60w3n commented on issue #24: [MDEP-435] Added xml outputType to dependency tree URL: https://github.com/apache/maven-dependency-plugin/pull/24#issuecomment-551837931 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-wagon] eolivelli commented on a change in pull request #60: [WAGON-574] advertise jsoup license for shaded jar
eolivelli commented on a change in pull request #60: [WAGON-574] advertise jsoup license for shaded jar URL: https://github.com/apache/maven-wagon/pull/60#discussion_r344184546 ## File path: wagon-providers/wagon-http/pom.xml ## @@ -33,6 +33,19 @@ under the License. Wagon provider that gets and puts artifacts through HTTP(S) using Apache HttpClient-4.x. + + + Apache License, Version 2.0 + https://www.apache.org/licenses/LICENSE-2.0.txt + repo + + Review comment: I am not sure about the official meaning of this tag. Usually crawlers read this tag to classify the project. This project is not MIT Licensed and it is not dual licensed. Maybe it is better to add the 'comment' into the primary ALv2.0 license tag This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-dependency-plugin] S4n60w3n commented on issue #24: [MDEP-435] Added xml outputType to dependency tree
S4n60w3n commented on issue #24: [MDEP-435] Added xml outputType to dependency tree URL: https://github.com/apache/maven-dependency-plugin/pull/24#issuecomment-551835309 https://issues.apache.org/jira/browse/MDEP-435 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (MDEP-435) improve mvn dependency:tree - add optional xml output of the results
[ https://issues.apache.org/jira/browse/MDEP-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970216#comment-16970216 ] Bogdan Sikora commented on MDEP-435: https://github.com/apache/maven-dependency-plugin/pull/24 > improve mvn dependency:tree - add optional xml output of the results > > > Key: MDEP-435 > URL: https://issues.apache.org/jira/browse/MDEP-435 > Project: Maven Dependency Plugin > Issue Type: Improvement > Components: tree > Environment: all >Reporter: Kow Unk >Priority: Major > Labels: close-pending > Time Spent: 10m > Remaining Estimate: 0h > > The output of mvn dependency:tree would be more useful to me if it was in a > format that is machine readable. I would like to create some tooling to be > able to easily determine what is causing a particular jar to be included. > for example: > >mymvntool -why org.springframework:org.springframework.beans:3.0.5 > org.springframework.beans-3.0.5 is being *dragged* in by: > my.otherproject.core:1.1 > %end of search > another use: > >mymvntool -makeexclusionfor > >org.springframework:org.springframework.beans:3.0.5 > > >org.springframework >org.springframework.beans > > > or even: > >mymvntool -makeexclusionfor org.springframework:*:3.0.5 > this would pickup all the included jars in the project and build exclusions > for them. > It may have been dumb to pick spring as the exclusion resource, but this is > just an example. having xml output would be valuable to me and probably > others too. > -K -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-dependency-plugin] S4n60w3n opened a new pull request #24: [MDEP-435] Added xml outputType to dependency tree
S4n60w3n opened a new pull request #24: [MDEP-435] Added xml outputType to dependency tree URL: https://github.com/apache/maven-dependency-plugin/pull/24 Following this checklist to help us incorporate your contribution quickly and easily: - [x] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MDEP) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [x] Each commit in the pull request should have a meaningful subject line and body. - [x] Format the pull request title like `[MDEP-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MDEP-XXX` with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message. - [x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [x] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [x] You have run the integration tests successfully (`mvn -Prun-its clean verify`). If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [x] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [x] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [maven-wagon] hboutemy opened a new pull request #60: [WAGON-574] advertise jsoup license for shaded jar
hboutemy opened a new pull request #60: [WAGON-574] advertise jsoup license for shaded jar URL: https://github.com/apache/maven-wagon/pull/60 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (MDEP-435) improve mvn dependency:tree - add optional xml output of the results
[ https://issues.apache.org/jira/browse/MDEP-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970134#comment-16970134 ] Bogdan Sikora commented on MDEP-435: I have created patches in our fork of the repo that add xml output as it was needed for our [repo|https://github.com/webscopeio/license.sh] . I`ll create MR on github with this changes > improve mvn dependency:tree - add optional xml output of the results > > > Key: MDEP-435 > URL: https://issues.apache.org/jira/browse/MDEP-435 > Project: Maven Dependency Plugin > Issue Type: Improvement > Components: tree > Environment: all >Reporter: Kow Unk >Priority: Major > Labels: close-pending > > The output of mvn dependency:tree would be more useful to me if it was in a > format that is machine readable. I would like to create some tooling to be > able to easily determine what is causing a particular jar to be included. > for example: > >mymvntool -why org.springframework:org.springframework.beans:3.0.5 > org.springframework.beans-3.0.5 is being *dragged* in by: > my.otherproject.core:1.1 > %end of search > another use: > >mymvntool -makeexclusionfor > >org.springframework:org.springframework.beans:3.0.5 > > >org.springframework >org.springframework.beans > > > or even: > >mymvntool -makeexclusionfor org.springframework:*:3.0.5 > this would pickup all the included jars in the project and build exclusions > for them. > It may have been dumb to pick spring as the exclusion resource, but this is > just an example. having xml output would be valuable to me and probably > others too. > -K -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNG-6800) 在执行 writePlugin 时 发生 ClassCastException
[
https://issues.apache.org/jira/browse/MNG-6800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969967#comment-16969967
]
Herve Boutemy commented on MNG-6800:
thanks for the explanation: I now better understand
I don't know how Idea precisely does, but I suppose that the Xpp3Dom class is
provided by their classloader, then you should more declare plexus-utils as
provided: can you try and report, please?
> 在执行 writePlugin 时 发生 ClassCastException
>
>
> Key: MNG-6800
> URL: https://issues.apache.org/jira/browse/MNG-6800
> Project: Maven
> Issue Type: Improvement
> Components: Artifacts and Repositories
>Affects Versions: 3.3.9
>Reporter: glmapper
>Priority: Blocker
> Fix For: waiting-for-feedback
>
>
> {code:java}
> //代码占位符
> java.lang.ClassCastException: org.codehaus.plexus.util.xml.Xpp3Dom cannot be
> cast to org.codehaus.plexus.util.xml.Xpp3Domjava.lang.ClassCastException:
> org.codehaus.plexus.util.xml.Xpp3Dom cannot be cast to
> org.codehaus.plexus.util.xml.Xpp3Dom at
> org.apache.maven.model.io.xpp3.MavenXpp3Writer.writePlugin(MavenXpp3Writer.java:1417)
> at
> org.apache.maven.model.io.xpp3.MavenXpp3Writer.writeBuild(MavenXpp3Writer.java:329)
> at
> org.apache.maven.model.io.xpp3.MavenXpp3Writer.writeModel(MavenXpp3Writer.java:1115)
> at
> org.apache.maven.model.io.xpp3.MavenXpp3Writer.write(MavenXpp3Writer.java:100)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (WAGON-567) Provide request retry strategy on transient client and server side errors
[ https://issues.apache.org/jira/browse/WAGON-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969960#comment-16969960 ] Michael Osipov commented on WAGON-567: -- They aren't the best, but the retry handler uses similar names. We wanted to keep it consistent for the users. > Provide request retry strategy on transient client and server side errors > - > > Key: WAGON-567 > URL: https://issues.apache.org/jira/browse/WAGON-567 > Project: Maven Wagon > Issue Type: New Feature > Components: wagon-http >Reporter: xueqian zhang >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.3.4 > > Time Spent: 20m > Remaining Estimate: 0h > > Currently wagon has a retry mechanism when there are connections issues with > repository manager like maven central, artifactory or nexus, see [wagon > source|https://github.com/apache/maven-wagon/blob/dfd22586b6b934aa5a652ca32d57ed26067432fd/wagon-providers/wagon-http-shared/src/main/java/org/apache/maven/wagon/shared/http/AbstractHttpClientWagon.java#L393] > and [httpclient > source|https://github.com/apache/httpcomponents-client/blob/4.5.x/httpclient/src/main/java/org/apache/http/impl/execchain/RetryExec.java#L90], > [httpclient default retry > handler|https://github.com/apache/httpcomponents-client/blob/4.5.x/httpclient/src/main/java/org/apache/http/impl/client/DefaultHttpRequestRetryHandler.java#L154]. > However, it only captures low level connection issues. When the repo > returns errors like 500 or 503, it does not retry. The 5xx response from the > repo might be a blip and maven should retry before giving up. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (WAGON-567) Provide request retry strategy on transient client and server side errors
[ https://issues.apache.org/jira/browse/WAGON-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969958#comment-16969958 ] Herve Boutemy commented on WAGON-567: - thanks for the explanation: now I better understand how these ids came in :) > Provide request retry strategy on transient client and server side errors > - > > Key: WAGON-567 > URL: https://issues.apache.org/jira/browse/WAGON-567 > Project: Maven Wagon > Issue Type: New Feature > Components: wagon-http >Reporter: xueqian zhang >Assignee: Michael Osipov >Priority: Minor > Fix For: 3.3.4 > > Time Spent: 20m > Remaining Estimate: 0h > > Currently wagon has a retry mechanism when there are connections issues with > repository manager like maven central, artifactory or nexus, see [wagon > source|https://github.com/apache/maven-wagon/blob/dfd22586b6b934aa5a652ca32d57ed26067432fd/wagon-providers/wagon-http-shared/src/main/java/org/apache/maven/wagon/shared/http/AbstractHttpClientWagon.java#L393] > and [httpclient > source|https://github.com/apache/httpcomponents-client/blob/4.5.x/httpclient/src/main/java/org/apache/http/impl/execchain/RetryExec.java#L90], > [httpclient default retry > handler|https://github.com/apache/httpcomponents-client/blob/4.5.x/httpclient/src/main/java/org/apache/http/impl/client/DefaultHttpRequestRetryHandler.java#L154]. > However, it only captures low level connection issues. When the repo > returns errors like 500 or 503, it does not retry. The 5xx response from the > repo might be a blip and maven should retry before giving up. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-jdeps-plugin] mihailstoynov commented on issue #4: [MJDEPS-16] jdeps now verifies transitive dependencies
mihailstoynov commented on issue #4: [MJDEPS-16] jdeps now verifies transitive dependencies URL: https://github.com/apache/maven-jdeps-plugin/pull/4#issuecomment-551436764 That's great. We had a lot of fun doing it. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
