[jira] [Commented] (SUREFIRE-1714) Created module "surefire-shared-utils" as a required dependency in "surefire-extensions-api" and "maven-surefire-common"

[Tibor Digana (Jira)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16971005#comment-16971005
 ] 

Tibor Digana commented on SUREFIRE-1714:


https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=9d23be06224c39a8e6c723d628745c4d15c661eb

> Created module "surefire-shared-utils" as a required dependency in 
> "surefire-extensions-api" and "maven-surefire-common"
> 
>
> Key: SUREFIRE-1714
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1714
> Project: Maven Surefire
>  Issue Type: Task
>Reporter: Tibor Digana
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M4
>
>
> We use Maven Shade Plugin to relocate the packages of the artifact 
> maven-shared-utils.
> The problem is that shaded dependency cannot be inherited in the project. 
> Therefore we have to release and deploy it separately. The new 
> module/artifact will be utilized in new version 3.0.0-M5.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Comment Edited] (SUREFIRE-1631) Forked VM terminated without properly saying goodbye with AciveMQ

[Tibor Digana (Jira)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970993#comment-16970993
 ] 

Tibor Digana edited comment on SUREFIRE-1631 at 11/10/19 1:29 AM:
--

[~rockymm]
[~adolfo.cia]
I guess I know where is the problem but you should help me when you run this 
command and show me how it goes on your system (Windows 10). Pickup some PID 
from Task Manager, e.g. 10488:
{{CMD /A /X /C wmic process where (ProcessId=10488) get CreationDate}}


was (Author: tibor17):
[~rockymm]
[~adolfo.cia]
I guess I know where is the problem but you should help when you run this 
command and show me how it goes on your system (Windows 10). Pickup some PID 
from Task Manager, e.g. 10488:
{{CMD /A /X/ /C wmic process where (ProcessId=10488) get CreationDate}}

> Forked VM terminated without properly saying goodbye with AciveMQ
> -
>
> Key: SUREFIRE-1631
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1631
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20.1, 2.22.0, 3.0.0-M2, 3.0.0-M1
>Reporter: Aaron Digulla
>Assignee: Tibor Digana
>Priority: Major
> Attachments: shurefire-shutdownhook-bug-0.0.1.zip
>
>
> I'm seeing spurious "The forked VM terminated without properly saying 
> goodbye. VM crash or System.exit called?" messages when running unit tests in 
> a big multi-module project.
> OS: Windows 10, running Maven 3.5.0 to 3.6.0 and different versions of 
> Surefire (2.20.1 to 3.0.0.-M2), Java 8u171 to 8u191.
> I'm running Maven from the command line using MinTTY (Cygwin).
> Things I tried which have no effect:
>  * Reboot / Cold boot (happens first thing on Monday morning when I come into 
> the office and turn on my PC).
>  * More free memory (happens when I only have a single window open). I have 
> 16GB of RAM.
>  * Different terminal. I tried CMD prompt and urxvt (Cygwin/X).
>  * Different versions of the Surefire plugin or Maven
>  * Different JDK 8 builds
> Things that affect the bug:
>  * Redirecting Maven's stdout to a file: mvn ... | tee mvn.log
>  * Redirecting all log output to a file using logback-test.xml
>  * Running Surefire with forkCount=0
>  * Running a subset of the tests (-Dtest=...)
>  * Pending Windows updates (I think, not sure about this one).
> Counts: I've never seen it with forkCount=0 (~ 20 test builds). I've never 
> seen it with redirecting log output (~ 10 builds). Redirecting sometimes 
> helps but not always.
> One thing which I notice is that one of the tests creates an ActiveMQ broker 
> and uses a shutdown hook to stop it. So I created a small test project which 
> demonstrates that Surefire will sometimes cut off stdout. I think that 
> happens because the main process kills the child after a timeout (correct?).
> So my guess would be that shutdown hooks can mess with the pipeline between 
> the surefire child VM and main Maven process. ActiveMQ might be worse since 
> it stops threads and execution pools (so the output comes slowly with a 
> couple of exceptions sprinkled in when one component loses connection because 
> another is shutting down).
> But now, it gets weird. When the build succeeds, it takes about ~5 minutes to 
> run 1028 tests. The log is 25 MB.
> When it fails, it takes ~8 minutes to run ~700-800 tests (this number varies) 
> and the log stops in the middle of a test but is also 25 MB.
> Some of the time discrepancy is probably because writing to a file is faster 
> than printing on a terminal. The strange part is that the log file is about 
> the same size but 30% of the tests haven't run. Most tests log a lot, do I 
> would expect to see a difference of at least a few MB. The Maven part (which 
> contains escape sequences, etc). is just 60 KB.
> Maybe the parent takes some part of the log output as "child terminated".
> I'm running out of ideas what to try next. I think a way to log the 
> communication between parent and child would help. Also the parent should 
> terminate the child and then read stdout until EOF to we can see anything 
> that happens afterwards.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (SUREFIRE-1631) Forked VM terminated without properly saying goodbye with AciveMQ

[Tibor Digana (Jira)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970993#comment-16970993
 ] 

Tibor Digana commented on SUREFIRE-1631:


[~rockymm]
[~adolfo.cia]
I guess I know where is the problem but you should help when you run this 
command and show me how it goes on your system (Windows 10). Pickup some PID 
from Task Manager, e.g. 10488:
{{CMD /A /X/ /C wmic process where (ProcessId=10488) get CreationDate}}

> Forked VM terminated without properly saying goodbye with AciveMQ
> -
>
> Key: SUREFIRE-1631
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1631
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20.1, 2.22.0, 3.0.0-M2, 3.0.0-M1
>Reporter: Aaron Digulla
>Assignee: Tibor Digana
>Priority: Major
> Attachments: shurefire-shutdownhook-bug-0.0.1.zip
>
>
> I'm seeing spurious "The forked VM terminated without properly saying 
> goodbye. VM crash or System.exit called?" messages when running unit tests in 
> a big multi-module project.
> OS: Windows 10, running Maven 3.5.0 to 3.6.0 and different versions of 
> Surefire (2.20.1 to 3.0.0.-M2), Java 8u171 to 8u191.
> I'm running Maven from the command line using MinTTY (Cygwin).
> Things I tried which have no effect:
>  * Reboot / Cold boot (happens first thing on Monday morning when I come into 
> the office and turn on my PC).
>  * More free memory (happens when I only have a single window open). I have 
> 16GB of RAM.
>  * Different terminal. I tried CMD prompt and urxvt (Cygwin/X).
>  * Different versions of the Surefire plugin or Maven
>  * Different JDK 8 builds
> Things that affect the bug:
>  * Redirecting Maven's stdout to a file: mvn ... | tee mvn.log
>  * Redirecting all log output to a file using logback-test.xml
>  * Running Surefire with forkCount=0
>  * Running a subset of the tests (-Dtest=...)
>  * Pending Windows updates (I think, not sure about this one).
> Counts: I've never seen it with forkCount=0 (~ 20 test builds). I've never 
> seen it with redirecting log output (~ 10 builds). Redirecting sometimes 
> helps but not always.
> One thing which I notice is that one of the tests creates an ActiveMQ broker 
> and uses a shutdown hook to stop it. So I created a small test project which 
> demonstrates that Surefire will sometimes cut off stdout. I think that 
> happens because the main process kills the child after a timeout (correct?).
> So my guess would be that shutdown hooks can mess with the pipeline between 
> the surefire child VM and main Maven process. ActiveMQ might be worse since 
> it stops threads and execution pools (so the output comes slowly with a 
> couple of exceptions sprinkled in when one component loses connection because 
> another is shutting down).
> But now, it gets weird. When the build succeeds, it takes about ~5 minutes to 
> run 1028 tests. The log is 25 MB.
> When it fails, it takes ~8 minutes to run ~700-800 tests (this number varies) 
> and the log stops in the middle of a test but is also 25 MB.
> Some of the time discrepancy is probably because writing to a file is faster 
> than printing on a terminal. The strange part is that the log file is about 
> the same size but 30% of the tests haven't run. Most tests log a lot, do I 
> would expect to see a difference of at least a few MB. The Maven part (which 
> contains escape sequences, etc). is just 60 KB.
> Maybe the parent takes some part of the log output as "child terminated".
> I'm running out of ideas what to try next. I think a way to log the 
> communication between parent and child would help. Also the parent should 
> terminate the child and then read stdout until EOF to we can see anything 
> that happens afterwards.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Closed] (SUREFIRE-1713) Another "The forked VM terminated without..." type of issue

[Tibor Digana (Jira)]

 [ 
https://issues.apache.org/jira/browse/SUREFIRE-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tibor Digana closed SUREFIRE-1713.
--
  Assignee: Tibor Digana
Resolution: Fixed

> 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
>Assignee: Tibor Digana
>Priority: Major
> Attachments: surefire-1713.zip
>
>
> 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] 

[jira] [Closed] (SUREFIRE-1713) Another "The forked VM terminated without..." type of issue

[Tibor Digana (Jira)]

 [ 
https://issues.apache.org/jira/browse/SUREFIRE-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tibor Digana closed SUREFIRE-1713.
--
Resolution: Duplicate

> 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
>Assignee: Tibor Digana
>Priority: Major
> Attachments: surefire-1713.zip
>
>
> 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] 

[jira] [Reopened] (SUREFIRE-1713) Another "The forked VM terminated without..." type of issue

[Tibor Digana (Jira)]

 [ 
https://issues.apache.org/jira/browse/SUREFIRE-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tibor Digana reopened SUREFIRE-1713:


> 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
>Assignee: Tibor Digana
>Priority: Major
> Attachments: surefire-1713.zip
>
>
> 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 

[jira] [Commented] (SUREFIRE-1713) Another "The forked VM terminated without..." type of issue

[Tibor Digana (Jira)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970991#comment-16970991
 ] 

Tibor Digana commented on SUREFIRE-1713:


[~adolfo.cia]
I would like to ask you to try with {{3.0.0-SNAPSHOT}} version.

{code:xml}

  surefire-snapshot
  surefire-snapshot
  https://repository.apache.org/content/repositories/snapshots/
  
true
  
 
...

  

  org.apache.maven.plugins
  maven-surefire-plugin
  3.0.0-SNAPSHOT

  

{code}


You issue is similar to [#SUREFIRE-1631] and I will close it as a duplicate.
Here is my project attached in ZIP. Try to run that one. It contains your POM 
and a trivial test. It passed successfully.


> 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
>Priority: Major
> Attachments: surefire-1713.zip
>
>
> 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 
> 

[jira] [Closed] (SUREFIRE-1712) Running tests with JDK13 fails with Unsupported class file major version 57

[Tibor Digana (Jira)]

 [ 
https://issues.apache.org/jira/browse/SUREFIRE-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tibor Digana closed SUREFIRE-1712.
--
Resolution: Fixed

https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=46cd88c6c92f4fb0cfc75eda7ee8ce6912d0c49a

> Running tests with JDK13 fails with Unsupported class file major version 57
> ---
>
> Key: SUREFIRE-1712
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1712
> Project: Maven Surefire
>  Issue Type: Bug
>Affects Versions: 2.22.2, 3.0.0-M2, 3.0.0-M1, 3.0.0-M3
> Environment: JDK 13+
>Reporter: Karl Heinz Marbaise
>Assignee: Tibor Digana
>Priority: Blocker
> Fix For: 3.0.0-M4
>
>
> I have a example project from [so|https://github.com/khmarbaise/so58710751] 
> the following exception occurs:
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M3:test (default-test) 
> on project oot: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M3:test failed: 
> Unsupported class file major version 57 -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M3:test 
> (default-test) on project oot: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M3:test failed: 
> Unsupported class file major version 57
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:215)
> 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 org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode 
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main 
> (Launcher.java:347)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
> default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M3:test failed: 
> Unsupported class file major version 57
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:148)
> 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 

[jira] [Closed] (SUREFIRE-1714) Created module "surefire-shared-utils" as a required dependency in "surefire-extensions-api" and "maven-surefire-common"

[Tibor Digana (Jira)]

 [ 
https://issues.apache.org/jira/browse/SUREFIRE-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tibor Digana closed SUREFIRE-1714.
--
Resolution: Fixed

https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=7e11fe349c2d6b4d46be4b5a64c9a88e334e36ad

> Created module "surefire-shared-utils" as a required dependency in 
> "surefire-extensions-api" and "maven-surefire-common"
> 
>
> Key: SUREFIRE-1714
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1714
> Project: Maven Surefire
>  Issue Type: Task
>Reporter: Tibor Digana
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M4
>
>
> We use Maven Shade Plugin to relocate the packages of the artifact 
> maven-shared-utils.
> The problem is that shaded dependency cannot be inherited in the project. 
> Therefore we have to release and deploy it separately. The new 
> module/artifact will be utilized in new version 3.0.0-M5.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (SUREFIRE-1714) Created module "surefire-shared-utils" as a required dependency in "surefire-extensions-api" and "maven-surefire-common"

[Tibor Digana (Jira)]

Tibor Digana created SUREFIRE-1714:
--

 Summary: Created module "surefire-shared-utils" as a required 
dependency in "surefire-extensions-api" and "maven-surefire-common"
 Key: SUREFIRE-1714
 URL: https://issues.apache.org/jira/browse/SUREFIRE-1714
 Project: Maven Surefire
  Issue Type: Task
Reporter: Tibor Digana
Assignee: Tibor Digana
 Fix For: 3.0.0-M4


We use Maven Shade Plugin to relocate the packages of the artifact 
maven-shared-utils.
The problem is that shaded dependency cannot be inherited in the project. 
Therefore we have to release and deploy it separately. The new module/artifact 
will be utilized in new version 3.0.0-M5.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (SUREFIRE-1712) Running tests with JDK13 fails with Unsupported class file major version 57

[Tibor Digana (Jira)]

[ 
https://issues.apache.org/jira/browse/SUREFIRE-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970974#comment-16970974
 ] 

Tibor Digana commented on SUREFIRE-1712:


[~khmarbaise]
We have fixed the issues without the need to upgrade the transitive dependency 
ASM, exactly as [~rfscholte] has proposed. This way the next JDK versions will 
work without any upgrade of {{plexus-java}}.

> Running tests with JDK13 fails with Unsupported class file major version 57
> ---
>
> Key: SUREFIRE-1712
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1712
> Project: Maven Surefire
>  Issue Type: Bug
>Affects Versions: 2.22.2, 3.0.0-M2, 3.0.0-M1, 3.0.0-M3
> Environment: JDK 13+
>Reporter: Karl Heinz Marbaise
>Assignee: Tibor Digana
>Priority: Blocker
> Fix For: 3.0.0-M4
>
>
> I have a example project from [so|https://github.com/khmarbaise/so58710751] 
> the following exception occurs:
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M3:test (default-test) 
> on project oot: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M3:test failed: 
> Unsupported class file major version 57 -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M3:test 
> (default-test) on project oot: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M3:test failed: 
> Unsupported class file major version 57
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:215)
> 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 org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode 
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main 
> (Launcher.java:347)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
> default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M3:test failed: 
> Unsupported class file major version 57
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:148)
> 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 

[jira] [Commented] (MJAVADOC-622) javadoc:javadoc fails for a JPMS module

[Robert Scholte (Jira)]

[ 
https://issues.apache.org/jira/browse/MJAVADOC-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970948#comment-16970948
 ] 

Robert Scholte commented on MJAVADOC-622:
-

Just must do it in 1 run: {{mvn compile javadoc:javadoc}} and it works as 
expected

> javadoc:javadoc fails for a JPMS module
> ---
>
> Key: MJAVADOC-622
> URL: https://issues.apache.org/jira/browse/MJAVADOC-622
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: javadoc
>Affects Versions: 3.1.1
>Reporter: Lukas Jungmann
>Priority: Major
> Attachments: jdocbug.zip, options
>
>
> sample project is attached, so to reproduce, either unzip it and run {{mvn 
> javadoc:javadoc}} or follow following steps: 
> - have a simple jar project with a simple class/interface and module-info.java
> - define compiler(3.8.1) and javadoc(3.1.1) plugins
> - set 'release=11' for both
> - on the command line with JDK 11.0.4 run {{mvn javadoc:javadoc}}
> => fails with:
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:3.1.1:javadoc (default-cli) on 
> project jdocbug: An error has occurred in Javadoc report generation:
> [ERROR] Exit code: 1 - error: module not found: org.jdocbug
> [ERROR]
> [ERROR] Command line was: 
> /Library/Java/JavaVirtualMachines/jdk-11.0.4.jdk/Contents/Home/bin/javadoc 
> @options @packages @argfile
> [ERROR]
> [ERROR] Refer to the generated Javadoc files in 
> '/Users/lukas/NetBeansProjects/jdocbug/target/site/apidocs' dir.
> [ERROR]
> {code}
> Expected behaviour is that javadoc for current project is generated in 
> {{target/site/apidocs}} folder.
> looking into options file generated by the plugin:
> - {{patch-module}} option looks strange there
> - either {{source-path}} is missing or {{module-source-path}} points to wrong 
> directory



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [maven-antrun-plugin] shivajithanneeru edited a comment on issue #1: MANTRUN-221 Fails to pass maven properties set in user properties only

[GitBox]

shivajithanneeru edited a comment on issue #1: MANTRUN-221 Fails to pass maven 
properties set in user properties only
URL: https://github.com/apache/maven-antrun-plugin/pull/1#issuecomment-552136751
 
 
   When will the new version of maven-antrun-plugin be released with this patch?


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-antrun-plugin] shivajithanneeru commented on issue #1: MANTRUN-221 Fails to pass maven properties set in user properties only

[GitBox]

shivajithanneeru commented on issue #1: MANTRUN-221 Fails to pass maven 
properties set in user properties only
URL: https://github.com/apache/maven-antrun-plugin/pull/1#issuecomment-552136751
 
 
   When will the version of maven-antrun-plugin be released with this patch?


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] (MJAVADOC-622) javadoc:javadoc fails for a JPMS module

[Jira]

[ 
https://issues.apache.org/jira/browse/MJAVADOC-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970938#comment-16970938
 ] 

Jörg Hohwiller commented on MJAVADOC-622:
-

Can you explain somewhat more please.

I am having the exact same error. MJAVADOC-576 is saying that the problem was 
that code was not compiled before. So I even downloaded `jdocbug.zip` and did:

mvn install

mvn javadoc:javadoc

This gives me the exact error described here. I also have this errors for my 
entire project. JavaDoc is completely unusable for me. This is a kind of 
blocker.

If I am stupid or missing something, please let me know. Otherwise I do not 
consider this as a duplicate.

My Environment:

mvn -v
Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555; 
2019-04-04T21:00:29+02:00)
Maven home: /projects/mmm/software/maven
Java version: 11.0.5, vendor: AdoptOpenJDK, runtime: 
/projects/software/default/java/11.0.5_10/Contents/Home
Default locale: en_DE, platform encoding: UTF-8
OS name: "mac os x", version: "10.14.6", arch: "x86_64", family: "mac"

> javadoc:javadoc fails for a JPMS module
> ---
>
> Key: MJAVADOC-622
> URL: https://issues.apache.org/jira/browse/MJAVADOC-622
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: javadoc
>Affects Versions: 3.1.1
>Reporter: Lukas Jungmann
>Priority: Major
> Attachments: jdocbug.zip, options
>
>
> sample project is attached, so to reproduce, either unzip it and run {{mvn 
> javadoc:javadoc}} or follow following steps: 
> - have a simple jar project with a simple class/interface and module-info.java
> - define compiler(3.8.1) and javadoc(3.1.1) plugins
> - set 'release=11' for both
> - on the command line with JDK 11.0.4 run {{mvn javadoc:javadoc}}
> => fails with:
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:3.1.1:javadoc (default-cli) on 
> project jdocbug: An error has occurred in Javadoc report generation:
> [ERROR] Exit code: 1 - error: module not found: org.jdocbug
> [ERROR]
> [ERROR] Command line was: 
> /Library/Java/JavaVirtualMachines/jdk-11.0.4.jdk/Contents/Home/bin/javadoc 
> @options @packages @argfile
> [ERROR]
> [ERROR] Refer to the generated Javadoc files in 
> '/Users/lukas/NetBeansProjects/jdocbug/target/site/apidocs' dir.
> [ERROR]
> {code}
> Expected behaviour is that javadoc for current project is generated in 
> {{target/site/apidocs}} folder.
> looking into options file generated by the plugin:
> - {{patch-module}} option looks strange there
> - either {{source-path}} is missing or {{module-source-path}} points to wrong 
> directory



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (SUREFIRE-1712) Running tests with JDK13 fails with Unsupported class file major version 57

[Tibor Digana (Jira)]

 [ 
https://issues.apache.org/jira/browse/SUREFIRE-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tibor Digana reassigned SUREFIRE-1712:
--

Assignee: Tibor Digana

> Running tests with JDK13 fails with Unsupported class file major version 57
> ---
>
> Key: SUREFIRE-1712
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1712
> Project: Maven Surefire
>  Issue Type: Bug
>Affects Versions: 2.22.2, 3.0.0-M2, 3.0.0-M1, 3.0.0-M3
> Environment: JDK 13+
>Reporter: Karl Heinz Marbaise
>Assignee: Tibor Digana
>Priority: Blocker
>
> I have a example project from [so|https://github.com/khmarbaise/so58710751] 
> the following exception occurs:
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M3:test (default-test) 
> on project oot: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M3:test failed: 
> Unsupported class file major version 57 -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M3:test 
> (default-test) on project oot: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M3:test failed: 
> Unsupported class file major version 57
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:215)
> 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 org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode 
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main 
> (Launcher.java:347)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
> default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M3:test failed: 
> Unsupported class file major version 57
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:148)
> 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 

[jira] [Updated] (SUREFIRE-1712) Running tests with JDK13 fails with Unsupported class file major version 57

[Tibor Digana (Jira)]

 [ 
https://issues.apache.org/jira/browse/SUREFIRE-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tibor Digana updated SUREFIRE-1712:
---
Fix Version/s: 3.0.0-M4

> Running tests with JDK13 fails with Unsupported class file major version 57
> ---
>
> Key: SUREFIRE-1712
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1712
> Project: Maven Surefire
>  Issue Type: Bug
>Affects Versions: 2.22.2, 3.0.0-M2, 3.0.0-M1, 3.0.0-M3
> Environment: JDK 13+
>Reporter: Karl Heinz Marbaise
>Assignee: Tibor Digana
>Priority: Blocker
> Fix For: 3.0.0-M4
>
>
> I have a example project from [so|https://github.com/khmarbaise/so58710751] 
> the following exception occurs:
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M3:test (default-test) 
> on project oot: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M3:test failed: 
> Unsupported class file major version 57 -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M3:test 
> (default-test) on project oot: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M3:test failed: 
> Unsupported class file major version 57
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:215)
> 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 org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode 
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main 
> (Launcher.java:347)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
> default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M3:test failed: 
> Unsupported class file major version 57
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:148)
> 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)

[jira] [Commented] (MSITE-851) Reproducible Builds: make entries in output jar files reproducible (order + timestamp)

[Hudson (Jira)]

[ 
https://issues.apache.org/jira/browse/MSITE-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970863#comment-16970863
 ] 

Hudson commented on MSITE-851:
--

Build failed in Jenkins: Maven TLP » maven-site-plugin » master #47

See https://builds.apache.org/job/maven-box/job/maven-site-plugin/job/master/47/

> Reproducible Builds: make entries in output jar files reproducible (order + 
> timestamp)
> --
>
> Key: MSITE-851
> URL: https://issues.apache.org/jira/browse/MSITE-851
> Project: Maven Site Plugin
>  Issue Type: New Feature
>  Components: site:jar
>Affects Versions: 3.8.2
>Reporter: Herve Boutemy
>Priority: Major
> Fix For: 3.9.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [maven-antrun-plugin] shivajithanneeru commented on issue #1: MANTRUN-221 Fails to pass maven properties set in user properties only

[GitBox]

shivajithanneeru commented on issue #1: MANTRUN-221 Fails to pass maven 
properties set in user properties only
URL: https://github.com/apache/maven-antrun-plugin/pull/1#issuecomment-552113660
 
 
   Approved your PR.


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] [Closed] (MSITE-851) Reproducible Builds: make entries in output jar files reproducible (order + timestamp)

[Herve Boutemy (Jira)]

 [ 
https://issues.apache.org/jira/browse/MSITE-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Herve Boutemy closed MSITE-851.
---
Resolution: Fixed

done in 
[19be00a9bf2a410abb7132487dc24055060b2c70|https://gitbox.apache.org/repos/asf?p=maven-site-plugin.git=commit=19be00a9bf2a410abb7132487dc24055060b2c70]

> Reproducible Builds: make entries in output jar files reproducible (order + 
> timestamp)
> --
>
> Key: MSITE-851
> URL: https://issues.apache.org/jira/browse/MSITE-851
> Project: Maven Site Plugin
>  Issue Type: New Feature
>  Components: site:jar
>Affects Versions: 3.8.2
>Reporter: Herve Boutemy
>Priority: Major
> Fix For: 3.9.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (MSHADE-333) Shading of sources uses hard-coded classifier "sources"

[Peter De Maeyer (Jira)]

 [ 
https://issues.apache.org/jira/browse/MSHADE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter De Maeyer updated MSHADE-333:
---
Summary: Shading of sources uses hard-coded classifier "sources"  (was: 
Shading sources uses hardcoded classifier "sources")

> Shading of sources uses hard-coded classifier "sources"
> ---
>
> Key: MSHADE-333
> URL: https://issues.apache.org/jira/browse/MSHADE-333
> Project: Maven Shade Plugin
>  Issue Type: Bug
>Affects Versions: 3.2.1
>Reporter: Peter De Maeyer
>Priority: Minor
>
> Shading sources only works for the default classifier "sources".
> The 
> [maven-source-plugin|https://maven.apache.org/plugins/maven-source-plugin/jar-mojo.html]
>  can be configured to use a different classifier with the optional parameter 
> {{}}, but then shading no longer works.
> Ideally, shading of sources should adopt/recognize the classifier(s) of the 
> project(s).
> The root cause is that the classifier "sources" is hard-coded in 
> {{ShadeMojo}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (MSHADE-333) Shading sources uses hardcoded classifier "sources"

[Peter De Maeyer (Jira)]

Peter De Maeyer created MSHADE-333:
--

 Summary: Shading sources uses hardcoded classifier "sources"
 Key: MSHADE-333
 URL: https://issues.apache.org/jira/browse/MSHADE-333
 Project: Maven Shade Plugin
  Issue Type: Bug
Affects Versions: 3.2.1
Reporter: Peter De Maeyer


Shading sources only works for the default classifier "sources".
The 
[maven-source-plugin|https://maven.apache.org/plugins/maven-source-plugin/jar-mojo.html]
 can be configured to use a different classifier with the optional parameter 
{{}}, but then shading no longer works.
Ideally, shading of sources should adopt/recognize the classifier(s) of the 
project(s).

The root cause is that the classifier "sources" is hard-coded in {{ShadeMojo}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (MSHADE-285) It should be possible to shade test sources as a JAR

[Peter De Maeyer (Jira)]

[ 
https://issues.apache.org/jira/browse/MSHADE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970852#comment-16970852
 ] 

Peter De Maeyer commented on MSHADE-285:


Fixed + integration test added, pull request created.
I took the second approach: introduced an optional parameter 
{{createTestSourcesJar}} with similar behavior as {{createSourcesJar}}, but for 
test sources.

> It should be possible to shade test sources as a JAR
> 
>
> Key: MSHADE-285
> URL: https://issues.apache.org/jira/browse/MSHADE-285
> Project: Maven Shade Plugin
>  Issue Type: Improvement
>Affects Versions: 3.1.0
>Reporter: Peter De Maeyer
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> The configuration option {{createSourcesJar}} allows to shade sources JAR, 
> but there is no such option for test sources.
> I see two solutions:
>  # Extend the semantics of {{createSourcesJar}} such that, when combined with 
> {{shadeTestJar}}, is also creates the _test_ sources JAR.
>  # Introduce a new configuration option {{createTestSourcesJar}}, similar to 
> {{createSourcesJar}}.
> The former is very intuitive, but it lacks the flexibility to create a JAR, 
> sources JAR, test JAR, but _no_ test sources JAR. The latter allows more 
> flexibility.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [maven-shade-plugin] peterdemaeyer opened a new pull request #31: [MSHADE-285] - Shade test sources JAR

[GitBox]

peterdemaeyer opened a new pull request #31: [MSHADE-285] - Shade test sources 
JAR
URL: https://github.com/apache/maven-shade-plugin/pull/31
 
 
   Added an optional parameter ``, in alignment with 
``, with a similar purpose for test sources.
   If enabled, this will create a test sources artifact with classifier 
`test-sources` (which is the official classifier for test sources).
   This fix depends on the fix for MSHADE-284, so be sure to merge them in 
order!
- Added an integration test `MSHADE-285_createTestSourcesJar` illustrating 
the new behavior.
- Successfully ran basic tests with `mvn clean verify`.
- Successfully ran integration tests with `mvn -Prun-its clean verify`.
- [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] I have recently signed an [Individual Contributor License 
Agreement](https://www.apache.org/licenses/icla.pdf), but I'm not sure it is 
"linked" correctly to this project.


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] (MANTRUN-221) Fails to pass maven properties set in user properties only

[Alex Szczuczko (Jira)]

[ 
https://issues.apache.org/jira/browse/MANTRUN-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970843#comment-16970843
 ] 

Alex Szczuczko commented on MANTRUN-221:


Pull Request: https://github.com/apache/maven-antrun-plugin/pull/1

> Fails to pass maven properties set in user properties only
> --
>
> Key: MANTRUN-221
> URL: https://issues.apache.org/jira/browse/MANTRUN-221
> Project: Maven Antrun Plugin
>  Issue Type: Bug
>Affects Versions: 1.8
>Reporter: Alex Szczuczko
>Priority: Major
> Attachments: mwe.zip
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> A user of mine [reported a 
> problem|https://github.com/ASzc/jsonpath-maven-plugin/issues/3] between 
> jsonpath-maven-plugin:set-properties and maven-antrun-plugin:run. My analysis 
> points to a bug in maven-antrun-plugin, introduced in version 1.8 by 
> MANTRUN-178. 
> MANTRUN-178 incorrectly assumes in AntRunMojo#copyProperties() that all 
> properties will be present in mavenProject.getProperties(), and so fails to 
> copy properties set at runtime in session.getUserProperties().
> I've attached a MWE, showing maven-help-plugin:evaluate seeing the property 
> set by jsonpath-maven-plugin:set-properties, and maven-antrun-plugin:run 
> failing to see the same property.
> I intend to file a PR to fix this shortly.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [maven-antrun-plugin] ASzc opened a new pull request #1: MANTRUN-221 Fails to pass maven properties set in user properties only

[GitBox]

ASzc opened a new pull request #1: MANTRUN-221 Fails to pass maven properties 
set in user properties only
URL: https://github.com/apache/maven-antrun-plugin/pull/1
 
 
   This resolves a bug introduced by MANTRUN-178, where it incorrectly
   assumes that mavenProject.getProperties() will contain all properties
   present in the session.
   
   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)
   
   


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] [Created] (MANTRUN-221) Fails to pass maven properties set in user properties only

[Alex Szczuczko (Jira)]

Alex Szczuczko created MANTRUN-221:
--

 Summary: Fails to pass maven properties set in user properties only
 Key: MANTRUN-221
 URL: https://issues.apache.org/jira/browse/MANTRUN-221
 Project: Maven Antrun Plugin
  Issue Type: Bug
Affects Versions: 1.8
Reporter: Alex Szczuczko
 Attachments: mwe.zip

A user of mine [reported a 
problem|https://github.com/ASzc/jsonpath-maven-plugin/issues/3] between 
jsonpath-maven-plugin:set-properties and maven-antrun-plugin:run. My analysis 
points to a bug in maven-antrun-plugin, introduced in version 1.8 by 
MANTRUN-178. 

MANTRUN-178 incorrectly assumes in AntRunMojo#copyProperties() that all 
properties will be present in mavenProject.getProperties(), and so fails to 
copy properties set at runtime in session.getUserProperties().

I've attached a MWE, showing maven-help-plugin:evaluate seeing the property set 
by jsonpath-maven-plugin:set-properties, and maven-antrun-plugin:run failing to 
see the same property.

I intend to file a PR to fix this shortly.





--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [maven-javadoc-plugin] eolivelli commented on issue #34: [MJAVADOC-628] - add javadoc.io link pattern when option is …

[GitBox]

eolivelli commented on issue #34: [MJAVADOC-628] - add javadoc.io link pattern 
when  option is …
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/34#issuecomment-552105588
 
 
   We are just waiting for other committers in the community to review this 
patch.
   If noone objects I will move forward.
   I would prefer to have configurable providers.
   Cc @rfscholte
   


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] (MSITE-845) Drop Maven 2 support

[Herve Boutemy (Jira)]

 [ 
https://issues.apache.org/jira/browse/MSITE-845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Herve Boutemy updated MSITE-845:

Fix Version/s: (was: 3.9.0)
   backlog

> Drop Maven 2 support
> 
>
> Key: MSITE-845
> URL: https://issues.apache.org/jira/browse/MSITE-845
> Project: Maven Site Plugin
>  Issue Type: Wish
>Reporter: Tibor Digana
>Assignee: Tibor Digana
>Priority: Major
> Fix For: backlog
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (MSITE-828) Jdk 1.8 required

[Herve Boutemy (Jira)]

 [ 
https://issues.apache.org/jira/browse/MSITE-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Herve Boutemy updated MSITE-828:

Fix Version/s: (was: 3.9.0)
   backlog

> Jdk 1.8 required
> 
>
> Key: MSITE-828
> URL: https://issues.apache.org/jira/browse/MSITE-828
> Project: Maven Site Plugin
>  Issue Type: Task
>Reporter: Olivier Lamy
>Assignee: Olivier Lamy
>Priority: Major
> Fix For: backlog
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (MSITE-829) Upgrade Jetty to 9.4.12

[Herve Boutemy (Jira)]

 [ 
https://issues.apache.org/jira/browse/MSITE-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Herve Boutemy updated MSITE-829:

Fix Version/s: (was: 3.9.0)
   backlog

> Upgrade Jetty to 9.4.12
> ---
>
> Key: MSITE-829
> URL: https://issues.apache.org/jira/browse/MSITE-829
> Project: Maven Site Plugin
>  Issue Type: Dependency upgrade
>Reporter: Olivier Lamy
>Assignee: Olivier Lamy
>Priority: Major
> Fix For: backlog
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (MNG-6778) Use https for schemaLocations

[Hudson (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-6778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970810#comment-16970810
 ] 

Hudson commented on MNG-6778:
-

Build succeeded in Jenkins: Maven TLP » maven » master #302

See https://builds.apache.org/job/maven-box/job/maven/job/master/302/

> Use https for schemaLocations
> -
>
> Key: MNG-6778
> URL: https://issues.apache.org/jira/browse/MNG-6778
> Project: Maven
>  Issue Type: Improvement
>Reporter: Robert Scholte
>Assignee: Robert Scholte
>Priority: Major
>  Labels: up-for-grabs
> Fix For: 3.6.3
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> All poms start with the following roottag:
> {code:xml}
> http://maven.apache.org/POM/4.0.0; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> {code}
> The schemaLocation VALUE should be updated to 
> {{https://maven.apache.org/xsd/maven-4.0.0.xsd}}; the key is just a constant 
> String, even though it looks like a URL, better to keep this the same.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (MPOM-225) add ASF snapshots repository to pluginRepositories

[Hudson (Jira)]

[ 
https://issues.apache.org/jira/browse/MPOM-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970806#comment-16970806
 ] 

Hudson commented on MPOM-225:
-

Build succeeded in Jenkins: Maven TLP » maven-apache-parent » master #22

See 
https://builds.apache.org/job/maven-box/job/maven-apache-parent/job/master/22/

> add ASF snapshots repository to pluginRepositories
> --
>
> Key: MPOM-225
> URL: https://issues.apache.org/jira/browse/MPOM-225
> Project: Maven POMs
>  Issue Type: Wish
>  Components: asf
>Affects Versions: ASF-21
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: ASF-22
>
>
> https://github.com/apache/maven-apache-parent/pull/1



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (MPOM-224) upgrade jar/source/assembly plugins for Reproducible Builds

[Hudson (Jira)]

[ 
https://issues.apache.org/jira/browse/MPOM-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970805#comment-16970805
 ] 

Hudson commented on MPOM-224:
-

Build succeeded in Jenkins: Maven TLP » maven-apache-parent » master #21

See 
https://builds.apache.org/job/maven-box/job/maven-apache-parent/job/master/21/

> upgrade jar/source/assembly plugins for Reproducible Builds
> ---
>
> Key: MPOM-224
> URL: https://issues.apache.org/jira/browse/MPOM-224
> Project: Maven POMs
>  Issue Type: New Feature
>  Components: asf
>Affects Versions: ASF-21
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: ASF-22
>
>
> see https://maven.apache.org/guides/mini/guide-reproducible-builds.html , 3 
> base packaging plugins require to be upgraded to 3.2.0: jar, source and 
> assembly
> by default, ASF parent won't activate the Reproducible Builds feature, just 
> prepare plugins versions: it remains up to each Apache project to activate by 
> adding the {{project.build.outputTimestamp}} property
> Notice: other packaging plugins like ear or war, or site and javadoc are not 
> upgraded, since no Reproducible Builds release is available for now



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (MPOM-221) All Links for Diff produce Forbidden

[Hudson (Jira)]

[ 
https://issues.apache.org/jira/browse/MPOM-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970804#comment-16970804
 ] 

Hudson commented on MPOM-221:
-

Build succeeded in Jenkins: Maven TLP » maven-apache-parent » master #19

See 
https://builds.apache.org/job/maven-box/job/maven-apache-parent/job/master/19/

> All Links for Diff produce Forbidden
> 
>
> Key: MPOM-221
> URL: https://issues.apache.org/jira/browse/MPOM-221
> Project: Maven POMs
>  Issue Type: Bug
>  Components: asf, doxia-tools, maven, maven-archeypes, maven-plugins, 
> maven-shared-components, maven-skins
>Affects Versions: MAVEN-SHARED-22, MAVEN-PLUGINS-28, MAVEN-33, ASF-21
>Reporter: Karl Heinz Marbaise
>Priority: Major
> Fix For: MAVEN-SKINS-10, MAVEN-PLUGINS-27, MAVEN-PLUGINS-28, 
> MAVEN-34, ASF-22
>
>
> Currently all links to diffs on the pages like 
> http://maven.apache.org/pom/asf/, http://maven.apache.org/pom/maven/ will 
> produce:
> {code}
> Forbidden
> You don't have permission to access /repos/asf on this server.
> {code}
> So we need to change all of the diff links to diff links on GitHub



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (MPOM-207) Upgrade maven-compiler-plugin to version 3.8.1

[Hudson (Jira)]

[ 
https://issues.apache.org/jira/browse/MPOM-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970803#comment-16970803
 ] 

Hudson commented on MPOM-207:
-

Build succeeded in Jenkins: Maven TLP » maven-apache-parent » master #20

See 
https://builds.apache.org/job/maven-box/job/maven-apache-parent/job/master/20/

> Upgrade maven-compiler-plugin to version 3.8.1
> --
>
> Key: MPOM-207
> URL: https://issues.apache.org/jira/browse/MPOM-207
> Project: Maven POMs
>  Issue Type: Dependency upgrade
>  Components: maven
>Affects Versions: MAVEN-33, ASF-21
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: ASF-22
>
>
> Release Notes - Maven Compiler Plugin - Version 3.8.0
> h3.  Bug
>  * MCOMPILER-311 - NPE when --patch-module is used
>  * MCOMPILER-321 - Problematic Java 9 modules are silently ignored
>  * MCOMPILER-332 - Java 10 not supported
>  * MCOMPILER-338 - Build Issue based on MCOMPILER-192 IT
>  * MCOMPILER-342 - Unsupported class file major version 55
>  * MCOMPILER-343 - Tests fail to compile in modularized project due to wrong 
> module descriptor path being passed to plexus-java
> h3. Improvement
>  * MCOMPILER-313 - Support mrjar dependency with module descriptor only in 
> META-INF/versions/x
>  * MCOMPILER-323 - Support multi-release jars
>  * MCOMPILER-335 - Update default source/target from 1.5 to 1.6
>  * MCOMPILER-341 - Compile module-info.java files located in test sources
> h3. Task
>  * MCOMPILER-336 - Dependency that should be on modulepath sometime put on 
> classpath
>  * MCOMPILER-344 - Deprecate  flag
>  * MCOMPILER-350 - Add GitHub Documentation
> h3. Dependency upgrade
>  * MCOMPILER-324 - Upgrade parent to 31
>  * MCOMPILER-351 - Upgrade maven-plugins parent to version 32
>  * MCOMPILER-352 - Upgrade maven-shared-utils to 3.2.1
>  * MCOMPILER-353 - Upgrade plexus-compiler to 2.8.4



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Closed] (MPOM-224) upgrade jar/source/assembly plugins for Reproducible Builds

[Herve Boutemy (Jira)]

 [ 
https://issues.apache.org/jira/browse/MPOM-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Herve Boutemy closed MPOM-224.
--
Resolution: Fixed

done in 
[1224eb41f4dcf1abe5bb8b78863e2af12c987b50|https://gitbox.apache.org/repos/asf?p=maven-apache-parent.git;a=commit;h=1224eb41f4dcf1abe5bb8b78863e2af12c987b50]

> upgrade jar/source/assembly plugins for Reproducible Builds
> ---
>
> Key: MPOM-224
> URL: https://issues.apache.org/jira/browse/MPOM-224
> Project: Maven POMs
>  Issue Type: New Feature
>  Components: asf
>Affects Versions: ASF-21
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: ASF-22
>
>
> see https://maven.apache.org/guides/mini/guide-reproducible-builds.html , 3 
> base packaging plugins require to be upgraded to 3.2.0: jar, source and 
> assembly
> by default, ASF parent won't activate the Reproducible Builds feature, just 
> prepare plugins versions: it remains up to each Apache project to activate by 
> adding the {{project.build.outputTimestamp}} property
> Notice: other packaging plugins like ear or war, or site and javadoc are not 
> upgraded, since no Reproducible Builds release is available for now



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Closed] (MPOM-225) add ASF snapshots repository to pluginRepositories

[Herve Boutemy (Jira)]

 [ 
https://issues.apache.org/jira/browse/MPOM-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Herve Boutemy closed MPOM-225.
--
Resolution: Fixed

done in 
[408fac26930f781e3ef1445ce3313b56ad38212a|https://gitbox.apache.org/repos/asf?p=maven-apache-parent.git;a=commit;h=408fac26930f781e3ef1445ce3313b56ad38212a]

> add ASF snapshots repository to pluginRepositories
> --
>
> Key: MPOM-225
> URL: https://issues.apache.org/jira/browse/MPOM-225
> Project: Maven POMs
>  Issue Type: Wish
>  Components: asf
>Affects Versions: ASF-21
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: ASF-22
>
>
> https://github.com/apache/maven-apache-parent/pull/1



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Closed] (MPOM-207) Upgrade maven-compiler-plugin to version 3.8.1

[Herve Boutemy (Jira)]

 [ 
https://issues.apache.org/jira/browse/MPOM-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Herve Boutemy closed MPOM-207.
--
Resolution: Fixed

done in 
[b3e55ebbd1f5dc81140243d17379423563eb6767|https://gitbox.apache.org/repos/asf?p=maven-apache-parent.git;a=commit;h=b3e55ebbd1f5dc81140243d17379423563eb6767]

> Upgrade maven-compiler-plugin to version 3.8.1
> --
>
> Key: MPOM-207
> URL: https://issues.apache.org/jira/browse/MPOM-207
> Project: Maven POMs
>  Issue Type: Dependency upgrade
>  Components: maven
>Affects Versions: MAVEN-33, ASF-21
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: ASF-22
>
>
> Release Notes - Maven Compiler Plugin - Version 3.8.0
> h3.  Bug
>  * MCOMPILER-311 - NPE when --patch-module is used
>  * MCOMPILER-321 - Problematic Java 9 modules are silently ignored
>  * MCOMPILER-332 - Java 10 not supported
>  * MCOMPILER-338 - Build Issue based on MCOMPILER-192 IT
>  * MCOMPILER-342 - Unsupported class file major version 55
>  * MCOMPILER-343 - Tests fail to compile in modularized project due to wrong 
> module descriptor path being passed to plexus-java
> h3. Improvement
>  * MCOMPILER-313 - Support mrjar dependency with module descriptor only in 
> META-INF/versions/x
>  * MCOMPILER-323 - Support multi-release jars
>  * MCOMPILER-335 - Update default source/target from 1.5 to 1.6
>  * MCOMPILER-341 - Compile module-info.java files located in test sources
> h3. Task
>  * MCOMPILER-336 - Dependency that should be on modulepath sometime put on 
> classpath
>  * MCOMPILER-344 - Deprecate  flag
>  * MCOMPILER-350 - Add GitHub Documentation
> h3. Dependency upgrade
>  * MCOMPILER-324 - Upgrade parent to 31
>  * MCOMPILER-351 - Upgrade maven-plugins parent to version 32
>  * MCOMPILER-352 - Upgrade maven-shared-utils to 3.2.1
>  * MCOMPILER-353 - Upgrade plexus-compiler to 2.8.4



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [maven-apache-parent] hboutemy closed pull request #2: Update maven-compiler-plugin to 3.8.0

[GitBox]

hboutemy closed pull request #2: Update maven-compiler-plugin to 3.8.0
URL: https://github.com/apache/maven-apache-parent/pull/2
 
 
   


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-apache-parent] hboutemy commented on issue #2: Update maven-compiler-plugin to 3.8.0

[GitBox]

hboutemy commented on issue #2: Update maven-compiler-plugin to 3.8.0
URL: https://github.com/apache/maven-apache-parent/pull/2#issuecomment-552102398
 
 
   upgrade done in b3e55ebbd1f5dc81140243d17379423563eb6767


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-apache-parent] hboutemy merged pull request #4: Minor grammar edits

[GitBox]

hboutemy merged pull request #4: Minor grammar edits
URL: https://github.com/apache/maven-apache-parent/pull/4
 
 
   


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-apache-parent] hboutemy commented on issue #1: Add pluginRepositories section for SNAPSHOTs

[GitBox]

hboutemy commented on issue #1: Add pluginRepositories section for SNAPSHOTs
URL: https://github.com/apache/maven-apache-parent/pull/1#issuecomment-552102045
 
 
   merged in 408fac26930f781e3ef1445ce3313b56ad38212a with 
https://issues.apache.org/jira/browse/MPOM-225


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-apache-parent] hboutemy closed pull request #1: Add pluginRepositories section for SNAPSHOTs

[GitBox]

hboutemy closed pull request #1: Add pluginRepositories section for SNAPSHOTs
URL: https://github.com/apache/maven-apache-parent/pull/1
 
 
   


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] [Created] (MPOM-225) add ASF snapshots repository to pluginRepositories

[Herve Boutemy (Jira)]

Herve Boutemy created MPOM-225:
--

 Summary: add ASF snapshots repository to pluginRepositories
 Key: MPOM-225
 URL: https://issues.apache.org/jira/browse/MPOM-225
 Project: Maven POMs
  Issue Type: Wish
  Components: asf
Affects Versions: ASF-21
Reporter: Herve Boutemy
Assignee: Herve Boutemy
 Fix For: ASF-22


https://github.com/apache/maven-apache-parent/pull/1



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (MPOM-224) upgrade jar/source/assembly plugins for Reproducible Builds

[Herve Boutemy (Jira)]

 [ 
https://issues.apache.org/jira/browse/MPOM-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Herve Boutemy updated MPOM-224:
---
Summary: upgrade jar/source/assembly plugins for Reproducible Builds  (was: 
upgrade plugins for Reproducible Builds)

> upgrade jar/source/assembly plugins for Reproducible Builds
> ---
>
> Key: MPOM-224
> URL: https://issues.apache.org/jira/browse/MPOM-224
> Project: Maven POMs
>  Issue Type: New Feature
>  Components: asf
>Affects Versions: ASF-21
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: ASF-22
>
>
> see https://maven.apache.org/guides/mini/guide-reproducible-builds.html , 3 
> base packaging plugins require to be upgraded to 3.2.0: jar, source and 
> assembly
> by default, ASF parent won't activate the Reproducible Builds feature, just 
> prepare plugins versions: it remains up to each Apache project to activate by 
> adding the {{project.build.outputTimestamp}} property
> Notice: other packaging plugins like ear or war, or site and javadoc are not 
> upgraded, since no Reproducible Builds release is available for now



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (MPOM-224) upgrade plugins for Reproducible Builds

[Herve Boutemy (Jira)]

 [ 
https://issues.apache.org/jira/browse/MPOM-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Herve Boutemy updated MPOM-224:
---
Description: 
see https://maven.apache.org/guides/mini/guide-reproducible-builds.html , 3 
base packaging plugins require to be upgraded to 3.2.0: jar, source and assembly

by default, ASF parent won't activate the Reproducible Builds feature, just 
prepare plugins versions: it remains up to each Apache project to activate by 
adding the {{project.build.outputTimestamp}} property

Notice: other packaging plugins like ear or war, or site and javadoc are not 
upgraded, since no Reproducible Builds release is available for now

  was:
see https://maven.apache.org/guides/mini/guide-reproducible-builds.html , 3 
packaging plugins require to be upgraded to 3.2.0

by default, ASF parent won't activate the Reproducible Builds feature, just 
prepare plugins versions: it remains up to each Apache project to activate by 
adding the {{project.build.outputTimestamp}} property


> upgrade plugins for Reproducible Builds
> ---
>
> Key: MPOM-224
> URL: https://issues.apache.org/jira/browse/MPOM-224
> Project: Maven POMs
>  Issue Type: New Feature
>  Components: asf
>Affects Versions: ASF-21
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: ASF-22
>
>
> see https://maven.apache.org/guides/mini/guide-reproducible-builds.html , 3 
> base packaging plugins require to be upgraded to 3.2.0: jar, source and 
> assembly
> by default, ASF parent won't activate the Reproducible Builds feature, just 
> prepare plugins versions: it remains up to each Apache project to activate by 
> adding the {{project.build.outputTimestamp}} property
> Notice: other packaging plugins like ear or war, or site and javadoc are not 
> upgraded, since no Reproducible Builds release is available for now



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (MPOM-224) upgrade plugins for Reproducible Builds

[Herve Boutemy (Jira)]

Herve Boutemy created MPOM-224:
--

 Summary: upgrade plugins for Reproducible Builds
 Key: MPOM-224
 URL: https://issues.apache.org/jira/browse/MPOM-224
 Project: Maven POMs
  Issue Type: New Feature
  Components: asf
Affects Versions: ASF-21
Reporter: Herve Boutemy
Assignee: Herve Boutemy
 Fix For: ASF-22


see https://maven.apache.org/guides/mini/guide-reproducible-builds.html , 3 
packaging plugins require to be upgraded to 3.2.0

by default, ASF parent won't activate the Reproducible Builds feature, just 
prepare plugins versions: it remains up to each Apache project to activate by 
adding the {{project.build.outputTimestamp}} property



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (MPOM-207) Upgrade maven-compiler-plugin to version 3.8.1

[Herve Boutemy (Jira)]

 [ 
https://issues.apache.org/jira/browse/MPOM-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Herve Boutemy updated MPOM-207:
---
Summary: Upgrade maven-compiler-plugin to version 3.8.1  (was: Upgrade 
maven-compiler-plugin to version 3.8.0)

> Upgrade maven-compiler-plugin to version 3.8.1
> --
>
> Key: MPOM-207
> URL: https://issues.apache.org/jira/browse/MPOM-207
> Project: Maven POMs
>  Issue Type: Dependency upgrade
>  Components: maven
>Affects Versions: MAVEN-33, ASF-21
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: ASF-22
>
>
> Release Notes - Maven Compiler Plugin - Version 3.8.0
> h3.  Bug
>  * MCOMPILER-311 - NPE when --patch-module is used
>  * MCOMPILER-321 - Problematic Java 9 modules are silently ignored
>  * MCOMPILER-332 - Java 10 not supported
>  * MCOMPILER-338 - Build Issue based on MCOMPILER-192 IT
>  * MCOMPILER-342 - Unsupported class file major version 55
>  * MCOMPILER-343 - Tests fail to compile in modularized project due to wrong 
> module descriptor path being passed to plexus-java
> h3. Improvement
>  * MCOMPILER-313 - Support mrjar dependency with module descriptor only in 
> META-INF/versions/x
>  * MCOMPILER-323 - Support multi-release jars
>  * MCOMPILER-335 - Update default source/target from 1.5 to 1.6
>  * MCOMPILER-341 - Compile module-info.java files located in test sources
> h3. Task
>  * MCOMPILER-336 - Dependency that should be on modulepath sometime put on 
> classpath
>  * MCOMPILER-344 - Deprecate  flag
>  * MCOMPILER-350 - Add GitHub Documentation
> h3. Dependency upgrade
>  * MCOMPILER-324 - Upgrade parent to 31
>  * MCOMPILER-351 - Upgrade maven-plugins parent to version 32
>  * MCOMPILER-352 - Upgrade maven-shared-utils to 3.2.1
>  * MCOMPILER-353 - Upgrade plexus-compiler to 2.8.4



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [maven-javadoc-plugin] maxcellent commented on issue #34: [MJAVADOC-628] - add javadoc.io link pattern when option is …

[GitBox]

maxcellent commented on issue #34: [MJAVADOC-628] - add javadoc.io link pattern 
when  option is …
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/34#issuecomment-552099768
 
 
   sure. With regards to 
   
   > I would like to know the option of other people
   
   anything needs to be done from my side? or we will just wait until you get 
back to us?


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-javadoc-plugin] maxcellent edited a comment on issue #34: [MJAVADOC-628] - add javadoc.io link pattern when option is …

[GitBox]

maxcellent edited a comment on issue #34: [MJAVADOC-628] - add javadoc.io link 
pattern when  option is …
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/34#issuecomment-552099768
 
 
   sure. With regards to 
   
   > I would like to know the option of other people
   
   anything needs to be done from my side? or we will just wait until you get 
back?


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] (MPOM-134) Add profile to use a different resource bundle for incubator projects

[Herve Boutemy (Jira)]

 [ 
https://issues.apache.org/jira/browse/MPOM-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Herve Boutemy updated MPOM-134:
---
Fix Version/s: (was: ASF-22)
   ASF-23

> Add profile to use a different resource bundle for incubator projects
> -
>
> Key: MPOM-134
> URL: https://issues.apache.org/jira/browse/MPOM-134
> Project: Maven POMs
>  Issue Type: Improvement
>Affects Versions: ASF-18
>Reporter: Christopher Tubbs
>Priority: Major
> Fix For: ASF-23
>
>
> The {{org.apache:apache-jar-resource-bundle:1.4}} resourceBundle currently 
> specified in the parent POM does not handle the DISCLAIMER file for incubator 
> projects.
> It would be nice if there were an incubation profile, which could be 
> activated for incubating projects, to use an incubating resource bundle which 
> did handle this DISCLAIMER file.
> This could be done in several ways:
> # An optional second execution of the {{maven-remote-resources-plugin}} could 
> run when the profile is activated, which handles a second resource bundle for 
> the DISCLAIMER file.
> # The current resourceBundle could be turned into a property, which is 
> overridden when the profile is activated, using a resourceBundle which 
> handles everything the current one does, plus the DISCLAIMER file.
> # The current {{maven-remote-resources-plugin}} execution could have the 
> {{}} element changed to {{ combine.children="append">}}, and the profile could specify an additional 
> {{}} to handle the DISCLAIMER file, for the same execution id 
> of {{maven-remote-resources-plugin}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (MPOM-168) JDK 9 requires updates to plugins

[Herve Boutemy (Jira)]

 [ 
https://issues.apache.org/jira/browse/MPOM-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Herve Boutemy updated MPOM-168:
---
Fix Version/s: ASF-23

> JDK 9 requires updates to plugins
> -
>
> Key: MPOM-168
> URL: https://issues.apache.org/jira/browse/MPOM-168
> Project: Maven POMs
>  Issue Type: Improvement
>  Components: asf
>Affects Versions: ASF-19
>Reporter: Karl Heinz Marbaise
>Priority: Minor
> Fix For: ASF-23
>
>
> The following plugins needed to be updated to work with JDK 9:
> * The maven-enforcer-plugin should be updated to final 3.0.0 release to make 
> the pom working with JDK 9...
> * maven-shade-plugin should be upgraded to 3.0.0



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (MPOM-168) JDK 9 requires updates to plugins

[Herve Boutemy (Jira)]

 [ 
https://issues.apache.org/jira/browse/MPOM-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Herve Boutemy updated MPOM-168:
---
Fix Version/s: (was: ASF-22)

> JDK 9 requires updates to plugins
> -
>
> Key: MPOM-168
> URL: https://issues.apache.org/jira/browse/MPOM-168
> Project: Maven POMs
>  Issue Type: Improvement
>  Components: asf
>Affects Versions: ASF-19
>Reporter: Karl Heinz Marbaise
>Priority: Minor
>
> The following plugins needed to be updated to work with JDK 9:
> * The maven-enforcer-plugin should be updated to final 3.0.0 release to make 
> the pom working with JDK 9...
> * maven-shade-plugin should be upgraded to 3.0.0



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (MPOM-208) upgrade m-scm-publish-p

[Herve Boutemy (Jira)]

 [ 
https://issues.apache.org/jira/browse/MPOM-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Herve Boutemy updated MPOM-208:
---
Fix Version/s: (was: ASF-22)
   ASF-23

> upgrade m-scm-publish-p
> ---
>
> Key: MPOM-208
> URL: https://issues.apache.org/jira/browse/MPOM-208
> Project: Maven POMs
>  Issue Type: Dependency upgrade
>  Components: asf
>Affects Versions: ASF-21
>Reporter: Herve Boutemy
>Priority: Major
> Fix For: ASF-23
>
>
> to benefit from MSCMPUB-37 (important when you publish site documentation 
> from Linux) that benefits in fact from SCM-763
> if m-scm-publish-p is not yet release and we want to release ASF parent POM, 
> just adding an upgraded dependency on maven-scm-provider-svnexe can do the 
> job (I tested)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (MNG-6778) Use https for schemaLocations

[Hudson (Jira)]

[ 
https://issues.apache.org/jira/browse/MNG-6778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970785#comment-16970785
 ] 

Hudson commented on MNG-6778:
-

Build succeeded in Jenkins: Maven TLP » maven » master #301

See https://builds.apache.org/job/maven-box/job/maven/job/master/301/

> Use https for schemaLocations
> -
>
> Key: MNG-6778
> URL: https://issues.apache.org/jira/browse/MNG-6778
> Project: Maven
>  Issue Type: Improvement
>Reporter: Robert Scholte
>Assignee: Robert Scholte
>Priority: Major
>  Labels: up-for-grabs
> Fix For: 3.6.3
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> All poms start with the following roottag:
> {code:xml}
> http://maven.apache.org/POM/4.0.0; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> {code}
> The schemaLocation VALUE should be updated to 
> {{https://maven.apache.org/xsd/maven-4.0.0.xsd}}; the key is just a constant 
> String, even though it looks like a URL, better to keep this the same.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (MNG-6778) Use https for schemaLocations

[Herve Boutemy (Jira)]

 [ 
https://issues.apache.org/jira/browse/MNG-6778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Herve Boutemy updated MNG-6778:
---
Fix Version/s: (was: 3.7.0)
   3.6.3

> Use https for schemaLocations
> -
>
> Key: MNG-6778
> URL: https://issues.apache.org/jira/browse/MNG-6778
> Project: Maven
>  Issue Type: Improvement
>Reporter: Robert Scholte
>Assignee: Robert Scholte
>Priority: Major
>  Labels: up-for-grabs
> Fix For: 3.6.3
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> All poms start with the following roottag:
> {code:xml}
> http://maven.apache.org/POM/4.0.0; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> {code}
> The schemaLocation VALUE should be updated to 
> {{https://maven.apache.org/xsd/maven-4.0.0.xsd}}; the key is just a constant 
> String, even though it looks like a URL, better to keep this the same.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Closed] (MNG-6778) Use https for schemaLocations

[Robert Scholte (Jira)]

 [ 
https://issues.apache.org/jira/browse/MNG-6778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte closed MNG-6778.
---
Fix Version/s: (was: 3.7.0-candidate)
   3.7.0
 Assignee: Robert Scholte
   Resolution: Fixed

Fixed in 
[d657c9c6b467db60c932799485fb4210c0bd1fe0|https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=d657c9c6b467db60c932799485fb4210c0bd1fe0]
Thanks for the patch!

> Use https for schemaLocations
> -
>
> Key: MNG-6778
> URL: https://issues.apache.org/jira/browse/MNG-6778
> Project: Maven
>  Issue Type: Improvement
>Reporter: Robert Scholte
>Assignee: Robert Scholte
>Priority: Major
>  Labels: up-for-grabs
> Fix For: 3.7.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> All poms start with the following roottag:
> {code:xml}
> http://maven.apache.org/POM/4.0.0; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> {code}
> The schemaLocation VALUE should be updated to 
> {{https://maven.apache.org/xsd/maven-4.0.0.xsd}}; the key is just a constant 
> String, even though it looks like a URL, better to keep this the same.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [maven] rfscholte merged pull request #299: [MNG-6778] - Use https for maven schemaLocations

[GitBox]

rfscholte merged pull request #299: [MNG-6778] - Use https for maven 
schemaLocations
URL: https://github.com/apache/maven/pull/299
 
 
   


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] rfscholte commented on issue #24: [MDEP-435] Added xml outputType to dependency tree

[GitBox]

rfscholte commented on issue #24: [MDEP-435] Added xml outputType to dependency 
tree
URL: 
https://github.com/apache/maven-dependency-plugin/pull/24#issuecomment-552093756
 
 
   To improve this patch:
   - try to write al least tests to confirm this works (and to prevent 
regression in the future due to other changes)
   - I personally would go for a different style of XML, maybe one that looks 
more like the pom. At least I would expect an explicit artifactId. the element 
should have the dependency-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

[jira] [Closed] (MPIR-383) Error when generation site with dependency build with Java 9+

[Robert Scholte (Jira)]

 [ 
https://issues.apache.org/jira/browse/MPIR-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte closed MPIR-383.
---
  Assignee: Robert Scholte
Resolution: Duplicate

> 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
>Assignee: Robert Scholte
>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 org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode 
> (Launcher.java:406)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.main 
> (Launcher.java:347)
> {code}
> This occurs because 

[GitHub] [maven] rfscholte commented on issue #299: [MNG-6778] - Use https for maven schemaLocations

[GitBox]

rfscholte commented on issue #299: [MNG-6778] - Use https for maven 
schemaLocations
URL: https://github.com/apache/maven/pull/299#issuecomment-552089308
 
 
   Just verified this: both master and 2.5.3 of maven-release-plugin doesn't 
change the schemaLocation if it is there.


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] michael-o commented on issue #299: [MNG-6778] - Use https for maven schemaLocations

[GitBox]

michael-o commented on issue #299: [MNG-6778] - Use https for maven 
schemaLocations
URL: https://github.com/apache/maven/pull/299#issuecomment-552089349
 
 
   Great, very good to know.


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

[Tibor Digana (Jira)]

 [ 
https://issues.apache.org/jira/browse/SUREFIRE-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tibor Digana updated SUREFIRE-1713:
---
Attachment: surefire-1713.zip

> 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
>Priority: Major
> Attachments: surefire-1713.zip
>
>
> 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 

[jira] [Closed] (MDEP-657) Maven - Failing when two modules have same dependency and both trying to download the dependency at the same time when Parallel flag is enabled.

[Robert Scholte (Jira)]

 [ 
https://issues.apache.org/jira/browse/MDEP-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte closed MDEP-657.
---
  Assignee: Robert Scholte
Resolution: Not A Problem

> Maven - Failing when two modules have same dependency and both trying to 
> download the dependency at the same time when Parallel flag is enabled.
> 
>
> Key: MDEP-657
> URL: https://issues.apache.org/jira/browse/MDEP-657
> Project: Maven Dependency Plugin
>  Issue Type: Bug
> Environment: Maven 3.6.1
>Reporter: Padma G
>Assignee: Robert Scholte
>Priority: Major
>
> Maven Version 3.6.1
> command : mvn -U -T 2C -DskipTests=true clean install -s settings.xml
> We have several modules with same dependency and it is failing when two are 
> downloading same dependency at the same time with below error. 
> if we remove parallel flag it will go through. But the build will be very 
> long. 
> Ideally it should wait and not fail?
> {noformat}
> [ERROR] Failed to execute goal on project content-model: Could not resolve 
> dependencies for project com.gehc.ei.zfp:content-model:jar:6011.0.1.8270: 
> Failed to collect dependencies at 
> com.gehc.ei.zfp:ei-logging-service:jar:6011.0.1.8109 -> 
> com.gehc.ei.zfp:atna-log-appender:jar:6011.0.1.8109: Failed to read artifact 
> descriptor for com.gehc.ei.zfp:atna-log-appender:jar:6011.0.1.8109: Could not 
> transfer artifact com.gehc.ei.zfp:atna-log-appender:pom:6011.0.1.8109 from/to 
> central ([/artifactory/maven-zfp-all|: 
> C:\Users\user\.m2\repository\com\gehc\ei\zfp\atna-log-appender\6011.0.1.8109\atna-log-appender-6011.0.1.8109.pom.part.lock
>  (The process cannot access the file because it is being used by another 
> process) -> [Help 1] 
> {noformat}
> Any idea why it is behaving this way?
> Regards,
> Padma



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Closed] (MDEP-639) Not showing omitted dependencies when running dependency:tree verbose

[Robert Scholte (Jira)]

 [ 
https://issues.apache.org/jira/browse/MDEP-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte closed MDEP-639.
---
  Assignee: Robert Scholte
Resolution: Duplicate

> Not showing omitted dependencies when running dependency:tree verbose
> -
>
> Key: MDEP-639
> URL: https://issues.apache.org/jira/browse/MDEP-639
> Project: Maven Dependency Plugin
>  Issue Type: Bug
>  Components: tree
>Affects Versions: 3.1.1
> Environment: Ubuntu 18.04.1 LTS (64-bit) Bionic Beaver Linux 
> 4.15.0-44-generic x86_64
>Reporter: Grzegorz Solecki
>Assignee: Robert Scholte
>Priority: Major
>
> When you run:
> {code:sh}
> $ mvn dependency:tree -Dverbose
> {code}
> it does not show omitted dependencies.
> It happens for version 3+.
> When I change to 2.10 it is working flawlessly
> Environment details:
> {code:sh}
> $ mvn -version
> Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 
> 2018-10-24T14:41:47-04:00)
> Maven home: /home/grzsol1/dev/tls/mvn/current
> Java version: 1.8.0_191, vendor: Oracle Corporation, runtime: 
> /home/grzsol1/dev/jdk/jdk1.8.0_191/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.15.0-44-generic", arch: "amd64", family: "unix"
> Ubuntu 18.04.1 LTS (64-bit) Bionic Beaver Linux 4.15.0-44-generic x86_64
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [maven-javadoc-plugin] eolivelli commented on issue #34: [MJAVADOC-628] - add javadoc.io link pattern when option is …

[GitBox]

eolivelli commented on issue #34: [MJAVADOC-628] - add javadoc.io link pattern 
when  option is …
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/34#issuecomment-552085735
 
 
   I am thinking about the mid term direction for the project.
   Hardcoding javadoc site is okay, we are wrapping the javadoc tool...
   Hardcoding a third party provider is something to think about a bit more.
   
   Having a configurable list with a default list of known providers may be 
some kind of trade off.
   
   I would like to know the option of other people in the community before 
moving forward with this work.
   I think it is very useful and I would like to do it, but following the best 
way for the community


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-javadoc-plugin] maxcellent commented on issue #34: [MJAVADOC-628] - add javadoc.io link pattern when option is …

[GitBox]

maxcellent commented on issue #34: [MJAVADOC-628] - add javadoc.io link pattern 
when  option is …
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/34#issuecomment-552084346
 
 
   yeah, I've been thinking about the same when implementing it. But it feels
   a bit overkill to add a generic mechanism if this is the only case.
   
   How about merge this for now? and then we can further extends it if there
   are more user requests to add more providers. Happy to help with the coding
   as well.
   
   On Sat, Nov 9, 2019 at 5:43 PM Enrico Olivelli 
   wrote:
   
   > *@eolivelli* requested changes on this pull request.
   >
   > Very nice.
   > I wonder if we can make it more configurable, with a list of patterns.
   > For each provider you can define a pattern with placeholders
   >
   > —
   > You are receiving this because you authored the thread.
   > Reply to this email directly, view it on GitHub
   > 
,
   > or unsubscribe
   > 

   > .
   >
   


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] michael-o commented on issue #299: [MNG-6778] - Use https for maven schemaLocations

[GitBox]

michael-o commented on issue #299: [MNG-6778] - Use https for maven 
schemaLocations
URL: https://github.com/apache/maven/pull/299#issuecomment-552084387
 
 
   I do remember that the Release Plugin rewrites the start tag. Previously, it 
injected still the old schema location. I may be wrong, but this needs to be 
checked.


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] cwansart commented on issue #299: [MNG-6778] - Use https for maven schemaLocations

[GitBox]

cwansart commented on issue #299: [MNG-6778] - Use https for maven 
schemaLocations
URL: https://github.com/apache/maven/pull/299#issuecomment-552080569
 
 
   @michael-o why? I changed the schemaLocations in the `maven.mdo` so I 
thought then running the build it will simply re-create everything with the 
changed url?


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