[jira] [Closed] (MEAR-307) skinny modules war libs are not put into shared lib directory

[Slawomir Jaranowski (Jira)]

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

Slawomir Jaranowski closed MEAR-307.

Resolution: Feedback Received

> skinny modules war libs are not put into shared lib directory
> -
>
> Key: MEAR-307
> URL: https://issues.apache.org/jira/browse/MEAR-307
> Project: Maven EAR Plugin
>  Issue Type: Bug
>Affects Versions: 3.2.0
>Reporter: Benjamin Asbach
>Priority: Major
> Attachments: MEAR-307_fixed_example.zip, ear-war-skinny-bug-ear.zip
>
>
> {code:xml}
>   
> 
>   
> maven-ear-plugin
> 3.2.0
> 
>   8
>   libs/
>   true
> 
>   
> 
>   
>   
> 
>   org.jenkins-ci.main
>   jenkins-war
>   2.328
>   war
> 
>   
> {code}
> With the current configuration the libs of war application are not placed 
> into libs directory. 
> This causes problems when you add an ejb module: The ejb dependencies are 
> placed in libs and the META-INF/MANIFEST-MF classpath entry of the war is set 
> with the libs classpath.
> This causes problems with classloading in JBoss EAP.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Assigned] (MDEP-795) Update Jetty to 9.4.45.v20220203

[Slawomir Jaranowski (Jira)]

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

Slawomir Jaranowski reassigned MDEP-795:


Assignee: Slawomir Jaranowski

> Update Jetty to 9.4.45.v20220203
> 
>
> Key: MDEP-795
> URL: https://issues.apache.org/jira/browse/MDEP-795
> Project: Maven Dependency Plugin
>  Issue Type: Task
>Affects Versions: 3.2.0
>Reporter: Jorge Solórzano
>Assignee: Slawomir Jaranowski
>Priority: Trivial
>
> New release of Jetty



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (MEAR-302) jakarta EE 9 EAR compatibility

[Hudson (Jira)]

[ 
https://issues.apache.org/jira/browse/MEAR-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17499976#comment-17499976
 ] 

Hudson commented on MEAR-302:
-

Build succeeded in Jenkins: Maven » Maven TLP » maven-ear-plugin » master #5

See 
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-ear-plugin/job/master/5/

> jakarta EE 9 EAR compatibility
> --
>
> Key: MEAR-302
> URL: https://issues.apache.org/jira/browse/MEAR-302
> Project: Maven EAR Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 3.2.0
> Environment: windows
> glassfish 6.1 
> jdk-15.0.0.36-hotspot
>Reporter: Dionysos
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.3.0
>
> Attachments: testapp.zip
>
>
> Hi! I've created this issue and attached a sample project as asked.
> On this one the war is getting packaged but again I cannot deploy it whatever 
> I tried.
>  
> Relative correspondence in users mailing list here:
> https://lists.apache.org/thread.html/r498322ab35e9e703f9e9735cf10c31959654f54ec85717cbd7aa84d7%40
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (SUREFIRE-2029) Parallel execution but surefire.forkNumber is the same

[Nathan McDonald (Jira)]

Nathan McDonald created SUREFIRE-2029:
-

 Summary: Parallel execution but surefire.forkNumber is the same
 Key: SUREFIRE-2029
 URL: https://issues.apache.org/jira/browse/SUREFIRE-2029
 Project: Maven Surefire
  Issue Type: Bug
  Components: Maven Failsafe Plugin
Affects Versions: 2.22.2
Reporter: Nathan McDonald


We have a multi module maven project, and due to our legacy architecture 
different modules are using the same underlying database.

We are using the one db per fork strategy mentioned, and each test clears the 
database before running its test.

 

This seems to work fine. But when running the full build on azure with
 -T 1C

We occasionally see one long running test fail, and have traced it to being 
that another test is running in parallel and clearing the database before that 
test fails.  This would only seem to happen if parallel threads running but 
same surefire.forkNumber being set for multiple threads.

Outputting logs of when tests start and end, with log outputting 
"Thread#$threadId\{$forkNumber}, e.g. Thread#7\{3} for thread with id 7, where  
surefire.forkNumber is 3 

Looking at logs we can see test starts on thread/fork 1, clears db as expected, 
and 30 seconds later logs that it completes (with error that is shown later).

But we can see just moments later, another test starts up and also clears the 
database, but is using same thread/fork:


2022-03-01T16:30:59.5953417Z 2022-03-01 16:30:59.585 [main] INFO  
e.t.b.h.w.c.AbstractIT:556 - Thread#1\{1} - Clearing the database before test
2022-03-01T16:30:59.7150510Z 2022-03-01 16:30:59.711 [main] INFO  
e.t.b.a.w.c.AnalysisJobDownloadControllerTest:78 - Thread#1\{1} - running setup 
for 
AnalysisJobDownloadControllerTest#downloadTransactionsAfterAppendingDuplicateRecords
….
2022-03-01T16:31:01.1305751Z 2022-03-01 16:31:01.128 [main] INFO  
e.t.b.h.w.c.AbstractIT:556 - Thread#1\{1} - Clearing the database before test
2022-03-01T16:31:01.6123984Z [INFO] Tests run: 2, Failures: 0, Errors: 0, 
Skipped: 0, Time elapsed: 24.715 s - in 
e.t.b.h.w.c.FinancialStatementReportItemRestControllerIT
2022-03-01T16:31:01.6124965Z [INFO] Running 
e.t.b.h.w.c.KeyInformationRestControllerIT
…
2022-03-01T16:31:29.1656587Z 2022-03-01 16:31:29.164 [main] INFO  
e.t.b.a.w.c.AnalysisJobDownloadControllerTest:94 - Thread#1\{1} - complete test 
AnalysisJobDownloadControllerTest#downloadTransactionsAfterAppendingDuplicateRecords

This isn't consistent though. Can see other cases where this works, but is 
running on separate fork:
Thread#1\{3} 

Obviously there are separate threads/forks running here, so seems like 
somewhere between maven multi module and  -T 1C, there is not always assigning 
unique forkNumber to each fork.

I figure best practice is probably having separate modules not use same db, so 
possibly this issue is existing but not being hit by people as would only cause 
issue if same fork number used for separate modules on different databases.

Still looking into issue our side will update if find workaround or more 
detailed information



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (SUREFIRE-2029) Parallel execution but surefire.forkNumber is the same

[Nathan McDonald (Jira)]

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

Nathan McDonald updated SUREFIRE-2029:
--
Description: 
We have a multi module maven project, and due to our legacy architecture 
different modules are using the same underlying database.

We are using the one db per fork strategy mentioned, and each test clears the 
database before running its test.

 

This seems to work fine. But when running the full build on azure with
 -T 1C

We occasionally see one long running test fail, and have traced it to being 
that another test is running in parallel and clearing the database before that 
test fails.  This would only seem to happen if parallel threads running but 
same surefire.forkNumber being set for multiple threads.

Outputting logs of when tests start and end, with log outputting 
"Thread#$threadId\{$forkNumber}, e.g. Thread#7\{3} for thread with id 7, where  
surefire.forkNumber is 3 

Looking at logs we can see test starts on thread/fork 1, clears db as expected, 
and 30 seconds later logs that it completes (with error that is shown later).

But we can see just moments later, another test starts up and also clears the 
database, but is using same thread/fork:

2022-03-01T16:30:59.5953417Z 2022-03-01 16:30:59.585 [main] INFO 
e.t.b.h.w.c.AbstractIT:556 - Thread#1\{1} - Clearing the database before test
2022-03-01T16:30:59.7150510Z 2022-03-01 16:30:59.711 [main] INFO 
e.t.b.a.w.c.AnalysisJobDownloadControllerTest:78 - Thread#1\{1} - running setup 
for 
AnalysisJobDownloadControllerTest#downloadTransactionsAfterAppendingDuplicateRecords
….
2022-03-01T16:31:01.1305751Z 2022-03-01 16:31:01.128 [main] INFO 
e.t.b.h.w.c.AbstractIT:556 - Thread#1\{1} - Clearing the database before test
2022-03-01T16:31:01.6123984Z [INFO] Tests run: 2, Failures: 0, Errors: 0, 
Skipped: 0, Time elapsed: 24.715 s - in 
e.t.b.h.w.c.FinancialStatementReportItemRestControllerIT
2022-03-01T16:31:01.6124965Z [INFO] Running 
e.t.b.h.w.c.KeyInformationRestControllerIT
…
2022-03-01T16:31:29.1656587Z 2022-03-01 16:31:29.164 [main] INFO 
e.t.b.a.w.c.AnalysisJobDownloadControllerTest:94 - Thread#1\{1} - complete test 
AnalysisJobDownloadControllerTest#downloadTransactionsAfterAppendingDuplicateRecords

This isn't consistent though. Can see other cases where this works, but is 
running on separate fork:
Thread#1\{3} 

Obviously there are separate threads/forks running here, so seems like 
somewhere between maven multi module and  -T 1C, there is not always assigning 
unique forkNumber to each fork.

I figure best practice is probably having separate modules not use same db, so 
possibly this issue is existing but not being hit by people as would only cause 
issue if same fork number used for separate modules on different databases.

Still looking into issue our side will update if find workaround or more 
detailed information.


Our surefire/failsafe config is in the root inherited by all other sub modules:


{code:java}

   org.apache.maven.plugins
   maven-surefire-plugin
   
  2
  @{argLine} -DforkNumber=${surefire.forkNumber}
  false
   


   org.apache.maven.plugins
   maven-failsafe-plugin
   
  1
  @{argLine} -DforkNumber=${surefire.forkNumber}
  false
  
${project.build.directory}/surefire-reports
   
   
  
 
integration-test
verify
 
  
   
{code}

  was:
We have a multi module maven project, and due to our legacy architecture 
different modules are using the same underlying database.

We are using the one db per fork strategy mentioned, and each test clears the 
database before running its test.

 

This seems to work fine. But when running the full build on azure with
 -T 1C

We occasionally see one long running test fail, and have traced it to being 
that another test is running in parallel and clearing the database before that 
test fails.  This would only seem to happen if parallel threads running but 
same surefire.forkNumber being set for multiple threads.

Outputting logs of when tests start and end, with log outputting 
"Thread#$threadId\{$forkNumber}, e.g. Thread#7\{3} for thread with id 7, where  
surefire.forkNumber is 3 

Looking at logs we can see test starts on thread/fork 1, clears db as expected, 
and 30 seconds later logs that it completes (with error that is shown later).

But we can see just moments later, another test starts up and also clears the 
database, but is using same thread/fork:


2022-03-01T16:30:59.5953417Z 2022-03-01 16:30:59.585 [main] INFO  
e.t.b.h.w.c.AbstractIT:556 - Thread#1\{1} - Clearing the database before test
2022-03-01T16:30:59.7150510Z 2022-03-01 16:30:59.711 [main] INFO  
e.t.b.a.w.c.AnalysisJobDownloadControllerTest:78 - Thread#1\{1} - running setup 
for 
AnalysisJobDownloadControllerTest#downloadTransactionsAfterAppendingDuplicateRecords
….
2022-03-01T16:31:01.1305751Z 2022-03-01 16:31:01.

[jira] [Updated] (SUREFIRE-2029) Parallel execution but surefire.forkNumber is the same

[Nathan McDonald (Jira)]

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

Nathan McDonald updated SUREFIRE-2029:
--
Description: 
We have a multi module maven project, and due to our legacy architecture 
different modules are using the same underlying database.

We are using the one db per fork strategy mentioned, and each test clears the 
database before running its test.

This seems to work fine. But when running the full build on azure with:
mvn ...  -T 1C -pl \{modulesToBuild} -amd

See output kicking off build like:
[INFO] Using the MultiThreadedBuilder implementation with a thread count of 8

We occasionally see one long running test fail, and have traced cause that 
another test is running in parallel and clearing the database before long 
running test completes .  This would only seem to be possible if parallel forks 
running but same surefire.forkNumber being set for multiple forks.

Outputting logs of when tests start and end, with log outputting 
"Thread#$threadId\{$forkNumber}, e.g. Thread#7\{3} for thread with id 7, where  
surefire.forkNumber is 3 

Looking at logs we can see test starts on thread/fork 1, clears db as expected, 
and 30 seconds later logs that it completes (with error that is shown later).

But we can see just moments later, another test starts up and also clears the 
database, but is using same thread/fork:

2022-03-01T16:30:59.5953417Z 2022-03-01 16:30:59.585 [main] INFO 
e.t.b.h.w.c.AbstractIT:556 - Thread#1\{1} - Clearing the database before test
2022-03-01T16:30:59.7150510Z 2022-03-01 16:30:59.711 [main] INFO 
e.t.b.a.w.c.AnalysisJobDownloadControllerTest:78 - Thread#1\{1} - running setup 
for 
AnalysisJobDownloadControllerTest#downloadTransactionsAfterAppendingDuplicateRecords
….
2022-03-01T16:31:01.1305751Z 2022-03-01 16:31:01.128 [main] INFO 
e.t.b.h.w.c.AbstractIT:556 - Thread#1\{1} - Clearing the database before test
2022-03-01T16:31:01.6123984Z [INFO] Tests run: 2, Failures: 0, Errors: 0, 
Skipped: 0, Time elapsed: 24.715 s - in 
e.t.b.h.w.c.FinancialStatementReportItemRestControllerIT
2022-03-01T16:31:01.6124965Z [INFO] Running 
e.t.b.h.w.c.KeyInformationRestControllerIT
…
2022-03-01T16:31:29.1656587Z 2022-03-01 16:31:29.164 [main] INFO 
e.t.b.a.w.c.AnalysisJobDownloadControllerTest:94 - Thread#1\{1} - complete test 
AnalysisJobDownloadControllerTest#downloadTransactionsAfterAppendingDuplicateRecords

This isn't consistent though. Can see other cases where this works, but is 
running on separate fork:
Thread#1\{3} 

Obviously there are separate threads/forks running here, so seems like 
somewhere between maven multi module and  -T 1C, there is not always assigning 
unique forkNumber to each fork.

I figure best practice is probably having separate modules not use same db, so 
possibly this issue is existing but not being hit by people as would only cause 
issue if same fork number used for separate modules on different databases.

Still looking into issue our side will update if find workaround or more 
detailed information.

Our surefire/failsafe config is in the root inherited by all other sub modules:
{code:java}

   org.apache.maven.plugins
   maven-surefire-plugin
   
  2
  @{argLine} -DforkNumber=${surefire.forkNumber}
  false
   


   org.apache.maven.plugins
   maven-failsafe-plugin
   
  1
  @{argLine} -DforkNumber=${surefire.forkNumber}
  false
  
${project.build.directory}/surefire-reports
   
   
  
 
integration-test
verify
 
  
   
{code}

  was:
We have a multi module maven project, and due to our legacy architecture 
different modules are using the same underlying database.

We are using the one db per fork strategy mentioned, and each test clears the 
database before running its test.

 

This seems to work fine. But when running the full build on azure with
 -T 1C

We occasionally see one long running test fail, and have traced it to being 
that another test is running in parallel and clearing the database before that 
test fails.  This would only seem to happen if parallel threads running but 
same surefire.forkNumber being set for multiple threads.

Outputting logs of when tests start and end, with log outputting 
"Thread#$threadId\{$forkNumber}, e.g. Thread#7\{3} for thread with id 7, where  
surefire.forkNumber is 3 

Looking at logs we can see test starts on thread/fork 1, clears db as expected, 
and 30 seconds later logs that it completes (with error that is shown later).

But we can see just moments later, another test starts up and also clears the 
database, but is using same thread/fork:

2022-03-01T16:30:59.5953417Z 2022-03-01 16:30:59.585 [main] INFO 
e.t.b.h.w.c.AbstractIT:556 - Thread#1\{1} - Clearing the database before test
2022-03-01T16:30:59.7150510Z 2022-03-01 16:30:59.711 [main] INFO 
e.t.b.a.w.c.AnalysisJobDownloadControllerTest:78 - Thread#1\{1} - running 

[jira] [Updated] (SUREFIRE-2029) Parallel execution but surefire.forkNumber is the same

[Nathan McDonald (Jira)]

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

Nathan McDonald updated SUREFIRE-2029:
--
Description: 
We have a multi module maven project, and due to our legacy architecture 
different modules are using the same underlying database.

We are using the one db per fork strategy mentioned, and each test clears the 
database before running its test.

This seems to work fine. But when running the full build on azure with:
{noformat}
mvn ...  -T 1C -pl {modulesToBuild} -amd{noformat}
 

See output kicking off build like:
{noformat}
[INFO] Using the MultiThreadedBuilder implementation with a thread count of 
8{noformat}
 

We occasionally see one long running test fail, and have traced cause that 
another test is running in parallel and clearing the database before long 
running test completes .  This would only seem to be possible if parallel forks 
running but same surefire.forkNumber being set for multiple forks.

Outputting logs of when tests start and end, with log outputting 
"Thread#$threadId\{$forkNumber}, e.g. Thread#7\{3} for thread with id 7, where  
surefire.forkNumber is 3 

Looking at logs we can see test starts on thread/fork 1, clears db as expected, 
and 30 seconds later logs that it completes (with error that is shown later).

But we can see just moments later, another test starts up and also clears the 
database, but is using same thread/fork:
{noformat}
2022-03-01T16:30:59.5953417Z 2022-03-01 16:30:59.585 [main] INFO 
e.t.b.h.w.c.AbstractIT:556 - Thread#1{1} - Clearing the database before test
2022-03-01T16:30:59.7150510Z 2022-03-01 16:30:59.711 [main] INFO 
e.t.b.a.w.c.AnalysisJobDownloadControllerTest:78 - Thread#1{1} - running setup 
for 
AnalysisJobDownloadControllerTest#downloadTransactionsAfterAppendingDuplicateRecords{noformat}
…
{noformat}
2022-03-01T16:31:01.1305751Z 2022-03-01 16:31:01.128 [main] INFO 
e.t.b.h.w.c.AbstractIT:556 - Thread#1{1} - Clearing the database before test
2022-03-01T16:31:01.6123984Z [INFO] Tests run: 2, Failures: 0, Errors: 0, 
Skipped: 0, Time elapsed: 24.715 s - in 
e.t.b.h.w.c.FinancialStatementReportItemRestControllerIT
2022-03-01T16:31:01.6124965Z [INFO] Running 
e.t.b.h.w.c.KeyInformationRestControllerIT{noformat}
…
{noformat}
2022-03-01T16:31:29.1656587Z 2022-03-01 16:31:29.164 [main] INFO 
e.t.b.a.w.c.AnalysisJobDownloadControllerTest:94 - Thread#1{1} - complete test 
AnalysisJobDownloadControllerTest#downloadTransactionsAfterAppendingDuplicateRecords{noformat}
This isn't consistent though. Can see other cases where this works, but the 
logs found where it is working can see long running test running on separate 
fork:
Thread#1\{3} 

Obviously there are separate threads/forks running here, so seems like 
somewhere between maven multi module and  -T 1C, there is not always assigning 
unique forkNumber to each fork.

I figure best practice is probably having separate modules not use same db, so 
possibly this issue is existing but not being hit by people as would only cause 
issue if same fork number used for separate modules on different databases.

Still looking into issue our side will update if find workaround or more 
detailed information.

Our surefire/failsafe config is in the root inherited by all other sub modules:
{code:java}

   org.apache.maven.plugins
   maven-surefire-plugin
   
  2
  @{argLine} -DforkNumber=${surefire.forkNumber}
  false
   


   org.apache.maven.plugins
   maven-failsafe-plugin
   
  1
  @{argLine} -DforkNumber=${surefire.forkNumber}
  false
  
${project.build.directory}/surefire-reports
   
   
  
 
integration-test
verify
 
  
   
{code}

  was:
We have a multi module maven project, and due to our legacy architecture 
different modules are using the same underlying database.

We are using the one db per fork strategy mentioned, and each test clears the 
database before running its test.

This seems to work fine. But when running the full build on azure with:
mvn ...  -T 1C -pl \{modulesToBuild} -amd

See output kicking off build like:
[INFO] Using the MultiThreadedBuilder implementation with a thread count of 8

We occasionally see one long running test fail, and have traced cause that 
another test is running in parallel and clearing the database before long 
running test completes .  This would only seem to be possible if parallel forks 
running but same surefire.forkNumber being set for multiple forks.

Outputting logs of when tests start and end, with log outputting 
"Thread#$threadId\{$forkNumber}, e.g. Thread#7\{3} for thread with id 7, where  
surefire.forkNumber is 3 

Looking at logs we can see test starts on thread/fork 1, clears db as expected, 
and 30 seconds later logs that it completes (with error that is shown later).

But we can see just moments later, another test starts up and also clears the 
database, 

[jira] [Updated] (MNG-6806) Provide Maven BOM

[Michael Osipov (Jira)]

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

Michael Osipov updated MNG-6806:

Fix Version/s: 3.9.0-candidate

> Provide Maven BOM
> -
>
> Key: MNG-6806
> URL: https://issues.apache.org/jira/browse/MNG-6806
> Project: Maven
>  Issue Type: Improvement
>Reporter: Robert Scholte
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-1, 3.9.0-candidate
>
>
> Maven libraries should always have the same version to ensure they work as 
> expected, hence the preferred way to manage that is with a bom.
> Let's introduce the {{maven-dependencies}}, a 
> [bom|https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Importing_Dependencies]
>  for Maven dependencies. We will likely need the same for plugins.
> See https://www.baeldung.com/spring-maven-bom about how to write and use the 
> bom.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (MNG-7427) Intermittend failure on Java 17 LTS on Windows x64

[Ben Middleton (Jira)]

Ben Middleton created MNG-7427:
--

 Summary: Intermittend failure on Java 17 LTS on Windows x64
 Key: MNG-7427
 URL: https://issues.apache.org/jira/browse/MNG-7427
 Project: Maven
  Issue Type: Bug
Affects Versions: 3.8.4
 Environment: I'm running Windows 2012 R2 Standard x64. Oracle JDK 
17.0.1+12 SE. Maven 3.8.4.
Reporter: Ben Middleton


I'm experiencing random failures building a Java 17 project on our Windows x64 
build agents:

{code}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-dependency-plugin:3.1.2:unpack 
(unpack-msbuild-tasks) on project udp-net-interop: Execution 
unpack-msbuild-tasks of goal 
org.apache.maven.plugins:maven-dependency-plugin:3.1.2:unpack failed: Plugin 
org.apache.maven.plugins:maven-dependency-plugin:3.1.2 or one of its 
dependencies could not be resolved: The following artifacts could not be 
resolved: org.apache.maven.doxia:doxia-logging-api:jar:${project.version}, 
org.apache.maven.doxia:doxia-skin-model:jar:${project.version}: 
org.apache.maven.doxia:doxia-logging-api:jar:${project.version} was not found 
in https://nexus.sdl.com/repository/releases during a previous attempt. This 
failure was cached in the local repository and resolution is not reattempted 
until the update interval of releases-nexus has elapsed or updates are forced 
-> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.apache.maven.plugins:maven-dependency-plugin:3.1.2:unpack 
(unpack-msbuild-tasks) on project udp-net-interop: Execution 
unpack-msbuild-tasks of goal 
org.apache.maven.plugins:maven-dependency-plugin:3.1.2:unpack failed: Plugin 
org.apache.maven.plugins:maven-dependency-plugin:3.1.2 or one of its 
dependencies could not be resolved: The following artifacts could not be 
resolved: org.apache.maven.doxia:doxia-logging-api:jar:${project.version}, 
org.apache.maven.doxia:doxia-skin-model:jar:${project.version}: 
org.apache.maven.doxia:doxia-logging-api:jar:${project.version} was not found 
in https://nexus.sdl.com/repository/releases during a previous attempt. This 
failure was cached in the local repository and resolution is not reattempted 
until the update interval of releases-nexus has elapsed or updates are forced
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:972)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke 
(NativeMethodAccessorImpl.java:77)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke 
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:568)
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 
unpack-msbuild-tasks of goal 
org.apache.maven.plugins:maven-dependency-plugin:3.1.2:unpack failed: Plugin 
org.apache.maven.plugins:maven-dependency-plugin:3.1.2 or one of its 
dependencies could not be resolved: The following artifacts could not be 
resolved: org.apache.maven.doxia:doxia-logging-api:jar:${project.version}, 
org.apache.maven.doxia:doxia-skin-model:jar:${project.version}: 
org.apache.maven.doxia:doxia-logging-api:jar:${project.version} was not found 
in https://nexus.sdl.com/repository/releases during a previous attempt. This 
failure was cached in the local repository and resolution is not reattempted 
until the update interval of releases-nexus has elapsed or updates are forced
at org.apache.maven.plugin.DefaultBuildPluginManager

[jira] [Commented] (MNG-7427) Intermittend failure on Java 17 LTS on Windows x64

[Michael Osipov (Jira)]

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

Michael Osipov commented on MNG-7427:
-

You are running an updated version of MDEP. Update!

> Intermittend failure on Java 17 LTS on Windows x64
> --
>
> Key: MNG-7427
> URL: https://issues.apache.org/jira/browse/MNG-7427
> Project: Maven
>  Issue Type: Bug
>Affects Versions: 3.8.4
> Environment: I'm running Windows 2012 R2 Standard x64. Oracle JDK 
> 17.0.1+12 SE. Maven 3.8.4.
>Reporter: Ben Middleton
>Priority: Major
> Fix For: waiting-for-feedback, wontfix-candidate
>
>
> I'm experiencing random failures building a Java 17 project on our Windows 
> x64 build agents:
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2:unpack 
> (unpack-msbuild-tasks) on project udp-net-interop: Execution 
> unpack-msbuild-tasks of goal 
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2:unpack failed: Plugin 
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2 or one of its 
> dependencies could not be resolved: The following artifacts could not be 
> resolved: org.apache.maven.doxia:doxia-logging-api:jar:${project.version}, 
> org.apache.maven.doxia:doxia-skin-model:jar:${project.version}: 
> org.apache.maven.doxia:doxia-logging-api:jar:${project.version} was not found 
> in https://nexus.sdl.com/repository/releases during a previous attempt. This 
> failure was cached in the local repository and resolution is not reattempted 
> until the update interval of releases-nexus has elapsed or updates are forced 
> -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-dependency-plugin:3.1.2:unpack 
> (unpack-msbuild-tasks) on project udp-net-interop: Execution 
> unpack-msbuild-tasks of goal 
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2:unpack failed: Plugin 
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2 or one of its 
> dependencies could not be resolved: The following artifacts could not be 
> resolved: org.apache.maven.doxia:doxia-logging-api:jar:${project.version}, 
> org.apache.maven.doxia:doxia-skin-model:jar:${project.version}: 
> org.apache.maven.doxia:doxia-logging-api:jar:${project.version} was not found 
> in https://nexus.sdl.com/repository/releases during a previous attempt. This 
> failure was cached in the local repository and resolution is not reattempted 
> until the update interval of releases-nexus has elapsed or updates are forced
> 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:972)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke 
> (NativeMethodAccessorImpl.java:77)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke 
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:568)
> 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 
> unpack-msbuild-tasks of goal 
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2:unpack failed: Plugin 
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2 or one of its 
> dependencies could not be resolved: The following artifacts could 

[jira] [Updated] (MNG-7427) Intermittend failure on Java 17 LTS on Windows x64

[Michael Osipov (Jira)]

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

Michael Osipov updated MNG-7427:

Fix Version/s: waiting-for-feedback
   wontfix-candidate

> Intermittend failure on Java 17 LTS on Windows x64
> --
>
> Key: MNG-7427
> URL: https://issues.apache.org/jira/browse/MNG-7427
> Project: Maven
>  Issue Type: Bug
>Affects Versions: 3.8.4
> Environment: I'm running Windows 2012 R2 Standard x64. Oracle JDK 
> 17.0.1+12 SE. Maven 3.8.4.
>Reporter: Ben Middleton
>Priority: Major
> Fix For: waiting-for-feedback, wontfix-candidate
>
>
> I'm experiencing random failures building a Java 17 project on our Windows 
> x64 build agents:
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2:unpack 
> (unpack-msbuild-tasks) on project udp-net-interop: Execution 
> unpack-msbuild-tasks of goal 
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2:unpack failed: Plugin 
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2 or one of its 
> dependencies could not be resolved: The following artifacts could not be 
> resolved: org.apache.maven.doxia:doxia-logging-api:jar:${project.version}, 
> org.apache.maven.doxia:doxia-skin-model:jar:${project.version}: 
> org.apache.maven.doxia:doxia-logging-api:jar:${project.version} was not found 
> in https://nexus.sdl.com/repository/releases during a previous attempt. This 
> failure was cached in the local repository and resolution is not reattempted 
> until the update interval of releases-nexus has elapsed or updates are forced 
> -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-dependency-plugin:3.1.2:unpack 
> (unpack-msbuild-tasks) on project udp-net-interop: Execution 
> unpack-msbuild-tasks of goal 
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2:unpack failed: Plugin 
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2 or one of its 
> dependencies could not be resolved: The following artifacts could not be 
> resolved: org.apache.maven.doxia:doxia-logging-api:jar:${project.version}, 
> org.apache.maven.doxia:doxia-skin-model:jar:${project.version}: 
> org.apache.maven.doxia:doxia-logging-api:jar:${project.version} was not found 
> in https://nexus.sdl.com/repository/releases during a previous attempt. This 
> failure was cached in the local repository and resolution is not reattempted 
> until the update interval of releases-nexus has elapsed or updates are forced
> 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:972)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke 
> (NativeMethodAccessorImpl.java:77)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke 
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:568)
> 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 
> unpack-msbuild-tasks of goal 
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2:unpack failed: Plugin 
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2 or one of its 
> dependencies could not be resolved: The following artifacts could not be 
> resolved: org.apache.ma

[jira] [Commented] (MNG-7427) Intermittend failure on Java 17 LTS on Windows x64

[Ben Middleton (Jira)]

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

Ben Middleton commented on MNG-7427:


OK - will try. Note that it affects various plugins. For example:

{code}
10:59:28  [INFO] Failed to execute goal 
org.apache.maven.plugins:maven-antrun-plugin:3.0.0:run (cpp-clean) on project 
udp-net-interop: Execution cpp-clean of goal 
org.apache.maven.plugins:maven-antrun-plugin:3.0.0:run failed: Plugin 
org.apache.maven.plugins:maven-antrun-plugin:3.0.0 or one of its dependencies 
could not be resolved: The following artifacts could not be resolved: 
org.apache.maven:maven-model:jar:${project.version}, 
org.sonatype.sisu:sisu-inject-bean:jar:${project.version}, 
org.apache.maven:maven-settings:jar:${project.version}, 
org.apache.maven:maven-settings-builder:jar:${project.version}, 
org.apache.maven:maven-repository-metadata:jar:${project.version}, 
org.apache.maven:maven-model-builder:jar:${project.version}, 
org.apache.maven:maven-aether-provider:jar:${project.version}, 
org.sonatype.aether:aether-spi:jar:${project.version}: Could not find artifact 
org.apache.maven:maven-model:jar:${project.version} in releases-nexus 
(https://nexus.sdl.com/repository/releases)
{code}

But perhaps it's related...

> Intermittend failure on Java 17 LTS on Windows x64
> --
>
> Key: MNG-7427
> URL: https://issues.apache.org/jira/browse/MNG-7427
> Project: Maven
>  Issue Type: Bug
>Affects Versions: 3.8.4
> Environment: I'm running Windows 2012 R2 Standard x64. Oracle JDK 
> 17.0.1+12 SE. Maven 3.8.4.
>Reporter: Ben Middleton
>Priority: Major
> Fix For: waiting-for-feedback, wontfix-candidate
>
>
> I'm experiencing random failures building a Java 17 project on our Windows 
> x64 build agents:
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2:unpack 
> (unpack-msbuild-tasks) on project udp-net-interop: Execution 
> unpack-msbuild-tasks of goal 
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2:unpack failed: Plugin 
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2 or one of its 
> dependencies could not be resolved: The following artifacts could not be 
> resolved: org.apache.maven.doxia:doxia-logging-api:jar:${project.version}, 
> org.apache.maven.doxia:doxia-skin-model:jar:${project.version}: 
> org.apache.maven.doxia:doxia-logging-api:jar:${project.version} was not found 
> in https://nexus.sdl.com/repository/releases during a previous attempt. This 
> failure was cached in the local repository and resolution is not reattempted 
> until the update interval of releases-nexus has elapsed or updates are forced 
> -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-dependency-plugin:3.1.2:unpack 
> (unpack-msbuild-tasks) on project udp-net-interop: Execution 
> unpack-msbuild-tasks of goal 
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2:unpack failed: Plugin 
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2 or one of its 
> dependencies could not be resolved: The following artifacts could not be 
> resolved: org.apache.maven.doxia:doxia-logging-api:jar:${project.version}, 
> org.apache.maven.doxia:doxia-skin-model:jar:${project.version}: 
> org.apache.maven.doxia:doxia-logging-api:jar:${project.version} was not found 
> in https://nexus.sdl.com/repository/releases during a previous attempt. This 
> failure was cached in the local repository and resolution is not reattempted 
> until the update interval of releases-nexus has elapsed or updates are forced
> 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:972)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
> at org.apache.maven.cli.MavenCli.m

[GitHub] [maven] kdebski85 commented on a change in pull request #589: [MNG-7304] - Use try-with-resources Statement

[GitBox]

kdebski85 commented on a change in pull request #589:
URL: https://github.com/apache/maven/pull/589#discussion_r817613991



##
File path: maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java
##
@@ -553,9 +553,8 @@ else if ( cliRequest.commandLine.hasOption( 
CLIManager.BATCH_MODE )
 logFile = resolveFile( logFile, cliRequest.workingDirectory );
 
 // redirect stdout and stderr to file
-try
+try ( PrintStream ps = new PrintStream( new FileOutputStream( 
logFile ) ) )

Review comment:
   PrintStream `ps` should not be closed here because it is passed to 
`System.setOut` and `System.setErr`. It will be automatically closed when 
`try-with-resource` block ends.




-- 
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.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven] michael-o commented on a change in pull request #589: [MNG-7304] - Use try-with-resources Statement

[GitBox]

michael-o commented on a change in pull request #589:
URL: https://github.com/apache/maven/pull/589#discussion_r817615789



##
File path: maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java
##
@@ -553,9 +553,8 @@ else if ( cliRequest.commandLine.hasOption( 
CLIManager.BATCH_MODE )
 logFile = resolveFile( logFile, cliRequest.workingDirectory );
 
 // redirect stdout and stderr to file
-try
+try ( PrintStream ps = new PrintStream( new FileOutputStream( 
logFile ) ) )

Review comment:
   I I think you are right. This could leave to side effects. Folks, other 
opinions?

##
File path: 
maven-compat/src/main/java/org/apache/maven/repository/legacy/DefaultUpdateCheckManager.java
##
@@ -350,60 +350,29 @@ private Properties read( File touchfile )
 
 synchronized ( touchfile.getAbsolutePath().intern() )
 {
-FileInputStream in = null;
-FileLock lock = null;
-
 try
 {
 Properties props = new Properties();
 
-in = new FileInputStream( touchfile );
-lock = in.getChannel().lock( 0, Long.MAX_VALUE, true );
-
-getLogger().debug( "Reading resolution-state from: " + 
touchfile );
-props.load( in );
-
-lock.release();
-lock = null;
+try ( FileInputStream in = new FileInputStream( touchfile ) )
+{
+try ( FileLock lock = in.getChannel().lock( 0, 
Long.MAX_VALUE, true ) )
+{
+getLogger().debug( "Reading resolution-state from: " + 
touchfile );
+props.load( in );
 
-in.close();
-in = null;
+lock.release();
+return props;
+}
+}
 
-return props;
 }
 catch ( IOException e )
 {
 getLogger().debug( "Failed to read resolution tracking file " 
+ touchfile, e );
 
 return null;
 }
-finally
-{
-if ( lock != null )
-{
-try
-{
-lock.release();
-}
-catch ( IOException e )
-{
-getLogger().debug( "Error releasing shared lock for 
resolution tracking file: " + touchfile,
-   e );
-}
-}
-
-if ( in != null )
-{
-try
-{
-in.close();
-}
-catch ( IOException e )
-{
-getLogger().debug( "Error closing FileChannel for 
resolution tracking file: " + touchfile, e );
-}
-}
-}
 }
 }
 

Review comment:
   I think we don't case about `maven-compat` anymore so I wouldn't really 
touch unless necessary. @gnodet @cstamas WDYT?




-- 
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.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven] kdebski85 commented on a change in pull request #589: [MNG-7304] - Use try-with-resources Statement

[GitBox]

kdebski85 commented on a change in pull request #589:
URL: https://github.com/apache/maven/pull/589#discussion_r817617088



##
File path: 
maven-compat/src/main/java/org/apache/maven/repository/legacy/DefaultUpdateCheckManager.java
##
@@ -350,60 +350,29 @@ private Properties read( File touchfile )
 
 synchronized ( touchfile.getAbsolutePath().intern() )
 {
-FileInputStream in = null;
-FileLock lock = null;
-
 try
 {
 Properties props = new Properties();
 
-in = new FileInputStream( touchfile );
-lock = in.getChannel().lock( 0, Long.MAX_VALUE, true );
-
-getLogger().debug( "Reading resolution-state from: " + 
touchfile );
-props.load( in );
-
-lock.release();
-lock = null;
+try ( FileInputStream in = new FileInputStream( touchfile ) )
+{
+try ( FileLock lock = in.getChannel().lock( 0, 
Long.MAX_VALUE, true ) )
+{
+getLogger().debug( "Reading resolution-state from: " + 
touchfile );
+props.load( in );
 
-in.close();
-in = null;
+lock.release();

Review comment:
   `lock.release();` is not needed because `FileLock::close` calls 
`FileLock::release`.
   `FileLock::close` will be called automatically when `try-with-resource` 
block ends.




-- 
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.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Commented] (MNG-7427) Intermittend failure on Java 17 LTS on Windows x64

[Michael Osipov (Jira)]

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

Michael Osipov commented on MNG-7427:
-

Something seems to be terribly wrong in your setup. Unless you can provide a 
sample project, it is likely an issue on your side.

> Intermittend failure on Java 17 LTS on Windows x64
> --
>
> Key: MNG-7427
> URL: https://issues.apache.org/jira/browse/MNG-7427
> Project: Maven
>  Issue Type: Bug
>Affects Versions: 3.8.4
> Environment: I'm running Windows 2012 R2 Standard x64. Oracle JDK 
> 17.0.1+12 SE. Maven 3.8.4.
>Reporter: Ben Middleton
>Priority: Major
> Fix For: waiting-for-feedback, wontfix-candidate
>
>
> I'm experiencing random failures building a Java 17 project on our Windows 
> x64 build agents:
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2:unpack 
> (unpack-msbuild-tasks) on project udp-net-interop: Execution 
> unpack-msbuild-tasks of goal 
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2:unpack failed: Plugin 
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2 or one of its 
> dependencies could not be resolved: The following artifacts could not be 
> resolved: org.apache.maven.doxia:doxia-logging-api:jar:${project.version}, 
> org.apache.maven.doxia:doxia-skin-model:jar:${project.version}: 
> org.apache.maven.doxia:doxia-logging-api:jar:${project.version} was not found 
> in https://nexus.sdl.com/repository/releases during a previous attempt. This 
> failure was cached in the local repository and resolution is not reattempted 
> until the update interval of releases-nexus has elapsed or updates are forced 
> -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-dependency-plugin:3.1.2:unpack 
> (unpack-msbuild-tasks) on project udp-net-interop: Execution 
> unpack-msbuild-tasks of goal 
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2:unpack failed: Plugin 
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2 or one of its 
> dependencies could not be resolved: The following artifacts could not be 
> resolved: org.apache.maven.doxia:doxia-logging-api:jar:${project.version}, 
> org.apache.maven.doxia:doxia-skin-model:jar:${project.version}: 
> org.apache.maven.doxia:doxia-logging-api:jar:${project.version} was not found 
> in https://nexus.sdl.com/repository/releases during a previous attempt. This 
> failure was cached in the local repository and resolution is not reattempted 
> until the update interval of releases-nexus has elapsed or updates are forced
> 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:972)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke 
> (NativeMethodAccessorImpl.java:77)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke 
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:568)
> 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 
> unpack-msbuild-tasks of goal 
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2:unpack failed: Plugin 
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2 or on

[GitHub] [maven-pdf-plugin] dependabot[bot] opened a new pull request #19: Bump actions/checkout from 2 to 3

[GitBox]

dependabot[bot] opened a new pull request #19:
URL: https://github.com/apache/maven-pdf-plugin/pull/19


   Bumps [actions/checkout](https://github.com/actions/checkout) from 2 to 3.
   
   Release notes
   Sourced from https://github.com/actions/checkout/releases";>actions/checkout's 
releases.
   
   v3.0.0
   
   Update default runtime to node16
   
   v2.4.0
   
   Convert SSH URLs like org-@github.com: to 
https://github.com/ - https://github-redirect.dependabot.com/actions/checkout/pull/621";>pr
   
   v2.3.5
   Update dependencies
   v2.3.4
   
   https://github-redirect.dependabot.com/actions/checkout/pull/379";>Add 
missing awaits
   https://github-redirect.dependabot.com/actions/checkout/pull/360";>Swap to 
Environment Files
   
   v2.3.3
   
   https://github-redirect.dependabot.com/actions/checkout/pull/345";>Remove 
Unneeded commit information from build logs
   https://github-redirect.dependabot.com/actions/checkout/pull/326";>Add 
Licensed to verify third party dependencies
   
   v2.3.2
   https://github-redirect.dependabot.com/actions/checkout/pull/320";>Add 
Third Party License Information to Dist Files
   v2.3.1
   https://github-redirect.dependabot.com/actions/checkout/pull/284";>Fix 
default branch resolution for .wiki and when using SSH
   v2.3.0
   https://github-redirect.dependabot.com/actions/checkout/pull/278";>Fallback
 to the default branch
   v2.2.0
   https://github-redirect.dependabot.com/actions/checkout/pull/258";>Fetch 
all history for all tags and branches when fetch-depth=0
   v2.1.1
   Changes to support GHES (https://github-redirect.dependabot.com/actions/checkout/pull/236";>here
 and https://github-redirect.dependabot.com/actions/checkout/pull/248";>here)
   v2.1.0
   
   https://github-redirect.dependabot.com/actions/checkout/pull/191";>Group 
output
   https://github-redirect.dependabot.com/actions/checkout/pull/199";>Changes 
to support GHES alpha release
   https://github-redirect.dependabot.com/actions/checkout/pull/184";>Persist 
core.sshCommand for submodules
   https://github-redirect.dependabot.com/actions/checkout/pull/163";>Add 
support ssh
   https://github-redirect.dependabot.com/actions/checkout/pull/179";>Convert 
submodule SSH URL to HTTPS, when not using SSH
   https://github-redirect.dependabot.com/actions/checkout/pull/157";>Add 
submodule support
   https://github-redirect.dependabot.com/actions/checkout/pull/144";>Follow 
proxy settings
   https://github-redirect.dependabot.com/actions/checkout/pull/141";>Fix ref 
for pr closed event when a pr is merged
   https://github-redirect.dependabot.com/actions/checkout/pull/128";>Fix 
issue checking detached when git less than 2.22
   
   
   
   
   Changelog
   Sourced from https://github.com/actions/checkout/blob/main/CHANGELOG.md";>actions/checkout's
 changelog.
   
   Changelog
   v2.3.1
   
   https://github-redirect.dependabot.com/actions/checkout/pull/284";>Fix 
default branch resolution for .wiki and when using SSH
   
   v2.3.0
   
   https://github-redirect.dependabot.com/actions/checkout/pull/278";>Fallback
 to the default branch
   
   v2.2.0
   
   https://github-redirect.dependabot.com/actions/checkout/pull/258";>Fetch 
all history for all tags and branches when fetch-depth=0
   
   v2.1.1
   
   Changes to support GHES (https://github-redirect.dependabot.com/actions/checkout/pull/236";>here
 and https://github-redirect.dependabot.com/actions/checkout/pull/248";>here)
   
   v2.1.0
   
   https://github-redirect.dependabot.com/actions/checkout/pull/191";>Group 
output
   https://github-redirect.dependabot.com/actions/checkout/pull/199";>Changes 
to support GHES alpha release
   https://github-redirect.dependabot.com/actions/checkout/pull/184";>Persist 
core.sshCommand for submodules
   https://github-redirect.dependabot.com/actions/checkout/pull/163";>Add 
support ssh
   https://github-redirect.dependabot.com/actions/checkout/pull/179";>Convert 
submodule SSH URL to HTTPS, when not using SSH
   https://github-redirect.dependabot.com/actions/checkout/pull/157";>Add 
submodule support
   https://github-redirect.dependabot.com/actions/checkout/pull/144";>Follow 
proxy settings
   https://github-redirect.dependabot.com/actions/checkout/pull/141";>Fix ref 
for pr closed event when a pr is merged
   https://github-redirect.dependabot.com/actions/checkout/pull/128";>Fix 
issue checking detached when git less than 2.22
   
   v2.0.0
   
   https://github-redirect.dependabot.com/actions/checkout/pull/108";>Do not 
pass cred on command line
   https://github-redirect.dependabot.com/actions/checkout/pull/107";>Add 
input persist-credentials
   https://github-redirect.dependabot.com/actions/checkout/pull/104";>Fallback
 to REST API to download repo
   
   
   
   
   Commits
   
   https://github.com/actions/checkout/commit/a12a3943b4bdde767164f792f33f40b04645d846";>a12a394
 update readme for v3 (https://github-redirect.dependabot.com/actions/checkout/issues/708";>#708)
   https://github.com/

[jira] [Commented] (MSHADE-156) shade plugin is transforming also strings that are not supposed to be transformed

[Patrick McCauley (Jira)]

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

Patrick McCauley commented on MSHADE-156:
-

I am seeing this as well.  Any updates on a fix?

> shade plugin is transforming also strings that are not supposed to be 
> transformed
> -
>
> Key: MSHADE-156
> URL: https://issues.apache.org/jira/browse/MSHADE-156
> Project: Maven Shade Plugin
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Neeme Praks
>Priority: Major
> Fix For: backlog
>
>
> I'm shading several third party libraries into a single JAR. In the context 
> of this issue, there are two important libraries:
> 1. com.nothome:javaxdelta:2.0.1 - this library is in "at.spardat.xma.xdelta" 
> package.
> 2. ch.qos.logback:logback-classic:1.0.11 - in this library, in class 
> ch.qos.logback.classic.spi.StackTraceElementProxy, there is a method to 
> convert stack trace elements into strings:
> {code}
>   public String getSTEAsString() {
> if (steAsString == null) {
>   steAsString = "at " + ste.toString();
> }
> return steAsString;
>   }
> {code}
> I use "org.myorgname.appname.shaded" package for shading.
> During shading, the constant "at " is replaced with 
> "org.myorgname.appname.shaded.at" -- shade plugin thinks that the "at" in the 
> beginning of that string is a package name and shades it.
> This results in an unfortunate side-effect: all logged stack traces now look 
> like this:
> {noformat}
> Caused by: java.util.zip.ZipException: error in opening zip file
>   org.myorgname.appname.shaded.at java.util.zip.ZipFile.open(Native 
> Method) ~[na:1.6.0_19]
>   org.myorgname.appname.shaded.at 
> java.util.zip.ZipFile.(ZipFile.java:114) ~[na:1.6.0_19]
>   org.myorgname.appname.shaded.at 
> java.util.zip.ZipFile.(ZipFile.java:131) ~[na:1.6.0_19]
> {noformat}
> Possible fixes:
> * instead of just checking the first part of the package (at), check for the 
> full package (at.spardat.xma.xdelta).
> * allow to configure shade plugin to ignore certain string constants in 
> certain classes (this would solve also some other issues we have with shade 
> plugin being too eager).
> * both of the above.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (MRELEASE-1079) scm tag is added to child module

[Jira]

Markus Schäfer created MRELEASE-1079:


 Summary: scm tag is added to child module
 Key: MRELEASE-1079
 URL: https://issues.apache.org/jira/browse/MRELEASE-1079
 Project: Maven Release Plugin
  Issue Type: Bug
  Components: prepare
Affects Versions: 3.0.0-M5
Reporter: Markus Schäfer


With Version 3.0.0-M5 child modules gets an scm tag during the prepare step 
when there is more than one module level.

The Bug seems to be in RewritePomsForReleasePhase.

RewritePomsForDevelopmentPhase removes the scm tag. Only the tagged release has 
these scm tags.

 

 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (MSHARED-1019) Allow pass raw cli option to Maven process

[Hudson (Jira)]

[ 
https://issues.apache.org/jira/browse/MSHARED-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500128#comment-17500128
 ] 

Hudson commented on MSHARED-1019:
-

Build succeeded in Jenkins: Maven » Maven TLP » maven-invoker » PR-44 #2

See 
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-invoker/job/PR-44/2/

> Allow pass raw cli option to Maven process
> --
>
> Key: MSHARED-1019
> URL: https://issues.apache.org/jira/browse/MSHARED-1019
> Project: Maven Shared Components
>  Issue Type: New Feature
>  Components: maven-invoker
>Reporter: Slawomir Jaranowski
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: maven-invoker-3.2.0
>
>
> Something like {{addCliOption}} in {{Verifier}}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (MRELEASE-1079) scm tag is added to child module

[Jira]

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

Markus Schäfer updated MRELEASE-1079:
-
Priority: Critical  (was: Major)

> scm tag is added to child module
> 
>
> Key: MRELEASE-1079
> URL: https://issues.apache.org/jira/browse/MRELEASE-1079
> Project: Maven Release Plugin
>  Issue Type: Bug
>  Components: prepare
>Affects Versions: 3.0.0-M5
>Reporter: Markus Schäfer
>Priority: Critical
>
> With Version 3.0.0-M5 child modules gets an scm tag during the prepare step 
> when there is more than one module level.
> The Bug seems to be in RewritePomsForReleasePhase.
> RewritePomsForDevelopmentPhase removes the scm tag. Only the tagged release 
> has these scm tags.
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (MEAR-302) jakarta EE 9 EAR compatibility

[Slawomir Jaranowski (Jira)]

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

Slawomir Jaranowski updated MEAR-302:
-
Issue Type: New Feature  (was: Dependency upgrade)

> jakarta EE 9 EAR compatibility
> --
>
> Key: MEAR-302
> URL: https://issues.apache.org/jira/browse/MEAR-302
> Project: Maven EAR Plugin
>  Issue Type: New Feature
>Affects Versions: 3.2.0
> Environment: windows
> glassfish 6.1 
> jdk-15.0.0.36-hotspot
>Reporter: Dionysos
>Assignee: Slawomir Jaranowski
>Priority: Major
> Fix For: 3.3.0
>
> Attachments: testapp.zip
>
>
> Hi! I've created this issue and attached a sample project as asked.
> On this one the war is getting packaged but again I cannot deploy it whatever 
> I tried.
>  
> Relative correspondence in users mailing list here:
> https://lists.apache.org/thread.html/r498322ab35e9e703f9e9735cf10c31959654f54ec85717cbd7aa84d7%40
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (SUREFIRE-2030) Upgrade to animal-sniffer 1.21

[Guillaume Nodet (Jira)]

Guillaume Nodet created SUREFIRE-2030:
-

 Summary: Upgrade to animal-sniffer 1.21
 Key: SUREFIRE-2030
 URL: https://issues.apache.org/jira/browse/SUREFIRE-2030
 Project: Maven Surefire
  Issue Type: Bug
Reporter: Guillaume Nodet






--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (SUREFIRE-2030) Upgrade to animal-sniffer 1.21

[Slawomir Jaranowski (Jira)]

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

Slawomir Jaranowski commented on SUREFIRE-2030:
---

Is it not duplicated for: SUREFIRE-2008

> Upgrade to animal-sniffer 1.21
> --
>
> Key: SUREFIRE-2030
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2030
> Project: Maven Surefire
>  Issue Type: Bug
>Reporter: Guillaume Nodet
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Closed] (SUREFIRE-2030) Upgrade to animal-sniffer 1.21

[Guillaume Nodet (Jira)]

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

Guillaume Nodet closed SUREFIRE-2030.
-
Resolution: Duplicate

> Upgrade to animal-sniffer 1.21
> --
>
> Key: SUREFIRE-2030
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2030
> Project: Maven Surefire
>  Issue Type: Bug
>Reporter: Guillaume Nodet
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (MENFORCER-407) Enforcer 3.0.0 breaks with Maven 3.8.4

[Matt Nelson (Jira)]

[ 
https://issues.apache.org/jira/browse/MENFORCER-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500309#comment-17500309
 ] 

Matt Nelson commented on MENFORCER-407:
---

[~michael-o] I'll echo what has been said on a few of the other issues logged 
against enforcer-3.0.0. I pulled down the changes from MSHARED-1016 and was 
able to confirm that fixes the issue.

{code:xml}
org.apache.maven.plugins
maven-enforcer-plugin
3.0.0


org.apache.maven.shared
maven-dependency-tree
3.1.1-SNAPSHOT


{code}

> Enforcer 3.0.0 breaks with Maven 3.8.4
> --
>
> Key: MENFORCER-407
> URL: https://issues.apache.org/jira/browse/MENFORCER-407
> Project: Maven Enforcer Plugin
>  Issue Type: Bug
>  Components: Plugin
>Affects Versions: 3.0.0
>Reporter: David Pilato
>Priority: Major
> Fix For: waiting-for-feedback
>
> Attachments: enforcer-3.0.0.log, enforcer.3.0.0-M3.log
>
>
> Here is the situation. I'm trying to [upgrade enforcer from 3.0.0-M3 to 
> 3.0.0|https://github.com/dadoonet/fscrawler/pull/1214]. 
>  
> Everything worked well on my laptop with Maven 3.5.3. So I looked at the 
> version used by Github actions and saw that it's using Maven 3.8.4.
> As soon as I upgraded my local version of Maven to 3.8.4, I started to hit 
> the same exact issue. It seems to try to pull 
> net.sf.ehcache:sizeof-agent:1.0.1. 
> If I revert Enforcer to 3.0.0-M3 with Maven 3.8.4, I can run without any 
> issue mvn enforcer:enforce.
> So I suspect that the combination of both upgrades is triggering something. 
> I noted also that 3.0.0 now tries to enforce as well dependencies marked as 
> provided. Might be the reason of this.
> I attached the full logs when running with 3.0.0 and 3.0.0-M3.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (SUREFIRE-2031) Both fields/parameters "includes" and "excludes" should should be in target MOJO class

[Tibor Digana (Jira)]

Tibor Digana created SUREFIRE-2031:
--

 Summary: Both fields/parameters "includes" and "excludes" should 
should be in target MOJO class
 Key: SUREFIRE-2031
 URL: https://issues.apache.org/jira/browse/SUREFIRE-2031
 Project: Maven Surefire
  Issue Type: Improvement
  Components: Maven Failsafe Plugin, Maven Surefire Plugin
Reporter: Tibor Digana
Assignee: Tibor Digana
 Fix For: 3.0.0-M6


The fields "includes" and "excludes" in the issue SUREFIRE-1964 cannot be 
tested in the same way because "excludes" appears in {{AbstractSurefireMojo}} 
but the "includes" is in {{SurefirePlugin}} and {{IntegrationTestMojo}}.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Assigned] (SUREFIRE-1964) Method filtering support on excludes and includes file

[Tibor Digana (Jira)]

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

Tibor Digana reassigned SUREFIRE-1964:
--

Assignee: Tibor Digana

> Method filtering support on excludes and includes file
> --
>
> Key: SUREFIRE-1964
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1964
> Project: Maven Surefire
>  Issue Type: New Feature
>  Components: Maven Surefire Plugin
>Reporter: Ildefonso Montero
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M6
>
>
> The current code of Maven Surefire plugin does not provide capabilities for 
> performing method filtering on includes/excludes based on files (using 
> surefire.excludesFile or surefire.includesFile params)
> Main idea is to provide the same method filtering capabilities that we can 
> perform nowadays using the -Dtest parameter but on the mentioned resources
> Thus, if we perform {{mvn test -Dsurefire.excludesFile=/foo/bar/file}} and it 
> is using method filtering like:
>  
> {code:java}
> test.SomeTest#test1
> test.SomeTest#test2
> test.SomeTest#test3
> test.SomeTest#test4
> test.SomeTest#test5
> test.SomeTest#test6 {code}
> on a project like: 
> [https://github.com/jglick/simple-maven-project-with-tests] we obtain:
>  
> {{Method filter prohibited in includes|excludes|includesFile|excludesFile 
> parameter}}
> With method filtering enabled on these parameters, we will be able to obtain
> {code:java}
> [INFO] ---
> [INFO]  T E S T S
> [INFO] ---
> [INFO] Running test.SomeTest
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.035 
> s - in test.SomeTest
> [INFO] Running test.OtherTest
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 
> s - in test.OtherTest
> [INFO] 
> [INFO] Results:
> [INFO] 
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> [INFO] 
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 1.808 s
> [INFO] Finished at: 2021-12-03T18:00:37+01:00
> [INFO] 
>  
> {code}
> were test.SomeTest test methods were directly ignored.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (SUREFIRE-1964) Method filtering support on excludes and includes file

[Tibor Digana (Jira)]

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

Tibor Digana updated SUREFIRE-1964:
---
Fix Version/s: 3.0.0-M6

> Method filtering support on excludes and includes file
> --
>
> Key: SUREFIRE-1964
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1964
> Project: Maven Surefire
>  Issue Type: New Feature
>  Components: Maven Surefire Plugin
>Reporter: Ildefonso Montero
>Priority: Major
> Fix For: 3.0.0-M6
>
>
> The current code of Maven Surefire plugin does not provide capabilities for 
> performing method filtering on includes/excludes based on files (using 
> surefire.excludesFile or surefire.includesFile params)
> Main idea is to provide the same method filtering capabilities that we can 
> perform nowadays using the -Dtest parameter but on the mentioned resources
> Thus, if we perform {{mvn test -Dsurefire.excludesFile=/foo/bar/file}} and it 
> is using method filtering like:
>  
> {code:java}
> test.SomeTest#test1
> test.SomeTest#test2
> test.SomeTest#test3
> test.SomeTest#test4
> test.SomeTest#test5
> test.SomeTest#test6 {code}
> on a project like: 
> [https://github.com/jglick/simple-maven-project-with-tests] we obtain:
>  
> {{Method filter prohibited in includes|excludes|includesFile|excludesFile 
> parameter}}
> With method filtering enabled on these parameters, we will be able to obtain
> {code:java}
> [INFO] ---
> [INFO]  T E S T S
> [INFO] ---
> [INFO] Running test.SomeTest
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.035 
> s - in test.SomeTest
> [INFO] Running test.OtherTest
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 
> s - in test.OtherTest
> [INFO] 
> [INFO] Results:
> [INFO] 
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> [INFO] 
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 1.808 s
> [INFO] Finished at: 2021-12-03T18:00:37+01:00
> [INFO] 
>  
> {code}
> were test.SomeTest test methods were directly ignored.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (SUREFIRE-2031) Both fields/parameters "includes" and "excludes" should be in target MOJO class. User names should be unique.

[Tibor Digana (Jira)]

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

Tibor Digana updated SUREFIRE-2031:
---
Summary: Both fields/parameters "includes" and "excludes" should be in 
target MOJO class. User names should be unique.  (was: Both fields/parameters 
"includes" and "excludes" should should be in target MOJO class)

> Both fields/parameters "includes" and "excludes" should be in target MOJO 
> class. User names should be unique.
> -
>
> Key: SUREFIRE-2031
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2031
> Project: Maven Surefire
>  Issue Type: Improvement
>  Components: Maven Failsafe Plugin, Maven Surefire Plugin
>Reporter: Tibor Digana
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M6
>
>
> The fields "includes" and "excludes" in the issue SUREFIRE-1964 cannot be 
> tested in the same way because "excludes" appears in {{AbstractSurefireMojo}} 
> but the "includes" is in {{SurefirePlugin}} and {{IntegrationTestMojo}}.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Closed] (MINSTALL-159) Prevent adding several times the same file for install

[Michael Osipov (Jira)]

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

Michael Osipov closed MINSTALL-159.
---
Fix Version/s: (was: 3.0.0)
 Assignee: Michael Osipov
   Resolution: Fixed

> Prevent adding several times the same file for install
> --
>
> Key: MINSTALL-159
> URL: https://issues.apache.org/jira/browse/MINSTALL-159
> Project: Maven Install Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.0-M1
>Reporter: Karl Heinz Marbaise
>Assignee: Michael Osipov
>Priority: Critical
>
> Currently you can execute several times maven-source-plugin and create more 
> than one file which should be installed. 
> That will result in installing several times the same file which means this 
> will overwrite the file. 
> Later with maven-deploy-plugin that will result in failure during release 
> cause in case of releases that will be blocked by a repository manager.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Closed] (SUREFIRE-2031) Both fields/parameters "includes" and "excludes" should be in target MOJO class. User names should be unique.

[Tibor Digana (Jira)]

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

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

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

> Both fields/parameters "includes" and "excludes" should be in target MOJO 
> class. User names should be unique.
> -
>
> Key: SUREFIRE-2031
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2031
> Project: Maven Surefire
>  Issue Type: Improvement
>  Components: Maven Failsafe Plugin, Maven Surefire Plugin
>Reporter: Tibor Digana
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M6
>
>
> The fields "includes" and "excludes" in the issue SUREFIRE-1964 cannot be 
> tested in the same way because "excludes" appears in {{AbstractSurefireMojo}} 
> but the "includes" is in {{SurefirePlugin}} and {{IntegrationTestMojo}}.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (SUREFIRE-2029) Parallel execution but surefire.forkNumber is the same

[Falko Modler (Jira)]

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

Falko Modler commented on SUREFIRE-2029:


I think I'm seeing something similar (with maven-surefire-plugin). Which Maven 
version are you using?

> Parallel execution but surefire.forkNumber is the same
> --
>
> Key: SUREFIRE-2029
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2029
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Failsafe Plugin
>Affects Versions: 2.22.2
>Reporter: Nathan McDonald
>Priority: Minor
>
> We have a multi module maven project, and due to our legacy architecture 
> different modules are using the same underlying database.
> We are using the one db per fork strategy mentioned, and each test clears the 
> database before running its test.
> This seems to work fine. But when running the full build on azure with:
> {noformat}
> mvn ...  -T 1C -pl {modulesToBuild} -amd{noformat}
>  
> See output kicking off build like:
> {noformat}
> [INFO] Using the MultiThreadedBuilder implementation with a thread count of 
> 8{noformat}
>  
> We occasionally see one long running test fail, and have traced cause that 
> another test is running in parallel and clearing the database before long 
> running test completes .  This would only seem to be possible if parallel 
> forks running but same surefire.forkNumber being set for multiple forks.
> Outputting logs of when tests start and end, with log outputting 
> "Thread#$threadId\{$forkNumber}, e.g. Thread#7\{3} for thread with id 7, 
> where  surefire.forkNumber is 3 
> Looking at logs we can see test starts on thread/fork 1, clears db as 
> expected, and 30 seconds later logs that it completes (with error that is 
> shown later).
> But we can see just moments later, another test starts up and also clears the 
> database, but is using same thread/fork:
> {noformat}
> 2022-03-01T16:30:59.5953417Z 2022-03-01 16:30:59.585 [main] INFO 
> e.t.b.h.w.c.AbstractIT:556 - Thread#1{1} - Clearing the database before test
> 2022-03-01T16:30:59.7150510Z 2022-03-01 16:30:59.711 [main] INFO 
> e.t.b.a.w.c.AnalysisJobDownloadControllerTest:78 - Thread#1{1} - running 
> setup for 
> AnalysisJobDownloadControllerTest#downloadTransactionsAfterAppendingDuplicateRecords{noformat}
> …
> {noformat}
> 2022-03-01T16:31:01.1305751Z 2022-03-01 16:31:01.128 [main] INFO 
> e.t.b.h.w.c.AbstractIT:556 - Thread#1{1} - Clearing the database before test
> 2022-03-01T16:31:01.6123984Z [INFO] Tests run: 2, Failures: 0, Errors: 0, 
> Skipped: 0, Time elapsed: 24.715 s - in 
> e.t.b.h.w.c.FinancialStatementReportItemRestControllerIT
> 2022-03-01T16:31:01.6124965Z [INFO] Running 
> e.t.b.h.w.c.KeyInformationRestControllerIT{noformat}
> …
> {noformat}
> 2022-03-01T16:31:29.1656587Z 2022-03-01 16:31:29.164 [main] INFO 
> e.t.b.a.w.c.AnalysisJobDownloadControllerTest:94 - Thread#1{1} - complete 
> test 
> AnalysisJobDownloadControllerTest#downloadTransactionsAfterAppendingDuplicateRecords{noformat}
> This isn't consistent though. Can see other cases where this works, but the 
> logs found where it is working can see long running test running on separate 
> fork:
> Thread#1\{3} 
> Obviously there are separate threads/forks running here, so seems like 
> somewhere between maven multi module and  -T 1C, there is not always 
> assigning unique forkNumber to each fork.
> I figure best practice is probably having separate modules not use same db, 
> so possibly this issue is existing but not being hit by people as would only 
> cause issue if same fork number used for separate modules on different 
> databases.
> Still looking into issue our side will update if find workaround or more 
> detailed information.
> Our surefire/failsafe config is in the root inherited by all other sub 
> modules:
> {code:java}
> 
>org.apache.maven.plugins
>maven-surefire-plugin
>
>   2
>   @{argLine} -DforkNumber=${surefire.forkNumber}
>   false
>
> 
> 
>org.apache.maven.plugins
>maven-failsafe-plugin
>
>   1
>   @{argLine} -DforkNumber=${surefire.forkNumber}
>   false
>   
> ${project.build.directory}/surefire-reports
>
>
>   
>  
> integration-test
> verify
>  
>   
>
> {code}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (SUREFIRE-1951) Required class missing (TestSetFailedException). Need to add dependency explicilty.

[Michael Osipov (Jira)]

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

Michael Osipov updated SUREFIRE-1951:
-
Fix Version/s: waiting-for-feedback

> Required class missing (TestSetFailedException). Need to add dependency 
> explicilty.
> ---
>
> Key: SUREFIRE-1951
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1951
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Failsafe Plugin
>Affects Versions: 3.0.0-M5
>Reporter: Chanseok Oh
>Priority: Major
>  Labels: waiting-for-feedback
> Fix For: waiting-for-feedback
>
>
> Getting the following error when upgrading from 3.0.0-M4 to 3.0.0-M5.
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-failsafe-plugin:3.0.0-M5:integration-test 
> (default) on project bigtable-beam-import: Execution default of goal 
> org.apache.maven.plugins:maven-failsafe-plugin:3.0.0-M5:integration-test 
> failed: A required class was missing while executing 
> org.apache.maven.plugins:maven-failsafe-plugin:3.0.0-M5:integration-test: 
> org/apache/maven/surefire/api/testset/TestSetFailedException
> [ERROR] -
> [ERROR] realm =
> plugin>org.apache.maven.plugins:maven-failsafe-plugin:3.0.0-M5
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] = 
> file:/root/.m2/repository/org/apache/maven/plugins/maven-failsafe-plugin/3.0.0-M5/maven-failsafe-plugin-3.0.0-M5.jar
> [ERROR] urls[1] = 
> file:/root/.m2/repository/org/apache/maven/surefire/surefire-junit47/3.0.0-M4/surefire-junit47-3.0.0-M4.jar
> [ERROR] urls[2] = 
> file:/root/.m2/repository/org/apache/maven/surefire/common-junit48/3.0.0-M4/common-junit48-3.0.0-M4.jar
> [ERROR] urls[3] = 
> file:/root/.m2/repository/org/apache/maven/surefire/common-junit4/3.0.0-M4/common-junit4-3.0.0-M4.jar
> [ERROR] urls[4] = 
> file:/root/.m2/repository/org/apache/maven/surefire/common-junit3/3.0.0-M4/common-junit3-3.0.0-M4.jar
> [ERROR] urls[5] = 
> file:/root/.m2/repository/org/apache/maven/surefire/common-java5/3.0.0-M4/common-java5-3.0.0-M4.jar
> [ERROR] urls[6] = 
> file:/root/.m2/repository/org/apache/maven/surefire/surefire-grouper/3.0.0-M4/surefire-grouper-3.0.0-M4.jar
> [ERROR] urls[7] = 
> file:/root/.m2/repository/org/apache/maven/surefire/surefire-api/3.0.0-M4/surefire-api-3.0.0-M4.jar
> [ERROR] urls[8] = 
> file:/root/.m2/repository/org/apache/maven/surefire/surefire-logger-api/3.0.0-M4/surefire-logger-api-3.0.0-M4.jar
> [ERROR] urls[9] = 
> file:/root/.m2/repository/org/apache/maven/surefire/maven-surefire-common/3.0.0-M5/maven-surefire-common-3.0.0-M5.jar
> [ERROR] urls[10] = 
> file:/root/.m2/repository/org/apache/maven/surefire/surefire-extensions-api/3.0.0-M5/surefire-extensions-api-3.0.0-M5.jar
> [ERROR] urls[11] = 
> file:/root/.m2/repository/org/apache/maven/surefire/surefire-booter/3.0.0-M5/surefire-booter-3.0.0-M5.jar
> [ERROR] urls[12] = 
> file:/root/.m2/repository/org/apache/maven/surefire/surefire-extensions-spi/3.0.0-M5/surefire-extensions-spi-3.0.0-M5.jar
> [ERROR] urls[13] = 
> file:/root/.m2/repository/org/apache/maven/shared/maven-artifact-transfer/0.11.0/maven-artifact-transfer-0.11.0.jar
> [ERROR] urls[14] = 
> file:/root/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/3.1.0/maven-common-artifact-filters-3.1.0.jar
> [ERROR] urls[15] = 
> file:/root/.m2/repository/commons-codec/commons-codec/1.11/commons-codec-1.11.jar
> [ERROR] urls[16] = 
> file:/root/.m2/repository/org/codehaus/plexus/plexus-java/1.0.5/plexus-java-1.0.5.jar
> [ERROR] urls[17] = file:/root/.m2/repository/org/ow2/asm/asm/7.2/asm-7.2.jar
> [ERROR] urls[18] = 
> file:/root/.m2/repository/com/thoughtworks/qdox/qdox/2.0-M9/qdox-2.0-M9.jar
> [ERROR] urls[19] = 
> file:/root/.m2/repository/org/apache/maven/surefire/surefire-shared-utils/3.0.0-M4/surefire-shared-utils-3.0.0-M4.jar
> [ERROR] urls[20] = 
> file:/root/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> [ERROR] Number of foreign imports: 1
> [ERROR] import: Entry[import  from realm 
> ClassRealm[project>com.google.cloud.bigtable:bigtable-client-parent:2.0.0-beta2-SNAPSHOT,
>  parent: ClassRealm[maven.api, parent: null]]]
> [ERROR]
> [ERROR] -: 
> org.apache.maven.surefire.api.testset.TestSetFailedException
> I have to manually add the following {{surefire-api}} dependency:
> 
>   org.apache.maven.plugins
>   maven-surefire-plugin
>   3.0.0-M5
>   
> false
>   
> 
> 
>   org.apache.maven.plugins
>   maven-failsafe-plugin
>   3.0.0-M5
>   
> false
>   
> 

[jira] [Updated] (SUREFIRE-1951) Required class missing (TestSetFailedException). Need to add dependency explicilty.

[Michael Osipov (Jira)]

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

Michael Osipov updated SUREFIRE-1951:
-
Labels:   (was: waiting-for-feedback)

> Required class missing (TestSetFailedException). Need to add dependency 
> explicilty.
> ---
>
> Key: SUREFIRE-1951
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1951
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Failsafe Plugin
>Affects Versions: 3.0.0-M5
>Reporter: Chanseok Oh
>Priority: Major
> Fix For: waiting-for-feedback
>
>
> Getting the following error when upgrading from 3.0.0-M4 to 3.0.0-M5.
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-failsafe-plugin:3.0.0-M5:integration-test 
> (default) on project bigtable-beam-import: Execution default of goal 
> org.apache.maven.plugins:maven-failsafe-plugin:3.0.0-M5:integration-test 
> failed: A required class was missing while executing 
> org.apache.maven.plugins:maven-failsafe-plugin:3.0.0-M5:integration-test: 
> org/apache/maven/surefire/api/testset/TestSetFailedException
> [ERROR] -
> [ERROR] realm =
> plugin>org.apache.maven.plugins:maven-failsafe-plugin:3.0.0-M5
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] = 
> file:/root/.m2/repository/org/apache/maven/plugins/maven-failsafe-plugin/3.0.0-M5/maven-failsafe-plugin-3.0.0-M5.jar
> [ERROR] urls[1] = 
> file:/root/.m2/repository/org/apache/maven/surefire/surefire-junit47/3.0.0-M4/surefire-junit47-3.0.0-M4.jar
> [ERROR] urls[2] = 
> file:/root/.m2/repository/org/apache/maven/surefire/common-junit48/3.0.0-M4/common-junit48-3.0.0-M4.jar
> [ERROR] urls[3] = 
> file:/root/.m2/repository/org/apache/maven/surefire/common-junit4/3.0.0-M4/common-junit4-3.0.0-M4.jar
> [ERROR] urls[4] = 
> file:/root/.m2/repository/org/apache/maven/surefire/common-junit3/3.0.0-M4/common-junit3-3.0.0-M4.jar
> [ERROR] urls[5] = 
> file:/root/.m2/repository/org/apache/maven/surefire/common-java5/3.0.0-M4/common-java5-3.0.0-M4.jar
> [ERROR] urls[6] = 
> file:/root/.m2/repository/org/apache/maven/surefire/surefire-grouper/3.0.0-M4/surefire-grouper-3.0.0-M4.jar
> [ERROR] urls[7] = 
> file:/root/.m2/repository/org/apache/maven/surefire/surefire-api/3.0.0-M4/surefire-api-3.0.0-M4.jar
> [ERROR] urls[8] = 
> file:/root/.m2/repository/org/apache/maven/surefire/surefire-logger-api/3.0.0-M4/surefire-logger-api-3.0.0-M4.jar
> [ERROR] urls[9] = 
> file:/root/.m2/repository/org/apache/maven/surefire/maven-surefire-common/3.0.0-M5/maven-surefire-common-3.0.0-M5.jar
> [ERROR] urls[10] = 
> file:/root/.m2/repository/org/apache/maven/surefire/surefire-extensions-api/3.0.0-M5/surefire-extensions-api-3.0.0-M5.jar
> [ERROR] urls[11] = 
> file:/root/.m2/repository/org/apache/maven/surefire/surefire-booter/3.0.0-M5/surefire-booter-3.0.0-M5.jar
> [ERROR] urls[12] = 
> file:/root/.m2/repository/org/apache/maven/surefire/surefire-extensions-spi/3.0.0-M5/surefire-extensions-spi-3.0.0-M5.jar
> [ERROR] urls[13] = 
> file:/root/.m2/repository/org/apache/maven/shared/maven-artifact-transfer/0.11.0/maven-artifact-transfer-0.11.0.jar
> [ERROR] urls[14] = 
> file:/root/.m2/repository/org/apache/maven/shared/maven-common-artifact-filters/3.1.0/maven-common-artifact-filters-3.1.0.jar
> [ERROR] urls[15] = 
> file:/root/.m2/repository/commons-codec/commons-codec/1.11/commons-codec-1.11.jar
> [ERROR] urls[16] = 
> file:/root/.m2/repository/org/codehaus/plexus/plexus-java/1.0.5/plexus-java-1.0.5.jar
> [ERROR] urls[17] = file:/root/.m2/repository/org/ow2/asm/asm/7.2/asm-7.2.jar
> [ERROR] urls[18] = 
> file:/root/.m2/repository/com/thoughtworks/qdox/qdox/2.0-M9/qdox-2.0-M9.jar
> [ERROR] urls[19] = 
> file:/root/.m2/repository/org/apache/maven/surefire/surefire-shared-utils/3.0.0-M4/surefire-shared-utils-3.0.0-M4.jar
> [ERROR] urls[20] = 
> file:/root/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
> [ERROR] Number of foreign imports: 1
> [ERROR] import: Entry[import  from realm 
> ClassRealm[project>com.google.cloud.bigtable:bigtable-client-parent:2.0.0-beta2-SNAPSHOT,
>  parent: ClassRealm[maven.api, parent: null]]]
> [ERROR]
> [ERROR] -: 
> org.apache.maven.surefire.api.testset.TestSetFailedException
> I have to manually add the following {{surefire-api}} dependency:
> 
>   org.apache.maven.plugins
>   maven-surefire-plugin
>   3.0.0-M5
>   
> false
>   
> 
> 
>   org.apache.maven.plugins
>   maven-failsafe-plugin
>   3.0.0-M5
>   
> false
>   
>   
> 
>   **
>

[jira] [Updated] (MNG-6112) Central repository in the 4.0.0 super POM should declare update policy 'never'.

[Michael Osipov (Jira)]

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

Michael Osipov updated MNG-6112:

Labels: must-be-in-4.0.0-alpha-2  (was: must-be-in-4.0.0-alpha-1)

> Central repository in the 4.0.0 super POM should declare update policy 
> 'never'.
> ---
>
> Key: MNG-6112
> URL: https://issues.apache.org/jira/browse/MNG-6112
> Project: Maven
>  Issue Type: Bug
>Affects Versions: 3.5.0-beta-1
>Reporter: Christian Schulte
>Assignee: Robert Scholte
>Priority: Major
>  Labels: must-be-in-4.0.0-alpha-2
> Fix For: 4.0.x-candidate
>
>




--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (MNG-5781) resolution of nested import scoped dependencies causes maven to reach out to external central repo

[Michael Osipov (Jira)]

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

Michael Osipov updated MNG-5781:

Labels: must-be-in-4.0.0-alpha-2  (was: must-be-in-4.0.0-alpha-1)

> resolution of nested import scoped dependencies causes maven to reach out to 
> external central repo
> --
>
> Key: MNG-5781
> URL: https://issues.apache.org/jira/browse/MNG-5781
> Project: Maven
>  Issue Type: Bug
>  Components: Bootstrap & Build, Dependencies
>Affects Versions: 3.2.5
> Environment: Apache Maven 3.2.5 
> (12a6b3acb947671f09b81f49094c53f426d8cea1; 2014-12-14T09:29:23-08:00)
> Maven home: /usr/local/maven-3.2.5
> Java version: 1.7.0_76, vendor: Oracle Corporation
> Java home: /usr/local/jdk1.7.0_76-server-jre/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "2.6.32-504.3.3.el6.centos.plus.x86_64", arch: 
> "amd64", family: "unix"
>Reporter: Ravi Sanwal
>Priority: Major
>  Labels: must-be-in-4.0.0-alpha-2
> Fix For: 4.0.x-candidate
>
> Attachments: MNG-5781-Maven360.txt, first.pom.xml, 
> global_settings.xml, last.pom.xml, second.pom.xml
>
>
> When a project uses a dependency that has as import scoped dependency, which 
> in turn also has another import scoped dependency (nested imported scoped 
> dependencies), resolution of the last level of dependency makes maven to 
> reach our to the external central repository 
> ([https://repo.maven.apache.org/maven2/])
> Steps to reproduce:
> Use the attached global settings file.
> It has an internal repository declared as a replacement to 'central', you can 
> point to one of your own internal repo.(not the local)
> Build the attached file first.pom.xml: 
> {code:java}
> mvn -gs global_settings.xml install -f first.pom.xml{code}
> Build the attached file second.pom.xml:
> {code:java}
> mvn install -f second.pom.xml{code}
> Then, delete _org.aspectj:aspectjtools from local repo (rm 
> ~/.m2/repository/org/aspectj_/aspectjtools), we want to download this from 
> our internal central repository alias repository.
> Build the attached file last.pom.xml: 
> {code:java}
> mvn -gs global_settings.xml dependency:copy-dependencies -f last.pom.xml{code}
> (copy dependencies because this is a pom project, alternatively change 
> last.pom.xml to a jar project and do mvn -gs global_settings.xml install - 
> same thing)
> You'll see that org.aspectj:aspectjtools is being downloaded from central 
> ([https://repo.maven.apache.org/maven2/]) effectively rendering hosting our 
> own repositories useless.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (MNG-6772) Super POM overwrites remapped central repository in nested dependencyManagement import POMs

[Michael Osipov (Jira)]

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

Michael Osipov updated MNG-6772:

Labels: must-be-in-4.0.0-alpha-2  (was: must-be-in-4.0.0-alpha-1)

> Super POM overwrites remapped central repository in nested 
> dependencyManagement import POMs
> ---
>
> Key: MNG-6772
> URL: https://issues.apache.org/jira/browse/MNG-6772
> Project: Maven
>  Issue Type: Bug
>  Components: Artifacts and Repositories, POM
>Affects Versions: 3.6.2
>Reporter: Eddie Wiegers
>Priority: Major
>  Labels: must-be-in-4.0.0-alpha-2
> Fix For: 4.0.x-candidate
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> My projects define a repository with {{central,}} which is meant to 
> specifically override the entry in the Super POM. This is specifically what 
> [JFrog Artifactory 
> recommends|https://www.jfrog.com/confluence/display/RTF/Maven+Repository#MavenRepository-ManuallyOverridingtheBuilt-inRepositories]
>  doing, and seems valid in situations where the _real_ Maven Central may be 
> unreachable.
>  
> The override takes precedence almost all of the time. However, there is at 
> least one scenario where this is not the case, and that is when importing a 
> POM that in turn imports another POM.
>  
> Digging into the code, it appears the reason this happens is because the 
> {{DefaultModelBuilder}} overwrites repositories after interpolation is 
> complete:
> [https://github.com/apache/maven/blob/53f04f03e3e58c75dcc791d557758357a6ec7983/maven-model-builder/src/main/java/org/apache/maven/model/building/DefaultModelBuilder.java#L411]
>  
> From what I can tell, this is done with the intention of overwriting 
> repositories that were added to the local resolver prior to interpolation 
> with the interpolated version. Due to the way the {{DefaultModelResolver}} 
> works, an unintended side effect is that the {{central}} repository from the 
> Super POM is added once after each interpolation. The first time the 
> repository is added, it is added to the {{repositoryIds}} but doesn't 
> actually remove the original repository. The second time it is added is when 
> the original repository will be replaced. Currently, the repositoryIds are 
> preserved in the {{ModelResolver}} when resolving import POMs, leading to the 
> behavior I am seeing where the second nested import POM ends up being where 
> the failure occurs.
>  
> I am planning on submitting a PR to clone the {{ModelResolver}} in a way that 
> resets the repositoryIds prior to import POMs being resolved, since they are 
> separate artifact builds. That seems like the most consistent fix to me that 
> covers cases outside of the the Super POM's {{central}} definition.
>  
> *Workarounds*:
> The current workaround is to use a repository ID other than {{central}} for 
> my Artifactory repository, which isn't ideal since it leaves the potential 
> for long timeouts to occur on the real {{central}} when an artifact can't be 
> resolved from my Artifactory repository.
>  
> Mirrors are not an ideal workaround since getting them in place on all 
> possible build environments isn't trivial.
>  
> When looking at the code I noticed 
> {{RepositorySystemSession#isIgnoreArtifactDescriptorRepositories()}} being 
> checked in various places, which seems like it would also act as a potential 
> workaround, but I don't see a way to enable this value via MavenCLI or 
> properties of any kind. It seems like this value aligns well with what 
> Artifactory is already trying to enforce, so it would make sense to enable 
> this in projects that intend to exclusively use Artifactory. Is there a 
> supported way to set this value outside of constructing a Maven build in code?



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (MNG-6561) New RepositorySystem implementation as replacement of deprecated from maven-compat

[Michael Osipov (Jira)]

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

Michael Osipov updated MNG-6561:

Labels: must-be-in-4.0.0-alpha-2  (was: must-be-in-4.0.0-alpha-1)

> New RepositorySystem implementation as replacement of deprecated from 
> maven-compat
> --
>
> Key: MNG-6561
> URL: https://issues.apache.org/jira/browse/MNG-6561
> Project: Maven
>  Issue Type: Improvement
>Reporter: Sylwester Lachiewicz
>Priority: Major
>  Labels: must-be-in-4.0.0-alpha-2
> Fix For: 4.0.x-candidate
>
>
> Create a component that will replace 
> org.apache.maven.repository.RepositorySystem implementation from maven-compat 
> module to keep backward compatibility with Maven 2.x plugins.
> While testing MNG-5995 and with deleted maven-compat.jar - a compilation of 
> basic project failed with error:
>  
> {code:java}
> [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @ my-app ---
> [WARNING] Error injecting: org.apache.maven.plugin.compiler.CompilerMojo
> com.google.inject.ProvisionException: Unable to provision, see the following 
> errors:
> 1) No implementation for org.apache.maven.repository.RepositorySystem was 
> bound.
> while locating org.apache.maven.plugin.compiler.CompilerMojo
> 1 error
> at com.google.inject.internal.InternalProvisionException.toProvisionException 
> (InternalProvisionException.java:226)
> at com.google.inject.internal.InjectorImpl$1.get (InjectorImpl.java:1053)
> at com.google.inject.internal.InjectorImpl.getInstance 
> (InjectorImpl.java:1086)
> at org.eclipse.sisu.space.AbstractDeferredClass.get 
> (AbstractDeferredClass.java:48)
> at com.google.inject.internal.ProviderInternalFactory.provision 
> (ProviderInternalFactory.java:85)
> at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision 
> (InternalFactoryToInitializableAdapter.java:57)
> at com.google.inject.internal.ProviderInternalFactory$1.call 
> (ProviderInternalFactory.java:66)
> at 
> com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision 
> (ProvisionListenerStackCallback.java:112)
> at 
> com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision 
> (ProvisionListenerStackCallback.java:127)
> at com.google.inject.internal.ProvisionListenerStackCallback.provision 
> (ProvisionListenerStackCallback.java:66)
> at com.google.inject.internal.ProviderInternalFactory.circularGet 
> (ProviderInternalFactory.java:61)
> at com.google.inject.internal.InternalFactoryToInitializableAdapter.get 
> (InternalFactoryToInitializableAdapter.java:47)
> at com.google.inject.internal.InjectorImpl$1.get (InjectorImpl.java:1050)
> at org.eclipse.sisu.inject.Guice4$1.get (Guice4.java:162)
> at org.eclipse.sisu.inject.LazyBeanEntry.getValue (LazyBeanEntry.java:81)
> at org.eclipse.sisu.plexus.LazyPlexusBean.getValue (LazyPlexusBean.java:51)
> at org.codehaus.plexus.DefaultPlexusContainer.lookup 
> (DefaultPlexusContainer.java:263)
> at org.codehaus.plexus.DefaultPlexusContainer.lookup 
> (DefaultPlexusContainer.java:255)
> at 
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo 
> (DefaultMavenPluginManager.java:520)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:124)
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile 
> (default-compile) on project my-app: Execution default-compile of goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile failed: Unable 
> to load the mojo 'compile' (or one of its required components) from the 
> plugin 'org.apache.maven.plugins:maven-compiler-plugin:3.8.0': 
> com.google.inject.ProvisionException: Unable to provision, see the following 
> errors:
> [ERROR]
> [ERROR] 1) No implementation for c was bound.
> [ERROR] while locating org.apache.maven.plugin.compiler.CompilerMojo
> [ERROR] at 
> ClassRealm[plugin>org.apache.maven.plugins:maven-compiler-plugin:3.8.0, 
> parent: jdk.internal.loader.ClassLoaders$AppClassLoader@6e5e91e4] (via 
> modules: org.eclipse.sisu.wire.WireModule -> 
> org.eclipse.sisu.plexus.PlexusBindingModule)
> [ERROR] while locating org.apache.maven.plugin.Mojo annotated with 
> @com.google.inject.name.Named(value="org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile")
> [ERROR]
> [ERROR] 1 error
> [ERROR] role: org.apache.maven.plugin.Mojo
> [ERROR] roleHint: 
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile{code}
> Sometimes we can change usages of 
> _org.apache.maven.repository.RepositorySystem_ to 
> _org.apache.maven.bridge.MavenRepositorySystem_



--
This message was sent by Atlassian Jira
(v8.20.1#82000

[jira] [Updated] (MNG-7046) Revert MNG-5639 and make repo config static only (no ${param} interpolation)

[Michael Osipov (Jira)]

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

Michael Osipov updated MNG-7046:

Labels: must-be-in-4.0.0-alpha-2  (was: must-be-in-4.0.0-alpha-1)

> Revert MNG-5639 and make repo config static only (no ${param} interpolation)
> 
>
> Key: MNG-7046
> URL: https://issues.apache.org/jira/browse/MNG-7046
> Project: Maven
>  Issue Type: Task
>  Components: Artifacts and Repositories, Dependencies
>Affects Versions: 3.6.3
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>  Labels: must-be-in-4.0.0-alpha-2
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> As discussed in MNG-5639 repositories should always be known upfront, they 
> have to be static to avoid chicken and egg situations, a project should not 
> influence settings. It should be the way around.
> In subsequent ticket it will be verified that repo configuration does not 
> contain any expression: 
> https://github.com/apache/maven/commit/d411c3fa98832e7d86d901fe86ff63ba907cf868#commitcomment-44782281.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (MNG-7059) Add profile-free repository support in Maven Settings model

[Michael Osipov (Jira)]

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

Michael Osipov updated MNG-7059:

Labels: must-be-in-4.0.0-alpha-2  (was: must-be-in-4.0.0-alpha-1)

> Add profile-free repository support in Maven Settings model
> ---
>
> Key: MNG-7059
> URL: https://issues.apache.org/jira/browse/MNG-7059
> Project: Maven
>  Issue Type: New Feature
>  Components: Settings
>Affects Versions: 3.6.3
>Reporter: Michael Osipov
>Assignee: Robert Scholte
>Priority: Major
>  Labels: must-be-in-4.0.0-alpha-2
> Fix For: 4.0.x-candidate
>
>
> With MNG-4645 = the move of Maven Central repository definition out of [Super 
> POM|https://maven.apache.org/ref/3.6.3/maven-model-builder/super-pom.html] 
> into global settings, [current settings 
> model|https://maven.apache.org/ref/3.6.3/maven-settings/settings.html] forces 
> to use a profile, although central repository should be always there w/o a 
> profile.
> Settings Model version 1.2.0 shall have native support for repositories w/o 
> the need to use profiles.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (MNG-7094) Assure in an IT that reactor repository definitions are not used when Model Builder downloads dependencies with scope import

[Michael Osipov (Jira)]

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

Michael Osipov updated MNG-7094:

Labels: must-be-in-4.0.0-alpha-2  (was: must-be-in-4.0.0-alpha-1)

> Assure in an IT that reactor repository definitions are not used when Model 
> Builder downloads dependencies with scope import
> 
>
> Key: MNG-7094
> URL: https://issues.apache.org/jira/browse/MNG-7094
> Project: Maven
>  Issue Type: Task
>  Components: Artifacts and Repositories, Dependencies, Design, 
> Patterns & Best Practices, Integration Tests
>Affects Versions: 3.6.3
>Reporter: Michael Osipov
>Priority: Major
>  Labels: must-be-in-4.0.0-alpha-2
> Fix For: 4.0.x-candidate
>
>
> Based on several discussions (MNG-6772, MNG-6397) the topic of repo scoping 
> causes a lot of confusion.
> Create an IT which shows that repositories defined in a reactor are never 
> available (inject) to download imported dependency BOMs. Thus all repos are 
> properly scoped.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (MNG-7046) Revert MNG-5639 and make repo config static only (no ${param} interpolation)

[Michael Osipov (Jira)]

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

Michael Osipov updated MNG-7046:

Fix Version/s: 4.0.0-alpha-2
   (was: 4.0.0-alpha-1)

> Revert MNG-5639 and make repo config static only (no ${param} interpolation)
> 
>
> Key: MNG-7046
> URL: https://issues.apache.org/jira/browse/MNG-7046
> Project: Maven
>  Issue Type: Task
>  Components: Artifacts and Repositories, Dependencies
>Affects Versions: 3.6.3
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>  Labels: must-be-in-4.0.0-alpha-2
> Fix For: 4.0.0, 4.0.0-alpha-2
>
>
> As discussed in MNG-5639 repositories should always be known upfront, they 
> have to be static to avoid chicken and egg situations, a project should not 
> influence settings. It should be the way around.
> In subsequent ticket it will be verified that repo configuration does not 
> contain any expression: 
> https://github.com/apache/maven/commit/d411c3fa98832e7d86d901fe86ff63ba907cf868#commitcomment-44782281.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (SUREFIRE-1964) Method filtering support on excludes and includes file

[Tibor Digana (Jira)]

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

Tibor Digana commented on SUREFIRE-1964:


The GH Ci is running.
But we have some problem with ASF build. I have reported a bug for our Infra 
team.

> Method filtering support on excludes and includes file
> --
>
> Key: SUREFIRE-1964
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1964
> Project: Maven Surefire
>  Issue Type: New Feature
>  Components: Maven Surefire Plugin
>Reporter: Ildefonso Montero
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M6
>
>
> The current code of Maven Surefire plugin does not provide capabilities for 
> performing method filtering on includes/excludes based on files (using 
> surefire.excludesFile or surefire.includesFile params)
> Main idea is to provide the same method filtering capabilities that we can 
> perform nowadays using the -Dtest parameter but on the mentioned resources
> Thus, if we perform {{mvn test -Dsurefire.excludesFile=/foo/bar/file}} and it 
> is using method filtering like:
>  
> {code:java}
> test.SomeTest#test1
> test.SomeTest#test2
> test.SomeTest#test3
> test.SomeTest#test4
> test.SomeTest#test5
> test.SomeTest#test6 {code}
> on a project like: 
> [https://github.com/jglick/simple-maven-project-with-tests] we obtain:
>  
> {{Method filter prohibited in includes|excludes|includesFile|excludesFile 
> parameter}}
> With method filtering enabled on these parameters, we will be able to obtain
> {code:java}
> [INFO] ---
> [INFO]  T E S T S
> [INFO] ---
> [INFO] Running test.SomeTest
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.035 
> s - in test.SomeTest
> [INFO] Running test.OtherTest
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 
> s - in test.OtherTest
> [INFO] 
> [INFO] Results:
> [INFO] 
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> [INFO] 
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 1.808 s
> [INFO] Finished at: 2021-12-03T18:00:37+01:00
> [INFO] 
>  
> {code}
> were test.SomeTest test methods were directly ignored.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (MNG-7399) Intermittent failures on Java 18-EA / 19-EA on Windows x86 (32-bit)

[Michael Osipov (Jira)]

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

Michael Osipov commented on MNG-7399:
-

Updated plugins:
{noformat}
diff --git a/pom.xml b/pom.xml
index 8978d643a..3bbcaa760 100644
--- a/pom.xml
+++ b/pom.xml
@@ -38,6 +38,7 @@
 
 org.apache.maven.plugins
 maven-compiler-plugin
+3.10.0
 
 1.8
 1.8
@@ -45,6 +46,26 @@
 1.8
 
 
+  
+org.apache.maven.plugins
+maven-install-plugin
+3.0.0-M1
+
+
+org.apache.maven.plugins
+maven-jar-plugin
+3.2.2
+
+
+org.apache.maven.plugins
+maven-surefire-plugin
+3.0.0-M5
+
+
+org.apache.maven.plugins
+maven-clean-plugin
+3.1.0
+
 
 
{noformat}

and see things like:
{noformat}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-jar-plugin:3.2.2:jar (default-jar) on project 
project9: The parameters 'classesDirectory', 'outputDirectory' for goal 
org.apache.maven.plugins:maven-jar-plugin:3.2.2:jar are missing or invalid -> 
[Help 1]
{noformat}

I have no idea how to diagnose this. I am sure that Oracle has broken something.

> Intermittent failures on Java 18-EA / 19-EA on Windows x86 (32-bit)
> ---
>
> Key: MNG-7399
> URL: https://issues.apache.org/jira/browse/MNG-7399
> Project: Maven
>  Issue Type: Bug
>Affects Versions: 3.8.4
>Reporter: Dmitry Bedrin
>Priority: Major
>
> I'm maintaining open-source project (multi-module Maven) and my CI/CD builds 
> it on 3 platforms (Linux, MacOS, Windows) on Java versions from 6 to 19-ea 
> both 64 bit and 32 bit (where available).
> After adding JDK 18-ea and 19-ea to the compatibility matrix I've noticed 
> that builds on Windows *32bit* are failing with errors like these:
>  
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar (default-jar) on project 
> sniffy: The parameters 'classesDirectory', 'outputDirectory' for goal 
> org.apache.maven.plugins:maven-jar-plugin:3.2.0:jar are missing or invalid -> 
> [Help 1]{noformat}
>  
> Another example with stack trace from compiler plugin (other plugins fail as 
> well):
> {noformat}[INFO] --- maven-compiler-plugin:3.9.0:compile (default-compile) @ 
> sniffy ---
> [DEBUG] Dependency collection stats {ConflictMarker.analyzeTime=9500, 
> ConflictMarker.markTime=9500, ConflictMarker.nodeCount=17, 
> ConflictIdSorter.graphTime=5100, ConflictIdSorter.topsortTime=8400, 
> ConflictIdSorter.conflictIdCount=12, ConflictIdSorter.conflictIdCycleCount=0, 
> ConflictResolver.totalTime=60300, ConflictResolver.conflictItemCount=17, 
> DefaultDependencyCollector.collectTime=1351500, 
> DefaultDependencyCollector.transformTime=101700}
> [DEBUG] org.apache.maven.plugins:maven-compiler-plugin:jar:3.9.0
> [DEBUG]org.apache.maven.shared:maven-shared-utils:jar:3.3.4:compile
> [DEBUG]   commons-io:commons-io:jar:2.6:compile
> [DEBUG]org.apache.maven.shared:maven-shared-incremental:jar:1.1:compile
> [DEBUG]   
> org.codehaus.plexus:plexus-component-annotations:jar:2.0.0:compile (version 
> managed from default)
> [DEBUG]org.codehaus.plexus:plexus-java:jar:1.1.0:compile
> [DEBUG]   org.ow2.asm:asm:jar:9.2:compile
> [DEBUG]   com.thoughtworks.qdox:qdox:jar:2.0.1:compile (version managed 
> from default)
> [DEBUG]org.codehaus.plexus:plexus-compiler-api:jar:2.9.0:compile
> [DEBUG]   org.codehaus.plexus:plexus-utils:jar:3.3.0:compile
> [DEBUG]org.codehaus.plexus:plexus-compiler-manager:jar:2.9.0:compile
> [DEBUG]org.codehaus.plexus:plexus-compiler-javac:jar:2.9.0:runtime
> [DEBUG] Created new class realm 
> plugin>org.apache.maven.plugins:maven-compiler-plugin:3.9.0--107150504
> [DEBUG] Importing foreign packages into class realm 
> plugin>org.apache.maven.plugins:maven-compiler-plugin:3.9.0--107150504
> [DEBUG]   Imported:  < project>io.sniffy:sniffy:3.1.13-SNAPSHOT
> [DEBUG] Populating class realm 
> plugin>org.apache.maven.plugins:maven-compiler-plugin:3.9.0--107150504
> [DEBUG]   Included: org.apache.maven.plugins:maven-compiler-plugin:jar:3.9.0
> [DEBUG]   Included: org.apache.maven.shared:maven-shared-utils:jar:3.3.4
> [DEBUG]   Included: commons-io:commons-io:jar:2.6
> [DEBUG]   Included: org.apache.maven.shared:maven-shared-incremental:jar:1.1
> [DEBUG]   Included: org.codehaus.plexus:plexus-component-annotations:jar:2.0.0
> [DEBUG]   Included: org.codehaus.plexus:plexus-java:jar:1.1.0
> [DEBUG]   Included: org.ow2.asm:asm:jar:9.2
> [DEBUG]   Included: com.thoughtworks.qdox:qdox:jar:2.0.1
> [DEBUG]   Included: org.codehaus.plexus:plexus-compil

[GitHub] [maven-surefire] Tibor17 commented on pull request #440: [SUREFIRE-1964] Support for method filtering on excludesFile and includesFile

[GitBox]

Tibor17 commented on pull request #440:
URL: https://github.com/apache/maven-surefire/pull/440#issuecomment-1057397696


   @slawekjaranowski 
   Would you pls make the review? Thx


-- 
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.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Updated] (SUREFIRE-2031) Both fields/parameters "includes" and "excludes" should be in target MOJO class. User properties should be unique.

[Tibor Digana (Jira)]

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

Tibor Digana updated SUREFIRE-2031:
---
Summary: Both fields/parameters "includes" and "excludes" should be in 
target MOJO class. User properties should be unique.  (was: Both 
fields/parameters "includes" and "excludes" should be in target MOJO class. 
User names should be unique.)

> Both fields/parameters "includes" and "excludes" should be in target MOJO 
> class. User properties should be unique.
> --
>
> Key: SUREFIRE-2031
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2031
> Project: Maven Surefire
>  Issue Type: Improvement
>  Components: Maven Failsafe Plugin, Maven Surefire Plugin
>Reporter: Tibor Digana
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M6
>
>
> The fields "includes" and "excludes" in the issue SUREFIRE-1964 cannot be 
> tested in the same way because "excludes" appears in {{AbstractSurefireMojo}} 
> but the "includes" is in {{SurefirePlugin}} and {{IntegrationTestMojo}}.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[GitHub] [maven-dependency-plugin] dependabot[bot] opened a new pull request #203: Bump maven-site-plugin from 3.10.0 to 3.11.0

[GitBox]

dependabot[bot] opened a new pull request #203:
URL: https://github.com/apache/maven-dependency-plugin/pull/203


   Bumps [maven-site-plugin](https://github.com/apache/maven-site-plugin) from 
3.10.0 to 3.11.0.
   
   Release notes
   Sourced from https://github.com/apache/maven-site-plugin/releases";>maven-site-plugin's 
releases.
   
   3.11.0
   What's Changed
   
   [MSITE-812] Missing '/' in log when deploying documentation by 
site:stage by https://github.com/aajisaka";>@​aajisaka 
in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/1";>apache/maven-site-plugin#1
   [MSITE-828] Upgrade jetty to recent version. Update to java 1.8 
(required for jetty) by https://github.com/oflebbe";>@​oflebbe in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/3";>apache/maven-site-plugin#3
   MSITE-848 Update sitedescriptor.apt by https://github.com/ctubbsii";>@​ctubbsii in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/13";>apache/maven-site-plugin#13
   MSITE-847: Corrected link to prerequisite maven version. by https://github.com/KathrynN";>@​KathrynN in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/14";>apache/maven-site-plugin#14
   remove info about old version by https://github.com/elharo";>@​elharo in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/19";>apache/maven-site-plugin#19
   update test dependencies by https://github.com/elharo";>@​elharo in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/17";>apache/maven-site-plugin#17
   Only reference current version: created on website by https://github.com/elharo";>@​elharo in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/18";>apache/maven-site-plugin#18
   [MNGSITE-393] assume Maven 3 as default by https://github.com/elharo";>@​elharo in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/20";>apache/maven-site-plugin#20
   add .checkstyle to .gitignore by https://github.com/elharo";>@​elharo in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/22";>apache/maven-site-plugin#22
   remove unused code by https://github.com/elharo";>@​elharo in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/23";>apache/maven-site-plugin#23
   [MSITE-859] update apache commons lang and IO by https://github.com/elharo";>@​elharo in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/25";>apache/maven-site-plugin#25
   [MSITE-757] remove Maven 2 support by https://github.com/elharo";>@​elharo in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/24";>apache/maven-site-plugin#24
   [MSITE-757] drop Maven 2 mention by https://github.com/elharo";>@​elharo in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/26";>apache/maven-site-plugin#26
   docs: use https by https://github.com/elharo";>@​elharo in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/28";>apache/maven-site-plugin#28
   [MSITE-861] remove obsolete dependency by https://github.com/elharo";>@​elharo in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/29";>apache/maven-site-plugin#29
   [MNGSITE-393] remove Maven 1 and 2 info by https://github.com/elharo";>@​elharo in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/30";>apache/maven-site-plugin#30
   Fix script injection example in docs by https://github.com/strkkk";>@​strkkk in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/35";>apache/maven-site-plugin#35
   trivial change by https://github.com/elharo";>@​elharo in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/38";>apache/maven-site-plugin#38
   [MSITE-871] Upgrade Maven Javadoc Plugin in integration tests by https://github.com/mthmulders";>@​mthmulders in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/39";>apache/maven-site-plugin#39
   Bump plexus-archiver from 4.2.4 to 4.2.5 by https://github.com/dependabot";>@​dependabot in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/47";>apache/maven-site-plugin#47
   Bump maven-shared-utils from 3.3.3 to 3.3.4 by https://github.com/dependabot";>@​dependabot in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/50";>apache/maven-site-plugin#50
   Bump slf4jVersion from 1.7.29 to 1.7.31 by https://github.com/dependabot";>@​dependabot in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/54";>apache/maven-site-plugin#54
   Bump slf4jVersion from 1.7.31 to 1.7.32 by https://github.com/dependabot";>@​dependabot in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/58";>apache/maven-site-plugin#58
   Add PR template by https://github.com/slawekjaranowski";>@​slawekjaranowski 
in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/63";>apache/maven-site-plugin#63
   [MSITE-877] Shared GitHub Actions by https://g

[GitHub] [maven-surefire] Tibor17 commented on pull request #460: Add some javadoc and unit tests to includesFile and excludesFile

[GitBox]

Tibor17 commented on pull request #460:
URL: https://github.com/apache/maven-surefire/pull/460#issuecomment-1057528603


   Closed. We continue in #440 .


-- 
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.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-surefire] Tibor17 closed pull request #460: Add some javadoc and unit tests to includesFile and excludesFile

[GitBox]

Tibor17 closed pull request #460:
URL: https://github.com/apache/maven-surefire/pull/460


   


-- 
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.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-surefire] olamy commented on pull request #440: [SUREFIRE-1964] Support for method filtering on excludesFile and includesFile

[GitBox]

olamy commented on pull request #440:
URL: https://github.com/apache/maven-surefire/pull/440#issuecomment-1057541721


   does this include the commits from 
https://github.com/apache/maven-surefire/pull/460?


-- 
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.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-invoker-plugin] dependabot[bot] opened a new pull request #106: Bump maven-project-info-reports-plugin from 3.1.2 to 3.2.2

[GitBox]

dependabot[bot] opened a new pull request #106:
URL: https://github.com/apache/maven-invoker-plugin/pull/106


   Bumps 
[maven-project-info-reports-plugin](https://github.com/apache/maven-project-info-reports-plugin)
 from 3.1.2 to 3.2.2.
   
   Commits
   
   https://github.com/apache/maven-project-info-reports-plugin/commit/ca84755a9d1f58f6bd39e70457fb0d36ce3755c4";>ca84755
 [maven-release-plugin] prepare release 
maven-project-info-reports-plugin-3.2.2
   https://github.com/apache/maven-project-info-reports-plugin/commit/d28e98b8cfedbe179a1017d1a221871919841415";>d28e98b
 [MPIR-413] Plugin repositories defined in project are not used by plugin 
mana...
   https://github.com/apache/maven-project-info-reports-plugin/commit/99bfaef54bbff120317a7adfb7ca9cf0f883075c";>99bfaef
 [MPIR-414] Upgrade Maven Reporting API/Impl to 3.1.0
   https://github.com/apache/maven-project-info-reports-plugin/commit/d1bd10325e2cddf1cdf41f799d1407282006e067";>d1bd103
 Upgrade Maven Site Plugin for IT to 3.11.0
   https://github.com/apache/maven-project-info-reports-plugin/commit/547314f7cd71bad658ecad07a8195e8bd5e5dbcc";>547314f
 Replace usage of deprecated expressions
   https://github.com/apache/maven-project-info-reports-plugin/commit/517662c10b1e817a91c11f8433f3c832f5ad1601";>517662c
 [maven-release-plugin] prepare for next development iteration
   https://github.com/apache/maven-project-info-reports-plugin/commit/8c25c66593f488f6609910b95ae2b246c196d734";>8c25c66
 [maven-release-plugin] prepare release 
maven-project-info-reports-plugin-3.2.1
   https://github.com/apache/maven-project-info-reports-plugin/commit/d85aec37c385d64196f7db5c3c27b400b46032ca";>d85aec3
 [MPIR-412] Dependency report generates non-well-formed output if the POM of 
a...
   https://github.com/apache/maven-project-info-reports-plugin/commit/3c155a8231fac8b018c257d6dbe6bff0902633a2";>3c155a8
 [maven-release-plugin] prepare for next development iteration
   https://github.com/apache/maven-project-info-reports-plugin/commit/b130e220569301f89c58bfd10bf9de36efa20b1e";>b130e22
 [maven-release-plugin] prepare release 
maven-project-info-reports-plugin-3.2.0
   Additional commits viewable in https://github.com/apache/maven-project-info-reports-plugin/compare/maven-project-info-reports-plugin-3.1.2...maven-project-info-reports-plugin-3.2.2";>compare
 view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.apache.maven.plugins:maven-project-info-reports-plugin&package-manager=maven&previous-version=3.1.2&new-version=3.2.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   
   Dependabot commands and options
   
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot merge` will merge this PR after your CI passes on it
   - `@dependabot squash and merge` will squash and merge this PR after your CI 
passes on it
   - `@dependabot cancel merge` will cancel a previously requested merge and 
block automerging
   - `@dependabot reopen` will reopen this PR if it is closed
   - `@dependabot close` will close this PR and stop Dependabot recreating it. 
You can achieve the same result by closing it manually
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   
   
   


-- 
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.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-apache-parent] dependabot[bot] opened a new pull request #71: Bump maven-project-info-reports-plugin from 3.1.2 to 3.2.2

[GitBox]

dependabot[bot] opened a new pull request #71:
URL: https://github.com/apache/maven-apache-parent/pull/71


   Bumps 
[maven-project-info-reports-plugin](https://github.com/apache/maven-project-info-reports-plugin)
 from 3.1.2 to 3.2.2.
   
   Commits
   
   https://github.com/apache/maven-project-info-reports-plugin/commit/ca84755a9d1f58f6bd39e70457fb0d36ce3755c4";>ca84755
 [maven-release-plugin] prepare release 
maven-project-info-reports-plugin-3.2.2
   https://github.com/apache/maven-project-info-reports-plugin/commit/d28e98b8cfedbe179a1017d1a221871919841415";>d28e98b
 [MPIR-413] Plugin repositories defined in project are not used by plugin 
mana...
   https://github.com/apache/maven-project-info-reports-plugin/commit/99bfaef54bbff120317a7adfb7ca9cf0f883075c";>99bfaef
 [MPIR-414] Upgrade Maven Reporting API/Impl to 3.1.0
   https://github.com/apache/maven-project-info-reports-plugin/commit/d1bd10325e2cddf1cdf41f799d1407282006e067";>d1bd103
 Upgrade Maven Site Plugin for IT to 3.11.0
   https://github.com/apache/maven-project-info-reports-plugin/commit/547314f7cd71bad658ecad07a8195e8bd5e5dbcc";>547314f
 Replace usage of deprecated expressions
   https://github.com/apache/maven-project-info-reports-plugin/commit/517662c10b1e817a91c11f8433f3c832f5ad1601";>517662c
 [maven-release-plugin] prepare for next development iteration
   https://github.com/apache/maven-project-info-reports-plugin/commit/8c25c66593f488f6609910b95ae2b246c196d734";>8c25c66
 [maven-release-plugin] prepare release 
maven-project-info-reports-plugin-3.2.1
   https://github.com/apache/maven-project-info-reports-plugin/commit/d85aec37c385d64196f7db5c3c27b400b46032ca";>d85aec3
 [MPIR-412] Dependency report generates non-well-formed output if the POM of 
a...
   https://github.com/apache/maven-project-info-reports-plugin/commit/3c155a8231fac8b018c257d6dbe6bff0902633a2";>3c155a8
 [maven-release-plugin] prepare for next development iteration
   https://github.com/apache/maven-project-info-reports-plugin/commit/b130e220569301f89c58bfd10bf9de36efa20b1e";>b130e22
 [maven-release-plugin] prepare release 
maven-project-info-reports-plugin-3.2.0
   Additional commits viewable in https://github.com/apache/maven-project-info-reports-plugin/compare/maven-project-info-reports-plugin-3.1.2...maven-project-info-reports-plugin-3.2.2";>compare
 view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.apache.maven.plugins:maven-project-info-reports-plugin&package-manager=maven&previous-version=3.1.2&new-version=3.2.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   
   Dependabot commands and options
   
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot merge` will merge this PR after your CI passes on it
   - `@dependabot squash and merge` will squash and merge this PR after your CI 
passes on it
   - `@dependabot cancel merge` will cancel a previously requested merge and 
block automerging
   - `@dependabot reopen` will reopen this PR if it is closed
   - `@dependabot close` will close this PR and stop Dependabot recreating it. 
You can achieve the same result by closing it manually
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   
   
   


-- 
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.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-apache-parent] dependabot[bot] commented on pull request #67: Bump maven-project-info-reports-plugin from 3.1.2 to 3.2.1

[GitBox]

dependabot[bot] commented on pull request #67:
URL: 
https://github.com/apache/maven-apache-parent/pull/67#issuecomment-1057649392


   Superseded by #71.


-- 
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.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-apache-parent] dependabot[bot] closed pull request #67: Bump maven-project-info-reports-plugin from 3.1.2 to 3.2.1

[GitBox]

dependabot[bot] closed pull request #67:
URL: https://github.com/apache/maven-apache-parent/pull/67


   


-- 
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.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-help-plugin] dependabot[bot] opened a new pull request #52: Bump maven-site-plugin from 3.10.0 to 3.11.0

[GitBox]

dependabot[bot] opened a new pull request #52:
URL: https://github.com/apache/maven-help-plugin/pull/52


   Bumps [maven-site-plugin](https://github.com/apache/maven-site-plugin) from 
3.10.0 to 3.11.0.
   
   Release notes
   Sourced from https://github.com/apache/maven-site-plugin/releases";>maven-site-plugin's 
releases.
   
   3.11.0
   What's Changed
   
   [MSITE-812] Missing '/' in log when deploying documentation by 
site:stage by https://github.com/aajisaka";>@​aajisaka 
in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/1";>apache/maven-site-plugin#1
   [MSITE-828] Upgrade jetty to recent version. Update to java 1.8 
(required for jetty) by https://github.com/oflebbe";>@​oflebbe in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/3";>apache/maven-site-plugin#3
   MSITE-848 Update sitedescriptor.apt by https://github.com/ctubbsii";>@​ctubbsii in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/13";>apache/maven-site-plugin#13
   MSITE-847: Corrected link to prerequisite maven version. by https://github.com/KathrynN";>@​KathrynN in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/14";>apache/maven-site-plugin#14
   remove info about old version by https://github.com/elharo";>@​elharo in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/19";>apache/maven-site-plugin#19
   update test dependencies by https://github.com/elharo";>@​elharo in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/17";>apache/maven-site-plugin#17
   Only reference current version: created on website by https://github.com/elharo";>@​elharo in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/18";>apache/maven-site-plugin#18
   [MNGSITE-393] assume Maven 3 as default by https://github.com/elharo";>@​elharo in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/20";>apache/maven-site-plugin#20
   add .checkstyle to .gitignore by https://github.com/elharo";>@​elharo in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/22";>apache/maven-site-plugin#22
   remove unused code by https://github.com/elharo";>@​elharo in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/23";>apache/maven-site-plugin#23
   [MSITE-859] update apache commons lang and IO by https://github.com/elharo";>@​elharo in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/25";>apache/maven-site-plugin#25
   [MSITE-757] remove Maven 2 support by https://github.com/elharo";>@​elharo in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/24";>apache/maven-site-plugin#24
   [MSITE-757] drop Maven 2 mention by https://github.com/elharo";>@​elharo in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/26";>apache/maven-site-plugin#26
   docs: use https by https://github.com/elharo";>@​elharo in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/28";>apache/maven-site-plugin#28
   [MSITE-861] remove obsolete dependency by https://github.com/elharo";>@​elharo in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/29";>apache/maven-site-plugin#29
   [MNGSITE-393] remove Maven 1 and 2 info by https://github.com/elharo";>@​elharo in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/30";>apache/maven-site-plugin#30
   Fix script injection example in docs by https://github.com/strkkk";>@​strkkk in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/35";>apache/maven-site-plugin#35
   trivial change by https://github.com/elharo";>@​elharo in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/38";>apache/maven-site-plugin#38
   [MSITE-871] Upgrade Maven Javadoc Plugin in integration tests by https://github.com/mthmulders";>@​mthmulders in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/39";>apache/maven-site-plugin#39
   Bump plexus-archiver from 4.2.4 to 4.2.5 by https://github.com/dependabot";>@​dependabot in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/47";>apache/maven-site-plugin#47
   Bump maven-shared-utils from 3.3.3 to 3.3.4 by https://github.com/dependabot";>@​dependabot in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/50";>apache/maven-site-plugin#50
   Bump slf4jVersion from 1.7.29 to 1.7.31 by https://github.com/dependabot";>@​dependabot in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/54";>apache/maven-site-plugin#54
   Bump slf4jVersion from 1.7.31 to 1.7.32 by https://github.com/dependabot";>@​dependabot in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/58";>apache/maven-site-plugin#58
   Add PR template by https://github.com/slawekjaranowski";>@​slawekjaranowski 
in https://github-redirect.dependabot.com/apache/maven-site-plugin/pull/63";>apache/maven-site-plugin#63
   [MSITE-877] Shared GitHub Actions by https://github.co

[GitHub] [maven-checkstyle-plugin] dependabot[bot] opened a new pull request #69: Bump maven-project-info-reports-plugin from 3.1.2 to 3.2.2

[GitBox]

dependabot[bot] opened a new pull request #69:
URL: https://github.com/apache/maven-checkstyle-plugin/pull/69


   Bumps 
[maven-project-info-reports-plugin](https://github.com/apache/maven-project-info-reports-plugin)
 from 3.1.2 to 3.2.2.
   
   Commits
   
   https://github.com/apache/maven-project-info-reports-plugin/commit/ca84755a9d1f58f6bd39e70457fb0d36ce3755c4";>ca84755
 [maven-release-plugin] prepare release 
maven-project-info-reports-plugin-3.2.2
   https://github.com/apache/maven-project-info-reports-plugin/commit/d28e98b8cfedbe179a1017d1a221871919841415";>d28e98b
 [MPIR-413] Plugin repositories defined in project are not used by plugin 
mana...
   https://github.com/apache/maven-project-info-reports-plugin/commit/99bfaef54bbff120317a7adfb7ca9cf0f883075c";>99bfaef
 [MPIR-414] Upgrade Maven Reporting API/Impl to 3.1.0
   https://github.com/apache/maven-project-info-reports-plugin/commit/d1bd10325e2cddf1cdf41f799d1407282006e067";>d1bd103
 Upgrade Maven Site Plugin for IT to 3.11.0
   https://github.com/apache/maven-project-info-reports-plugin/commit/547314f7cd71bad658ecad07a8195e8bd5e5dbcc";>547314f
 Replace usage of deprecated expressions
   https://github.com/apache/maven-project-info-reports-plugin/commit/517662c10b1e817a91c11f8433f3c832f5ad1601";>517662c
 [maven-release-plugin] prepare for next development iteration
   https://github.com/apache/maven-project-info-reports-plugin/commit/8c25c66593f488f6609910b95ae2b246c196d734";>8c25c66
 [maven-release-plugin] prepare release 
maven-project-info-reports-plugin-3.2.1
   https://github.com/apache/maven-project-info-reports-plugin/commit/d85aec37c385d64196f7db5c3c27b400b46032ca";>d85aec3
 [MPIR-412] Dependency report generates non-well-formed output if the POM of 
a...
   https://github.com/apache/maven-project-info-reports-plugin/commit/3c155a8231fac8b018c257d6dbe6bff0902633a2";>3c155a8
 [maven-release-plugin] prepare for next development iteration
   https://github.com/apache/maven-project-info-reports-plugin/commit/b130e220569301f89c58bfd10bf9de36efa20b1e";>b130e22
 [maven-release-plugin] prepare release 
maven-project-info-reports-plugin-3.2.0
   Additional commits viewable in https://github.com/apache/maven-project-info-reports-plugin/compare/maven-project-info-reports-plugin-3.1.2...maven-project-info-reports-plugin-3.2.2";>compare
 view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.apache.maven.plugins:maven-project-info-reports-plugin&package-manager=maven&previous-version=3.1.2&new-version=3.2.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   
   Dependabot commands and options
   
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot merge` will merge this PR after your CI passes on it
   - `@dependabot squash and merge` will squash and merge this PR after your CI 
passes on it
   - `@dependabot cancel merge` will cancel a previously requested merge and 
block automerging
   - `@dependabot reopen` will reopen this PR if it is closed
   - `@dependabot close` will close this PR and stop Dependabot recreating it. 
You can achieve the same result by closing it manually
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   
   
   


-- 
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.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-checkstyle-plugin] dependabot[bot] commented on pull request #66: Bump maven-project-info-reports-plugin from 3.1.2 to 3.2.1

[GitBox]

dependabot[bot] commented on pull request #66:
URL: 
https://github.com/apache/maven-checkstyle-plugin/pull/66#issuecomment-1057681564


   Superseded by #69.


-- 
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.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [maven-checkstyle-plugin] dependabot[bot] closed pull request #66: Bump maven-project-info-reports-plugin from 3.1.2 to 3.2.1

[GitBox]

dependabot[bot] closed pull request #66:
URL: https://github.com/apache/maven-checkstyle-plugin/pull/66


   


-- 
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.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: Maven Dependency Plugin - Log4j vulnerabilities

[Jaladi, Venumadhav]

Hi,

Below I am pasting some of the information on the 3 vulnerabilities from
our report.  FYI, I removed the information about the server details and
also trimmed the file path.  This report is generated by the Tenable agent.

Severity scandate Vuln Name Description Summary Fix CVE ID CVS Base
Score Plugin
Output
Critical 3/02/2022 Apache Log4j Unsupported Version Detection According to
its self-reported version number, the installation of Apache Log4j on the
remote host is no longer supported. Log4j reached its end of life prior to
2016.

Lack of support implies that no new security patches for the product will
be released by the vendor. As a result, it is likely to contain security
vulnerabilities. A logging library running on the remote host is no longer
supported. Upgrade to a version of Apache Log4j that is currently supported.

Upgrading to the latest versions for Apache Log4j is highly recommended as
intermediate versions / patches have known high severity vulnerabilities
and the vendor is updating their advisories often as new research and
knowledge about the impact of Log4j is discovered. Refer to
https://logging.apache.org/log4j/2.x/security.html for the latest versions.
  10 Path  :
.../.m2/repository/log4j/log4j/1.2.12/log4j-1.2.12.jar
  Installed version : 1.2.12
Critical 3/02/2022 Apache Log4j 1.x Multiple Vulnerabilities According to
its self-reported version number, the installation of Apache Log4j on the
remote host is 1.x and is no longer supported. Log4j reached its end of
life prior to 2016. Additionally, Log4j 1.x is affected by multiple
vulnerabilities, including :

  - Log4j includes a SocketServer that accepts serialized log events and
deserializes them without verifying whether the objects are allowed or
not. This can provide an attack vector that can be exploited.
(CVE-2019-17571)

  - Improper validation of certificate with host mismatch in Apache Log4j
SMTP appender. This could allow an SMTPS connection to be intercepted
by a man-in-the-middle attack which could leak any log messages sent
through that appender. (CVE-2020-9488)

  - JMSSink uses JNDI in an unprotected manner allowing any application
using the JMSSink to be vulnerable if it is configured to reference an
untrusted site or if the site referenced can be accesseed by the attacker.
(CVE-2022-23302)

Lack of support implies that no new security patches for the product will
be released by the vendor. As a result, it is likely to contain security
vulnerabilities. A logging library running on the remote host has multiple
vulnerabilities. Upgrade to a version of Apache Log4j that is currently
supported.

Upgrading to the latest versions for Apache Log4j is highly recommended as
intermediate versions / patches have known high severity vulnerabilities
and the vendor is updating their advisories often as new research and
knowledge about the impact of Log4j is discovered. Refer to
https://logging.apache.org/log4j/2.x/security.html for the latest
versions. CVE-2019-17571,
CVE-2020-9488, CVE-2022-23302, CVE-2022-23305, CVE-2022-23307 10 Path
: .../.m2/repository/log4j/log4j/1.2.12/log4j-1.2.12.jar
  Installed version : 1.2.12
High 3/02/2022 Apache Log4j 1.2 JMSAppender Remote Code Execution
(CVE-2021-4104) The version of Apache Log4j on the remote host is 1.2. It
is, therefore, affected by a remote code execution vulnerability when
specifically configured to use JMSAppender.

Note that Nessus has not tested for these issues but has instead relied
only on the application's self-reported version number. A package installed
on the remote host is affected by a remote code execution
vulnerability. Upgrade
to Apache Log4j version 2.16.0 or later since 1.x is end of life.

Upgrading to the latest versions for Apache Log4j is highly recommended as
intermediate versions / patches have known high severity vulnerabilities
and the vendor is updating their advisories often as new research and
knowledge about the impact of Log4j is discovered. Refer to
https://logging.apache.org/log4j/2.x/security.html for the latest versions.
CVE-2021-4104 6 Path  :
.../.m2/repository/log4j/log4j/1.2.12/log4j-1.2.12.jar
  Installed version : 1.2.12
  Fixed version : 2.16.0

Thanks,
Venu


On Tue, Mar 1, 2022 at 3:09 PM John Patrick  wrote:

> You might need to raise a bug with your security scanner regarding false
> positives.
>
> So your dependency tree I only see log4j 2.17.1; i.e.
>
> Your Pom
> - org.springframework.boot:spring-boot-starter-web:2.6.4
> -- org.springframework.boot:spring-boot-starter-web:2.6.4
> --- org.springframework.boot:spring-boot-starter:2.6.4
>  org.springframework.boot:spring-boot-starter-logging:2.6.4
> - org.apache.logging.log4j:log4j-to-slf4j:2.17.1
> -- org.apache.logging.log4j:log4j-api:2.17.1
>
> Doing a build "mvn clean install -Dmaven.repo.local=repo"
> Then "find repo -name "*log4j*" -type f", only returns;
> repo/org/apache/logging/log4j/log4j-api/2.17.1/log4j-a

Re: Maven Dependency Plugin - Log4j vulnerabilities

[John Patrick]

You might need to raise a bug with your security scanner regarding false
positives.

So your dependency tree I only see log4j 2.17.1; i.e.

Your Pom
- org.springframework.boot:spring-boot-starter-web:2.6.4
-- org.springframework.boot:spring-boot-starter-web:2.6.4
--- org.springframework.boot:spring-boot-starter:2.6.4
 org.springframework.boot:spring-boot-starter-logging:2.6.4
- org.apache.logging.log4j:log4j-to-slf4j:2.17.1
-- org.apache.logging.log4j:log4j-api:2.17.1

Doing a build "mvn clean install -Dmaven.repo.local=repo"
Then "find repo -name "*log4j*" -type f", only returns;
repo/org/apache/logging/log4j/log4j-api/2.17.1/log4j-api-2.17.1.jar
repo/org/apache/logging/log4j/log4j-api/2.17.1/log4j-api-2.17.1.pom.sha1
repo/org/apache/logging/log4j/log4j-api/2.17.1/log4j-api-2.17.1.pom
repo/org/apache/logging/log4j/log4j-api/2.17.1/log4j-api-2.17.1.jar.sha1
repo/org/apache/logging/log4j/log4j-to-slf4j/2.17.1/log4j-to-slf4j-2.17.1.pom
repo/org/apache/logging/log4j/log4j-to-slf4j/2.17.1/log4j-to-slf4j-2.17.1.pom.sha1
repo/org/apache/logging/log4j/log4j-to-slf4j/2.17.1/log4j-to-slf4j-2.17.1.jar
repo/org/apache/logging/log4j/log4j-to-slf4j/2.17.1/log4j-to-slf4j-2.17.1.jar.sha1
repo/org/apache/logging/log4j/log4j-bom/2.17.1/log4j-bom-2.17.1.pom
repo/org/apache/logging/log4j/log4j-bom/2.17.1/log4j-bom-2.17.1.pom.sha1
repo/org/apache/logging/log4j/log4j/2.17.1/log4j-2.17.1.pom.sha1
repo/org/apache/logging/log4j/log4j/2.17.1/log4j-2.17.1.pom
repo/log4j/log4j/1.2.12/log4j-1.2.12.pom
repo/log4j/log4j/1.2.12/log4j-1.2.12.pom.sha1

What version does the scanner say its found?

John


On Mon, 28 Feb 2022 at 23:15, Juraj Veverka
 wrote:

> Hi David
>
> Just for clarification: we are not relying on the maven dependency plugin
> at runtime. Our runtime is perfectly clear of log4j vulnerabilities.
> The problem is that our security scanners are scanning gitlab runner nodes
> (virtual machines on which we compile and package our application) and
> log4j vulnerability is found there.
>
> Kind regards
> Juraj Veverka
>
> On Mon, Feb 28, 2022 at 1:32 PM Juraj Veverka <
> juraj.veve...@globallogic.com>
> wrote:
>
> > Hi David
> >
> > Many thanks for your email, I really appreciate your reply. This is an
> > isolated example of the problem.
> > https://github.com/jveverka/mvn-dependency-log4j
> > You can find all repro steps there. In case of any questions, feel free
> > to contact me.
> >
> > Kind regards
> > Juraj Veverka
> >
> >
> >
> > On Mon, Feb 28, 2022 at 12:14 PM David Milet 
> > wrote:
> >
> >> Where I work we decided to address log4j vulnerabilities only for
> >> components directly used by the application and actually performing
> logging.
> >> We ignored transitive dependencies and maven plug-ins.
> >> I’m curious about this use case from Venu though, what application would
> >> rely on the maven dependency plugin at runtime? Does it mean you’re
> pulling
> >> maven dependencies after application startup?
> >>
> >> > On Feb 28, 2022, at 03:30, Slawomir Jaranowski <
> s.jaranow...@gmail.com>
> >> wrote:
> >> >
> >> > Hi,
> >> >
> >> > Please provide more information, like plugin, mven, os version.
> >> >
> >> > We also need an example project which reproduces your issue.
> >> > When we can't reproduce we can't help.
> >> >
> >> > pon., 28 lut 2022 o 08:55 Jaladi, Venumadhav
> >> >  napisał(a):
> >> >
> >> >> Hi team,
> >> >>
> >> >> Can I expect any response?  Is this the right email address for my
> >> >> question?
> >> >>
> >> >> Thanks,
> >> >> Venu
> >> >>
> >> >>
> >> >>> On Thu, Feb 24, 2022 at 6:47 AM Jaladi, Venumadhav <
> >> >>> jaladi.venumad...@verizon.com> wrote:
> >> >>>
> >> >>> Hi team,
> >> >>>
> >> >>> We are using the Maven Dependency Plugin in one of our projects and
> >> our
> >> >>> scanning tools are showing multiple vulnerabilities related to Log4j
> >> >>> (CVE-2019-17571, CVE-2020-9488, CVE-2022-23302, CVE-2022-23305,
> >> >>> CVE-2022-23307 and CVE-2021-4104).
> >> >>>
> >> >>> We would  like to know if there are any plans to release a newer
> >> version
> >> >>> of Maven Dependency Plugin with the fixes of these
> >> >>> vulnerabilities(referring to the latest version of Log4j libraries).
> >> If
> >> >>> so, is there any planned date for this release?
> >> >>>
> >> >>> Please let us know any any more information is required.
> >> >>>
> >> >>> Thanks,
> >> >>> Venu
> >> >>>
> >> >>
> >> >
> >> >
> >> > --
> >> > Sławomir Jaranowski
> >>
> >>
> >
> > --
> >
> > Best Regards
> >
> >
> > --
> >
> > Juraj Veverka  | Solution Design Architect
> >
> > M +421 917 521 285
> >
> > www.globallogic.sk  
> >
> >    [image: GLTwitter]
> > 
> > 
> > 
> > 
> >
> > http://www.globallogic.com/Disclai

[jira] [Created] (SUREFIRE-2032) When declare the @Disabled annotation at the class level, skip displayed in other test class

[xie tao (Jira)]

xie tao created SUREFIRE-2032:
-

 Summary: When declare the @Disabled annotation at the class level, 
skip displayed in other test class
 Key: SUREFIRE-2032
 URL: https://issues.apache.org/jira/browse/SUREFIRE-2032
 Project: Maven Surefire
  Issue Type: Bug
  Components: Maven Surefire Plugin
Affects Versions: 3.0.0-M5
Reporter: xie tao
 Attachments: test report.png

When declare the @Disabled annotation at the class level, skip displayed in 
other test class。

junit5: 5.8.2
surefire: 3.0.0-M5

I have a test class like 

{code:java}
public abstract class TagTest {

  @Tag("red")
  public static class RedTest extends TagTest {

  }

  @Disabled
  @Tag("orange")
  public static class OrangeTest extends TagTest {

  }

  @Test
  public void test1() {
// Do Nothing
  }

  @Test
  public void test2() {
// Do Nothing
  }
}
{code}

Run with the following command：
{code}
mvn test -Dgroups="red|orange"
{code}

!test report.png!




--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (SUREFIRE-2032) When declare the @Disabled annotation at the class level, skip displayed in other test class

[xie tao (Jira)]

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

xie tao updated SUREFIRE-2032:
--
Description: 
When declare the @Disabled annotation at the class level, skip displayed in 
other test class。

junit5: 5.8.2
surefire: 3.0.0-M5

I have a test class like
{code:java}
public abstract class TagTest {

  @Tag("red")
  public static class RedTest extends TagTest {

  }

  @Disabled
  @Tag("orange")
  public static class OrangeTest extends TagTest {

  }

  @Test
  public void test1() {
// Do Nothing
  }

  @Test
  public void test2() {
// Do Nothing
  }
}
{code}
Run with the following command：
{code:java}
mvn test -Dgroups="red|orange"
{code}
!test report.png!

 

TagTest$RedTest has only 2 test case.

 

 

  was:
When declare the @Disabled annotation at the class level, skip displayed in 
other test class。

junit5: 5.8.2
surefire: 3.0.0-M5

I have a test class like 

{code:java}
public abstract class TagTest {

  @Tag("red")
  public static class RedTest extends TagTest {

  }

  @Disabled
  @Tag("orange")
  public static class OrangeTest extends TagTest {

  }

  @Test
  public void test1() {
// Do Nothing
  }

  @Test
  public void test2() {
// Do Nothing
  }
}
{code}

Run with the following command：
{code}
mvn test -Dgroups="red|orange"
{code}

!test report.png!



> When declare the @Disabled annotation at the class level, skip displayed in 
> other test class
> 
>
> Key: SUREFIRE-2032
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2032
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 3.0.0-M5
>Reporter: xie tao
>Priority: Major
> Attachments: test report.png
>
>
> When declare the @Disabled annotation at the class level, skip displayed in 
> other test class。
> junit5: 5.8.2
> surefire: 3.0.0-M5
> I have a test class like
> {code:java}
> public abstract class TagTest {
>   @Tag("red")
>   public static class RedTest extends TagTest {
>   }
>   @Disabled
>   @Tag("orange")
>   public static class OrangeTest extends TagTest {
>   }
>   @Test
>   public void test1() {
> // Do Nothing
>   }
>   @Test
>   public void test2() {
> // Do Nothing
>   }
> }
> {code}
> Run with the following command：
> {code:java}
> mvn test -Dgroups="red|orange"
> {code}
> !test report.png!
>  
> TagTest$RedTest has only 2 test case.
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[GitHub] [maven-dependency-plugin] olamy merged pull request #202: [MDEP-795] - Update Jetty to 9.4.45.v20220203

[GitBox]

olamy merged pull request #202:
URL: https://github.com/apache/maven-dependency-plugin/pull/202


   


-- 
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.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: Maven Dependency Plugin - Log4j vulnerabilities

[Piotr Żygieło]

On Thu, 3 Mar 2022 at 08:37, Thomas Matthijs  wrote:
>
> Can confirm this project downloads log4j 1.12.12 for me

As I see it - you confirm something else.

> Failed to read artifact descriptor for log4j:log4j:jar:1.2.12:

Failed to read artifact descriptor for log4j:log4j:jar:1.2.12:
_artifact descriptor_

-- 
Piotrek