[jira] (MNG-8481) NamedLockFactory discovery stopped working on Maven 3.9.9 and Named Locks 2.0.5

[ https://issues.apache.org/jira/browse/MNG-8481 ] Elias Balasis deleted comment on MNG-8481: was (Author: eliasbalasis): This is now working. [~cstamas], is there a convenient way to identify the compatible resolver version ? > NamedLockFac

[jira] [Commented] (MNG-8481) NamedLockFactory discovery stopped working on Maven 3.9.9 and Named Locks 2.0.5

[ https://issues.apache.org/jira/browse/MNG-8481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17909948#comment-17909948 ] Elias Balasis commented on MNG-8481: This is now working. > NamedLockFactory discovery

[jira] [Commented] (MNG-7868) "Could not acquire lock(s)" error in concurrent maven builds

[ https://issues.apache.org/jira/browse/MNG-7868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17909886#comment-17909886 ] Elias Balasis commented on MNG-7868: Thanks [~michael-o], it all makes perfect sense no

[jira] [Commented] (MNG-7868) "Could not acquire lock(s)" error in concurrent maven builds

[ https://issues.apache.org/jira/browse/MNG-7868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17909589#comment-17909589 ] Elias Balasis commented on MNG-7868: If it helps, I can confirm that use of {{aether.sy

[jira] [Commented] (MNG-8481) NamedLockFactory discovery stopped working on Maven 3.9.9 and Named Locks 2.0.5

[ https://issues.apache.org/jira/browse/MNG-8481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17909577#comment-17909577 ] Elias Balasis commented on MNG-8481: This is now working. [~cstamas], is there a conve

[jira] [Commented] (MNG-8481) NamedLockFactory discovery stopped working on Maven 3.9.9 and Named Locks 2.0.5

[ https://issues.apache.org/jira/browse/MNG-8481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17909573#comment-17909573 ] Elias Balasis commented on MNG-8481: Thanks [~cstamas]. This makes perfect sense. I wa

[jira] [Created] (MNG-8481) NamedLockFactory discovery stopped working on Maven 3.9.9 and Named Locks 2.0.5

Elias Balasis created MNG-8481: -- Summary: NamedLockFactory discovery stopped working on Maven 3.9.9 and Named Locks 2.0.5 Key: MNG-8481 URL: https://issues.apache.org/jira/browse/MNG-8481 Project: Maven

[jira] [Commented] (MRELEASE-1151) Maven Release Plugin fails to adjust version (regression in 3.1.0)

[ https://issues.apache.org/jira/browse/MRELEASE-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864691#comment-17864691 ] Elias Balasis commented on MRELEASE-1151: - I think I understand now. The prob

[jira] [Comment Edited] (MRELEASE-1151) Maven Release Plugin fails to adjust version (regression in 3.1.0)

[ https://issues.apache.org/jira/browse/MRELEASE-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864023#comment-17864023 ] Elias Balasis edited comment on MRELEASE-1151 at 7/9/24 6:19 AM: ---

[jira] [Comment Edited] (MRELEASE-1151) Maven Release Plugin fails to adjust version (regression in 3.1.0)

[ https://issues.apache.org/jira/browse/MRELEASE-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864023#comment-17864023 ] Elias Balasis edited comment on MRELEASE-1151 at 7/9/24 6:19 AM: ---

[jira] [Commented] (MRELEASE-1151) Maven Release Plugin fails to adjust version (regression in 3.1.0)

[ https://issues.apache.org/jira/browse/MRELEASE-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864023#comment-17864023 ] Elias Balasis commented on MRELEASE-1151: - I haven't tried it yet, but the rel

[jira] [Comment Edited] (MRELEASE-1151) Maven Release Plugin fails to adjust version (regression in 3.1.0)

[ https://issues.apache.org/jira/browse/MRELEASE-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864002#comment-17864002 ] Elias Balasis edited comment on MRELEASE-1151 at 7/9/24 4:18 AM: ---

[jira] [Commented] (MRELEASE-1151) Maven Release Plugin fails to adjust version (regression in 3.1.0)

[ https://issues.apache.org/jira/browse/MRELEASE-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864002#comment-17864002 ] Elias Balasis commented on MRELEASE-1151: - Great, Jenkins 2.466 has been relea

[jira] [Commented] (MRESOURCES-273) Filtering of Maven properties with long names is not working after transition from 2.6 to 3.2.0

[ https://issues.apache.org/jira/browse/MRESOURCES-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264926#comment-17264926 ] Elias Balasis commented on MRESOURCES-273: -- Thanks for clarifying, it would

[jira] [Commented] (MRESOURCES-273) Filtering of Maven properties with long names is not working after transition from 2.6 to 3.2.0

[ https://issues.apache.org/jira/browse/MRESOURCES-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264825#comment-17264825 ] Elias Balasis commented on MRESOURCES-273: -- This works with 2.6 In our organ

[jira] [Comment Edited] (MRESOURCES-273) Filtering of Maven properties with long names is not working after transition from 2.6 to 3.2.0

[ https://issues.apache.org/jira/browse/MRESOURCES-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264789#comment-17264789 ] Elias Balasis edited comment on MRESOURCES-273 at 1/14/21, 11:21 AM: --

[jira] [Comment Edited] (MRESOURCES-273) Filtering of Maven properties with long names is not working after transition from 2.6 to 3.2.0

[ https://issues.apache.org/jira/browse/MRESOURCES-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264789#comment-17264789 ] Elias Balasis edited comment on MRESOURCES-273 at 1/14/21, 11:19 AM: --

[jira] [Commented] (MRESOURCES-273) Filtering of Maven properties with long names is not working after transition from 2.6 to 3.2.0

[ https://issues.apache.org/jira/browse/MRESOURCES-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264789#comment-17264789 ] Elias Balasis commented on MRESOURCES-273: -- Clone Github repository at [htt

[jira] [Updated] (MRESOURCES-273) Filtering of Maven properties with long names is not working after transition from 2.6 to 3.2.0

[ https://issues.apache.org/jira/browse/MRESOURCES-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elias Balasis updated MRESOURCES-273: - Affects Version/s: 3.2.0 > Filtering of Maven properties with long names is not worki

[jira] [Updated] (MRESOURCES-273) Filtering of Maven properties with long names is not working after transition from 2.6 to 3.2.0

[ https://issues.apache.org/jira/browse/MRESOURCES-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elias Balasis updated MRESOURCES-273: - Component/s: filtering > Filtering of Maven properties with long names is not working

[jira] [Created] (MRESOURCES-273) Filtering of Maven properties with long names is not working after transition from 2.6 to 3.2.0

Elias Balasis created MRESOURCES-273: Summary: Filtering of Maven properties with long names is not working after transition from 2.6 to 3.2.0 Key: MRESOURCES-273 URL: https://issues.apache.org/jira/browse/MRE

[jira] [Comment Edited] (SUREFIRE-1346) surefire-reports overwrite each other when using reuseForks=false

[ https://issues.apache.org/jira/browse/SUREFIRE-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078153#comment-16078153 ] Elias Balasis edited comment on SUREFIRE-1346 at 7/7/17 3:08 PM:

[jira] [Comment Edited] (SUREFIRE-1346) surefire-reports overwrite each other when using reuseForks=false

[ https://issues.apache.org/jira/browse/SUREFIRE-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078153#comment-16078153 ] Elias Balasis edited comment on SUREFIRE-1346 at 7/7/17 2:30 PM:

[jira] [Comment Edited] (SUREFIRE-1346) surefire-reports overwrite each other when using reuseForks=false

[ https://issues.apache.org/jira/browse/SUREFIRE-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078153#comment-16078153 ] Elias Balasis edited comment on SUREFIRE-1346 at 7/7/17 2:27 PM:

[jira] [Comment Edited] (SUREFIRE-1346) surefire-reports overwrite each other when using reuseForks=false

[ https://issues.apache.org/jira/browse/SUREFIRE-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078153#comment-16078153 ] Elias Balasis edited comment on SUREFIRE-1346 at 7/7/17 2:27 PM:

[jira] [Comment Edited] (SUREFIRE-1346) surefire-reports overwrite each other when using reuseForks=false

[ https://issues.apache.org/jira/browse/SUREFIRE-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078153#comment-16078153 ] Elias Balasis edited comment on SUREFIRE-1346 at 7/7/17 2:25 PM:

[jira] [Comment Edited] (SUREFIRE-1346) surefire-reports overwrite each other when using reuseForks=false

[ https://issues.apache.org/jira/browse/SUREFIRE-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078153#comment-16078153 ] Elias Balasis edited comment on SUREFIRE-1346 at 7/7/17 2:25 PM:

[jira] [Commented] (SUREFIRE-1346) surefire-reports overwrite each other when using reuseForks=false

[ https://issues.apache.org/jira/browse/SUREFIRE-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078153#comment-16078153 ] Elias Balasis commented on SUREFIRE-1346: - Following discussion under SUREFIRE-

[jira] [Commented] (SUREFIRE-875) testng-results contains only last suite execute in forkmode = always

[ https://issues.apache.org/jira/browse/SUREFIRE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078137#comment-16078137 ] Elias Balasis commented on SUREFIRE-875: Following discussion under [https://git

[jira] [Commented] (SUREFIRE-1346) surefire-reports overwrite each other when using reuseForks=false

[ https://issues.apache.org/jira/browse/SUREFIRE-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16077731#comment-16077731 ] Elias Balasis commented on SUREFIRE-1346: - More info is now provided under SURE

[jira] [Commented] (SUREFIRE-875) testng-results contains only last suite execute in forkmode = always

[ https://issues.apache.org/jira/browse/SUREFIRE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071818#comment-16071818 ] Elias Balasis commented on SUREFIRE-875: Thanks [~tibor17], I noticed your comm

[jira] [Commented] (SUREFIRE-875) testng-results contains only last suite execute in forkmode = always

[ https://issues.apache.org/jira/browse/SUREFIRE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071573#comment-16071573 ] Elias Balasis commented on SUREFIRE-875: Yes, that's exactly what I do but manua

[jira] [Commented] (SUREFIRE-875) testng-results contains only last suite execute in forkmode = always

[ https://issues.apache.org/jira/browse/SUREFIRE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16070064#comment-16070064 ] Elias Balasis commented on SUREFIRE-875: I could solve the problem only by expli