[jira] [Comment Edited] (MSOURCES-121) Check for duplicated addition of the same file

[ https://issues.apache.org/jira/browse/MSOURCES-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17749379#comment-17749379 ] Olivier Lamy edited comment on MSOURCES-121 at 8/1/23 12:59 AM: not

[jira] [Commented] (MSOURCES-121) Check for duplicated addition of the same file

[ https://issues.apache.org/jira/browse/MSOURCES-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17749379#comment-17749379 ] Olivier Lamy commented on MSOURCES-121: --- not even sure we need this test now because of

[jira] [Updated] (MSOURCES-139) Typo in exception

[ https://issues.apache.org/jira/browse/MSOURCES-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MSOURCES-139: -- Fix Version/s: 3.3.1 (was: next-release) > Typo in exception >

[jira] [Created] (MSOURCES-141) Check duplication of attached jar should be configurable to not fail when using the build cache

Olivier Lamy created MSOURCES-141: - Summary: Check duplication of attached jar should be configurable to not fail when using the build cache Key: MSOURCES-141 URL:

[jira] [Updated] (MSOURCES-141) Check duplication of attached jar should be configurable to not fail when using the build cache

[ https://issues.apache.org/jira/browse/MSOURCES-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MSOURCES-141: -- Fix Version/s: (was: next-release) > Check duplication of attached jar should be

[jira] [Updated] (MSOURCES-141) Check duplication of attached jar should be configurable to not fail when using the build cache

[ https://issues.apache.org/jira/browse/MSOURCES-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MSOURCES-141: -- Fix Version/s: 3.3.1 > Check duplication of attached jar should be configurable to not fail

[jira] [Created] (MBUILDCACHE-66) Mojo execution can be out of scope

Olivier Lamy created MBUILDCACHE-66: --- Summary: Mojo execution can be out of scope Key: MBUILDCACHE-66 URL: https://issues.apache.org/jira/browse/MBUILDCACHE-66 Project: Maven Build Cache Extension

[jira] [Commented] (SUREFIRE-2097) More configuration for surefire JPMS

[ https://issues.apache.org/jira/browse/SUREFIRE-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17748510#comment-17748510 ] Olivier Lamy commented on SUREFIRE-2097: Well actually it's not exactly the same issue :) The

[jira] [Commented] (MBUILDCACHE-37) Allow disabled-by-default configuration

[ https://issues.apache.org/jira/browse/MBUILDCACHE-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17730774#comment-17730774 ] Olivier Lamy commented on MBUILDCACHE-37: - [~ahus1] good catch. Thanks! > Allow

[jira] [Updated] (MBUILDCACHE-48) Add ability to disable caching on a per-module level

[ https://issues.apache.org/jira/browse/MBUILDCACHE-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MBUILDCACHE-48: Issue Type: Improvement (was: New Feature) > Add ability to disable caching on a

[jira] [Updated] (MBUILDCACHE-57) Configure remote url/remote server id with command line property

[ https://issues.apache.org/jira/browse/MBUILDCACHE-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MBUILDCACHE-57: Issue Type: Improvement (was: New Feature) > Configure remote url/remote server id

[jira] [Updated] (MBUILDCACHE-50) Unsupported phase: null with dependency:analyze in multimodule project

[ https://issues.apache.org/jira/browse/MBUILDCACHE-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MBUILDCACHE-50: Fix Version/s: 1.1.0 (was: 1.0.1) > Unsupported phase: null

[jira] [Closed] (MBUILDCACHE-51) Broken link to maven-build-cache-config.xml template on Getting Started page

[ https://issues.apache.org/jira/browse/MBUILDCACHE-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MBUILDCACHE-51. --- Resolution: Fixed > Broken link to maven-build-cache-config.xml template on Getting

[jira] [Closed] (MBUILDCACHE-42) the CLI maven.build.cache.enabled=false is not honoured

[ https://issues.apache.org/jira/browse/MBUILDCACHE-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MBUILDCACHE-42. --- Resolution: Fixed > the CLI maven.build.cache.enabled=false is not honoured >

[jira] [Updated] (MBUILDCACHE-51) Broken link to maven-build-cache-config.xml template on Getting Started page

[ https://issues.apache.org/jira/browse/MBUILDCACHE-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MBUILDCACHE-51: Fix Version/s: 1.0.1 > Broken link to maven-build-cache-config.xml template on Getting

[jira] [Commented] (MBUILDCACHE-45) Compiled classes are not copied/restored to target, causing higher phase builds to fail

[ https://issues.apache.org/jira/browse/MBUILDCACHE-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727496#comment-17727496 ] Olivier Lamy commented on MBUILDCACHE-45: - strange because I use this on very large project

[jira] [Commented] (MINVOKER-336) .mvn/extensions.xml from main project is used in it projects run

[ https://issues.apache.org/jira/browse/MINVOKER-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17722604#comment-17722604 ] Olivier Lamy commented on MINVOKER-336: --- [~sjaranowski] yes sounds like a good workaround idea.

[jira] [Updated] (MINVOKER-336) .mvn/extensions.xml from main project is used in it projects run

[ https://issues.apache.org/jira/browse/MINVOKER-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MINVOKER-336: -- Description: if the main project contains some extensions in the top directory

[jira] [Created] (MINVOKER-336) .mvn/extensions.xml from main project is used in it projects run

Olivier Lamy created MINVOKER-336: - Summary: .mvn/extensions.xml from main project is used in it projects run Key: MINVOKER-336 URL: https://issues.apache.org/jira/browse/MINVOKER-336 Project: Maven

[jira] [Closed] (MBUILDCACHE-58) save remote not working anymore with Maven 3.9.1

[ https://issues.apache.org/jira/browse/MBUILDCACHE-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MBUILDCACHE-58. --- Resolution: Fixed > save remote not working anymore with Maven 3.9.1 >

[jira] [Closed] (MBUILDCACHE-56) NPE with mojo parameters not declared as fields (prevent any saving of cache)

[ https://issues.apache.org/jira/browse/MBUILDCACHE-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MBUILDCACHE-56. --- Resolution: Fixed > NPE with mojo parameters not declared as fields (prevent any saving

[jira] [Commented] (MNGSITE-517) "Maven before 3.8.8" table under /docs/history.html not rendering correctly

[ https://issues.apache.org/jira/browse/MNGSITE-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17717004#comment-17717004 ] Olivier Lamy commented on MNGSITE-517: -- good catch, this should be fixed now. > "Maven before

[jira] [Closed] (MRESOLVER-355) Programmatic support of webdav put per request

[ https://issues.apache.org/jira/browse/MRESOLVER-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MRESOLVER-355. -- Fix Version/s: (was: 1.9.9) Resolution: Won't Fix let say there are 2 workaround

[jira] [Closed] (MBUILDCACHE-57) Configure remote url/remote server id with command line property

[ https://issues.apache.org/jira/browse/MBUILDCACHE-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MBUILDCACHE-57. --- Resolution: Fixed > Configure remote url/remote server id with command line property >

[jira] [Updated] (MBUILDCACHE-57) Configure remote url/remote server id with command line property

[ https://issues.apache.org/jira/browse/MBUILDCACHE-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MBUILDCACHE-57: Summary: Configure remote url/remote server id with command line property (was:

[jira] [Created] (MRESOLVER-355) Programmatic support of webdav put per request

Olivier Lamy created MRESOLVER-355: -- Summary: Programmatic support of webdav put per request Key: MRESOLVER-355 URL: https://issues.apache.org/jira/browse/MRESOLVER-355 Project: Maven Resolver

[jira] [Comment Edited] (MBUILDCACHE-58) save remote not working anymore with Maven 3.9.1

[ https://issues.apache.org/jira/browse/MBUILDCACHE-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17716076#comment-17716076 ] Olivier Lamy edited comment on MBUILDCACHE-58 at 4/25/23 4:34 AM: --

[jira] [Commented] (MBUILDCACHE-58) save remote not working anymore with Maven 3.9.1

[ https://issues.apache.org/jira/browse/MBUILDCACHE-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17716076#comment-17716076 ] Olivier Lamy commented on MBUILDCACHE-58: - because of webdav disables per default. remote

[jira] [Created] (MBUILDCACHE-58) save remote not working anymore with Maven 3.9.1

Olivier Lamy created MBUILDCACHE-58: --- Summary: save remote not working anymore with Maven 3.9.1 Key: MBUILDCACHE-58 URL: https://issues.apache.org/jira/browse/MBUILDCACHE-58 Project: Maven Build

[jira] [Created] (MBUILDCACHE-57) Configure remote url with command line property

Olivier Lamy created MBUILDCACHE-57: --- Summary: Configure remote url with command line property Key: MBUILDCACHE-57 URL: https://issues.apache.org/jira/browse/MBUILDCACHE-57 Project: Maven Build

[jira] [Closed] (MBUILDCACHE-44) Running duplicate maven phase leads to IllegalStateException and cache miss

[ https://issues.apache.org/jira/browse/MBUILDCACHE-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MBUILDCACHE-44. --- Resolution: Fixed > Running duplicate maven phase leads to IllegalStateException and

[jira] [Updated] (MBUILDCACHE-44) Running duplicate maven phase leads to IllegalStateException and cache miss

[ https://issues.apache.org/jira/browse/MBUILDCACHE-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MBUILDCACHE-44: Fix Version/s: 1.0.1 > Running duplicate maven phase leads to IllegalStateException

[jira] [Closed] (MBUILDCACHE-52) Use current latest release in Getting Started snippet

[ https://issues.apache.org/jira/browse/MBUILDCACHE-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MBUILDCACHE-52. --- Resolution: Fixed fixed with

[jira] [Updated] (MBUILDCACHE-52) Use current latest release in Getting Started snippet

[ https://issues.apache.org/jira/browse/MBUILDCACHE-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MBUILDCACHE-52: Fix Version/s: 1.0.1 > Use current latest release in Getting Started snippet >

[jira] [Assigned] (MBUILDCACHE-52) Use current latest release in Getting Started snippet

[ https://issues.apache.org/jira/browse/MBUILDCACHE-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy reassigned MBUILDCACHE-52: --- Assignee: Olivier Lamy > Use current latest release in Getting Started snippet

[jira] [Commented] (MBUILDCACHE-38) IAE while execution plugin goal

[ https://issues.apache.org/jira/browse/MBUILDCACHE-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17715597#comment-17715597 ] Olivier Lamy commented on MBUILDCACHE-38: - sounds like a duplicate of MBUILDCACHE-50 ? > IAE

[jira] [Updated] (MBUILDCACHE-50) Unsupported phase: null with dependency:analyze in multimodule project

[ https://issues.apache.org/jira/browse/MBUILDCACHE-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MBUILDCACHE-50: Fix Version/s: 1.0.1 > Unsupported phase: null with dependency:analyze in multimodule

[jira] [Commented] (MBUILDCACHE-56) NPE with mojo parameters not declared as fields (prevent any saving of cache)

[ https://issues.apache.org/jira/browse/MBUILDCACHE-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17715444#comment-17715444 ] Olivier Lamy commented on MBUILDCACHE-56: - why people simply not use standard field pattern

[jira] [Comment Edited] (MBUILDCACHE-56) NPE with mojo parameters not declared as fields (prevent any saving of cache)

[ https://issues.apache.org/jira/browse/MBUILDCACHE-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17715444#comment-17715444 ] Olivier Lamy edited comment on MBUILDCACHE-56 at 4/23/23 11:12 AM: ---

[jira] [Commented] (MBUILDCACHE-56) NPE with mojo parameters not declared as fields (prevent any saving of cache)

[ https://issues.apache.org/jira/browse/MBUILDCACHE-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17715443#comment-17715443 ] Olivier Lamy commented on MBUILDCACHE-56: - another case is

[jira] [Commented] (MBUILDCACHE-56) NPE with mojo parameters not declared as fields (prevent any saving of cache)

[ https://issues.apache.org/jira/browse/MBUILDCACHE-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17715438#comment-17715438 ] Olivier Lamy commented on MBUILDCACHE-56: - I will push a PR which will warn to ignore those

[jira] [Comment Edited] (MBUILDCACHE-56) NPE with mojo parameters not declared as fields (prevent any saving of cache)

[ https://issues.apache.org/jira/browse/MBUILDCACHE-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17715435#comment-17715435 ] Olivier Lamy edited comment on MBUILDCACHE-56 at 4/23/23 10:48 AM: ---

[jira] [Commented] (MBUILDCACHE-56) NPE with mojo parameters not declared as fields (prevent any saving of cache)

[ https://issues.apache.org/jira/browse/MBUILDCACHE-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17715435#comment-17715435 ] Olivier Lamy commented on MBUILDCACHE-56: - [~sjaranowski] I know BUT this is not the problem

[jira] [Commented] (MBUILDCACHE-56) NPE with mojo parameters not declared as fields (prevent any saving of cache)

[ https://issues.apache.org/jira/browse/MBUILDCACHE-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17715327#comment-17715327 ] Olivier Lamy commented on MBUILDCACHE-56: - current workaround is to ignore the property:

[jira] [Created] (MBUILDCACHE-56) NPE with mojo parameters not declared as fields (prevent any saving of cache)

Olivier Lamy created MBUILDCACHE-56: --- Summary: NPE with mojo parameters not declared as fields (prevent any saving of cache) Key: MBUILDCACHE-56 URL: https://issues.apache.org/jira/browse/MBUILDCACHE-56

[jira] [Closed] (MBUILDCACHE-46) Add maven.build.cache.remote.enabled parameter

[ https://issues.apache.org/jira/browse/MBUILDCACHE-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MBUILDCACHE-46. --- Resolution: Fixed > Add maven.build.cache.remote.enabled parameter >

[jira] [Updated] (MBUILDCACHE-48) Add ability to disable caching on a per-module level

[ https://issues.apache.org/jira/browse/MBUILDCACHE-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MBUILDCACHE-48: Fix Version/s: 1.0.1 > Add ability to disable caching on a per-module level >

[jira] [Closed] (MBUILDCACHE-48) Add ability to disable caching on a per-module level

[ https://issues.apache.org/jira/browse/MBUILDCACHE-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MBUILDCACHE-48. --- Resolution: Fixed > Add ability to disable caching on a per-module level >

[jira] [Updated] (MNG-7710) Upgrade plexus-utils to 3.5.1

[ https://issues.apache.org/jira/browse/MNG-7710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MNG-7710: -- Summary: Upgrade plexus-utils to 3.5.1 (was: Downgrade plexus-utils to 3.5.1) > Upgrade plexus-utils

[jira] [Updated] (MNG-7710) Downgrade plexus-utils to 3.5.1

[ https://issues.apache.org/jira/browse/MNG-7710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MNG-7710: -- Summary: Downgrade plexus-utils to 3.5.1 (was: Downgrade plexus-utils to 3.3.1) > Downgrade

[jira] [Closed] (SUREFIRE-2155) system property java.io.tmpdir set too late

[ https://issues.apache.org/jira/browse/SUREFIRE-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed SUREFIRE-2155. -- Resolution: Won't Fix just using argLine fixed the problem > system property

[jira] [Closed] (SUREFIRE-2150) Upgrade Maven parent 39

[ https://issues.apache.org/jira/browse/SUREFIRE-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed SUREFIRE-2150. -- Resolution: Fixed done > Upgrade Maven parent 39 > --- > >

[jira] [Created] (SUREFIRE-2155) system property java.io.tmpdir set too late

Olivier Lamy created SUREFIRE-2155: -- Summary: system property java.io.tmpdir set too late Key: SUREFIRE-2155 URL: https://issues.apache.org/jira/browse/SUREFIRE-2155 Project: Maven Surefire

[jira] [Closed] (MENFORCER-468) Enforcer plugin 3.2.1 concurrency issue

[ https://issues.apache.org/jira/browse/MENFORCER-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MENFORCER-468. -- Assignee: Olivier Lamy Resolution: Won't Fix Correct.I agree. FTR probably fixed with

[jira] [Created] (MBUILDCACHE-46) Add maven.build.cache.remote.enabled parameter

Olivier Lamy created MBUILDCACHE-46: --- Summary: Add maven.build.cache.remote.enabled parameter Key: MBUILDCACHE-46 URL: https://issues.apache.org/jira/browse/MBUILDCACHE-46 Project: Maven Build Cache

[jira] [Updated] (MBUILDCACHE-42) the CLI maven.build.cache.enabled=false is not honoured

[ https://issues.apache.org/jira/browse/MBUILDCACHE-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MBUILDCACHE-42: Description: related to BUILDCACHE-38 using something such {code} mvn install

[jira] [Created] (MBUILDCACHE-42) the CLI maven.build.cache.enabled=false is not honoured

Olivier Lamy created MBUILDCACHE-42: --- Summary: the CLI maven.build.cache.enabled=false is not honoured Key: MBUILDCACHE-42 URL: https://issues.apache.org/jira/browse/MBUILDCACHE-42 Project: Maven

[jira] [Closed] (MBUILDCACHE-37) Allow disabled-by-default configuration

[ https://issues.apache.org/jira/browse/MBUILDCACHE-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MBUILDCACHE-37. --- Assignee: Olivier Lamy Resolution: Fixed PR merged. Thanks for the contribution.

[jira] [Created] (SUREFIRE-2150) Upgrade Maven parent 39

Olivier Lamy created SUREFIRE-2150: -- Summary: Upgrade Maven parent 39 Key: SUREFIRE-2150 URL: https://issues.apache.org/jira/browse/SUREFIRE-2150 Project: Maven Surefire Issue Type: Bug

[jira] [Comment Edited] (MENFORCER-468) Enforcer plugin 3.2.1 concurrency issue

[ https://issues.apache.org/jira/browse/MENFORCER-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17687692#comment-17687692 ] Olivier Lamy edited comment on MENFORCER-468 at 2/13/23 3:23 AM: -

[jira] [Commented] (MENFORCER-468) Enforcer plugin 3.2.1 concurrency issue

[ https://issues.apache.org/jira/browse/MENFORCER-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17687692#comment-17687692 ] Olivier Lamy commented on MENFORCER-468: looks to have only with branch jetty-12.0.x mvn

[jira] [Commented] (MBUILDCACHE-38) IAE while execution plugin goal

[ https://issues.apache.org/jira/browse/MBUILDCACHE-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17685714#comment-17685714 ] Olivier Lamy commented on MBUILDCACHE-38: - yup this makes the cache unusable if you add any

[jira] [Updated] (MBUILDCACHE-38) IAE while execution plugin goal

[ https://issues.apache.org/jira/browse/MBUILDCACHE-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MBUILDCACHE-38: Priority: Critical (was: Major) > IAE while execution plugin goal >

[jira] [Closed] (SUREFIRE-2065) Test Reports Inconsistencies with Parameterized and junit4

[ https://issues.apache.org/jira/browse/SUREFIRE-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed SUREFIRE-2065. -- Assignee: Olivier Lamy Resolution: Fixed PR merged. Thanks > Test Reports

[jira] [Updated] (SUREFIRE-2065) Test Reports Inconsistencies with Parameterized and junit4

[ https://issues.apache.org/jira/browse/SUREFIRE-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated SUREFIRE-2065: --- Fix Version/s: 3.0.0-M9 > Test Reports Inconsistencies with Parameterized and junit4 >

[jira] [Updated] (MENFORCER-468) Enforcer plugin 3.2.1 concurrency issue

[ https://issues.apache.org/jira/browse/MENFORCER-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MENFORCER-468: --- Affects Version/s: 3.2.1 > Enforcer plugin 3.2.1 concurrency issue >

[jira] [Created] (MENFORCER-468) Enforcer plugin 3.2.1 concurrency issue

Olivier Lamy created MENFORCER-468: -- Summary: Enforcer plugin 3.2.1 concurrency issue Key: MENFORCER-468 URL: https://issues.apache.org/jira/browse/MENFORCER-468 Project: Maven Enforcer Plugin

[jira] [Closed] (SUREFIRE-2095) Fork crash doesn't fail build with -Dmaven.test.failure.ignore=true when run with failsafe

[ https://issues.apache.org/jira/browse/SUREFIRE-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed SUREFIRE-2095. -- Resolution: Fixed PR merged thanks a lot. > Fork crash doesn't fail build with

[jira] [Commented] (MCOMPILER-481) JPMS Regression: cannot access (requires static module not include anymore)

[ https://issues.apache.org/jira/browse/MCOMPILER-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17682326#comment-17682326 ] Olivier Lamy commented on MCOMPILER-481: [~cstamas] good catch!! maybe you can lock the

[jira] [Closed] (MCOMPILER-503) Unexpected dependency resolution of `annotationProcessorPaths`

[ https://issues.apache.org/jira/browse/MCOMPILER-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MCOMPILER-503. -- Resolution: Fixed PR merged. Thanks! > Unexpected dependency resolution of

[jira] [Assigned] (MCOMPILER-503) Unexpected dependency resolution of `annotationProcessorPaths`

[ https://issues.apache.org/jira/browse/MCOMPILER-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy reassigned MCOMPILER-503: -- Assignee: Olivier Lamy > Unexpected dependency resolution of

[jira] [Updated] (MCOMPILER-503) Unexpected dependency resolution of `annotationProcessorPaths`

[ https://issues.apache.org/jira/browse/MCOMPILER-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MCOMPILER-503: --- Fix Version/s: 3.11.0 > Unexpected dependency resolution of `annotationProcessorPaths` >

[jira] [Commented] (MCOMPILER-525) Incremental recompile incorrect detection of dependency change

[ https://issues.apache.org/jira/browse/MCOMPILER-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17681804#comment-17681804 ] Olivier Lamy commented on MCOMPILER-525: duplicate of MCOMPILER-517 > Incremental recompile

[jira] [Updated] (MCOMPILER-517) store compilation time of modules to avoid not needed compile when using install

[ https://issues.apache.org/jira/browse/MCOMPILER-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MCOMPILER-517: --- Description: when using `install` m-compiler-p detects artifacts of the reactor as new

[jira] [Created] (MCOMPILER-517) store compilation time of modules to avoid not needed compile when using install

Olivier Lamy created MCOMPILER-517: -- Summary: store compilation time of modules to avoid not needed compile when using install Key: MCOMPILER-517 URL: https://issues.apache.org/jira/browse/MCOMPILER-517

[jira] [Updated] (MNG-7642) 4.0.0-alpha 3 not compatible with flatten plugin

[ https://issues.apache.org/jira/browse/MNG-7642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MNG-7642: -- Description: when using flatten-m-p {code} [WARNING]

[jira] [Created] (MNG-7642) 4.0.0-alpha 3 not compatible with flatten plugin

Olivier Lamy created MNG-7642: - Summary: 4.0.0-alpha 3 not compatible with flatten plugin Key: MNG-7642 URL: https://issues.apache.org/jira/browse/MNG-7642 Project: Maven Issue Type: Bug

[jira] [Updated] (MSHARED-1157) Bump maven-shared-components from 36 to 39

[ https://issues.apache.org/jira/browse/MSHARED-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MSHARED-1157: -- Summary: Bump maven-shared-components from 36 to 39 (was: Bump maven-shared-components from

[jira] [Closed] (MINVOKER-312) Upgrade Groovy to 4.x

[ https://issues.apache.org/jira/browse/MINVOKER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MINVOKER-312. - > Upgrade Groovy to 4.x > - > > Key: MINVOKER-312 >

[jira] [Updated] (MINVOKER-307) invoker should also support the @{ } syntax like the surefire plugin

[ https://issues.apache.org/jira/browse/MINVOKER-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MINVOKER-307: -- Fix Version/s: next-version (was: 3.4.0) > invoker should also

[jira] [Resolved] (MINVOKER-312) Upgrade Groovy to 4.x

[ https://issues.apache.org/jira/browse/MINVOKER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy resolved MINVOKER-312. --- Resolution: Fixed > Upgrade Groovy to 4.x > - > > Key:

[jira] [Commented] (MCOMPILER-515) Plugin is NOT incremental, so let it go

[ https://issues.apache.org/jira/browse/MCOMPILER-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646352#comment-17646352 ] Olivier Lamy commented on MCOMPILER-515: -1 I'm happy to not have to recompile everything all

[jira] [Assigned] (MINVOKER-312) Upgrade Groovy to 4.x

[ https://issues.apache.org/jira/browse/MINVOKER-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy reassigned MINVOKER-312: - Assignee: Olivier Lamy > Upgrade Groovy to 4.x > - > >

[jira] [Commented] (MRESOLVER-298) javax.inject should not be provided or optional

[ https://issues.apache.org/jira/browse/MRESOLVER-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641119#comment-17641119 ] Olivier Lamy commented on MRESOLVER-298: code is here

[jira] [Created] (MRESOLVER-298) javax.inject should not be provided or optional

Olivier Lamy created MRESOLVER-298: -- Summary: javax.inject should not be provided or optional Key: MRESOLVER-298 URL: https://issues.apache.org/jira/browse/MRESOLVER-298 Project: Maven Resolver

[jira] [Commented] (MNG-7316) MavenProject.getAttachedArtifacts() regression with 3.8.1

[ https://issues.apache.org/jira/browse/MNG-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17640307#comment-17640307 ] Olivier Lamy commented on MNG-7316: --- frankly looking at the commons plugin code, it looks they should fix

[jira] [Commented] (MSHARED-1158) DependencyCollectorBuilder more configurable

[ https://issues.apache.org/jira/browse/MSHARED-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17634659#comment-17634659 ] Olivier Lamy commented on MSHARED-1158: --- [~laeubi] yes possible but default still stay the same.

[jira] [Updated] (MSHARED-1158) DependencyCollectorBuilder more configurable

[ https://issues.apache.org/jira/browse/MSHARED-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MSHARED-1158: -- Summary: DependencyCollectorBuilder more configurable (was:

[jira] [Created] (MSHARED-1158) DefaultDependencyCollectorBuilder not configurable enough

Olivier Lamy created MSHARED-1158: - Summary: DefaultDependencyCollectorBuilder not configurable enough Key: MSHARED-1158 URL: https://issues.apache.org/jira/browse/MSHARED-1158 Project: Maven Shared

[jira] [Resolved] (MRELEASE-1104) stage goal doesn’t use stagingRepository parameter

[ https://issues.apache.org/jira/browse/MRELEASE-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy resolved MRELEASE-1104. Resolution: Fixed > stage goal doesn’t use stagingRepository parameter >

[jira] [Commented] (MRELEASE-1104) stage goal doesn’t use stagingRepository parameter

[ https://issues.apache.org/jira/browse/MRELEASE-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608595#comment-17608595 ] Olivier Lamy commented on MRELEASE-1104: PR https://github.com/apache/maven-release/pull/151

[jira] [Updated] (MRELEASE-1105) when running with mvnDebug the spawned process in in debug mode as well

[ https://issues.apache.org/jira/browse/MRELEASE-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MRELEASE-1105: --- Fix Version/s: 3.0.0-M7 > when running with mvnDebug the spawned process in in debug mode

[jira] [Created] (MRELEASE-1105) when running with mvnDebug the spawned process in in debug mode as well

Olivier Lamy created MRELEASE-1105: -- Summary: when running with mvnDebug the spawned process in in debug mode as well Key: MRELEASE-1105 URL: https://issues.apache.org/jira/browse/MRELEASE-1105

[jira] [Updated] (MRELEASE-1104) stage goal doesn’t use stagingRepository parameter

[ https://issues.apache.org/jira/browse/MRELEASE-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MRELEASE-1104: --- Priority: Blocker (was: Major) > stage goal doesn’t use stagingRepository parameter >

[jira] [Commented] (MRELEASE-1104) stage goal doesn’t use stagingRepository parameter

[ https://issues.apache.org/jira/browse/MRELEASE-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608033#comment-17608033 ] Olivier Lamy commented on MRELEASE-1104: it looks bug happen when using both arguments and

[jira] [Created] (MRELEASE-1104) stage goal doesn’t use stagingRepository parameter

Olivier Lamy created MRELEASE-1104: -- Summary: stage goal doesn’t use stagingRepository parameter Key: MRELEASE-1104 URL: https://issues.apache.org/jira/browse/MRELEASE-1104 Project: Maven Release

[jira] [Updated] (MRELEASE-1103) decryption of server password in settings.xml failed (works with 2.5.3)

[ https://issues.apache.org/jira/browse/MRELEASE-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MRELEASE-1103: --- Priority: Blocker (was: Major) > decryption of server password in settings.xml failed

[jira] [Commented] (SUREFIRE-2116) Surefire release notes page gives Page Not Found error

[ https://issues.apache.org/jira/browse/SUREFIRE-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17607974#comment-17607974 ] Olivier Lamy commented on SUREFIRE-2116: Just noted the releases link (on the left side) is

[jira] [Commented] (SUREFIRE-2116) Surefire release notes page gives Page Not Found error

[ https://issues.apache.org/jira/browse/SUREFIRE-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17607721#comment-17607721 ] Olivier Lamy commented on SUREFIRE-2116: TBH this means running all the tests which means

[jira] [Closed] (MRRESOURCES-122) Java 8 as minimum

[ https://issues.apache.org/jira/browse/MRRESOURCES-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MRRESOURCES-122. Resolution: Fixed > Java 8 as minimum > - > > Key:

<    1   2   3   4   5   6   7   8   9   10   >