[jira] [Closed] (MNG-7922) Remove any "change detection" from installation

[ https://issues.apache.org/jira/browse/MNG-7922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MNG-7922. Resolution: Fixed > Remove any "change detection" from installation >

[jira] [Created] (MNG-7922) Remove any "smartness" from installation

Tamas Cservenak created MNG-7922: Summary: Remove any "smartness" from installation Key: MNG-7922 URL: https://issues.apache.org/jira/browse/MNG-7922 Project: Maven Issue Type: Task

[jira] [Assigned] (MNG-7922) Remove any "change detection" from installation

[ https://issues.apache.org/jira/browse/MNG-7922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MNG-7922: Assignee: Tamas Cservenak > Remove any "change detection" from installation >

[jira] [Updated] (MNG-7922) Remove any "smartness" from installation

[ https://issues.apache.org/jira/browse/MNG-7922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-7922: - Description: This basically undoes MNG-4368. No code change needed, as this is coming with

[jira] [Closed] (MNG-7909) Upgrade to Resolver 2.0.0-alpha-1

[ https://issues.apache.org/jira/browse/MNG-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MNG-7909. Resolution: Fixed > Upgrade to Resolver 2.0.0-alpha-1 > - > >

[jira] [Commented] (MRESOLVER-425) Session should carry VersionScheme?

[ https://issues.apache.org/jira/browse/MRESOLVER-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783787#comment-17783787 ] Tamas Cservenak commented on MRESOLVER-425: --- Moved off 2.0.0, consider maybe later, but IMO

[jira] [Updated] (MRESOLVER-425) Session should carry VersionScheme?

[ https://issues.apache.org/jira/browse/MRESOLVER-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-425: -- Fix Version/s: (was: 2.0.0) > Session should carry VersionScheme? >

[jira] [Assigned] (MRESOLVER-424) Make DependencyGraphDumper extensible

[ https://issues.apache.org/jira/browse/MRESOLVER-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MRESOLVER-424: - Assignee: Tamas Cservenak > Make DependencyGraphDumper extensible >

[jira] [Assigned] (MRESOLVER-426) Move some HTTP configuration properties from transport-http

[ https://issues.apache.org/jira/browse/MRESOLVER-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MRESOLVER-426: - Assignee: Tamas Cservenak > Move some HTTP configuration properties from

[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=17780643#comment-17780643 ] Tamas Cservenak commented on MNG-7868: -- [~joewitt] If you can "afford" (unsure how big the build is)

[jira] [Comment Edited] (MJAVADOC-769) javadoc plugin can not deal with transitive filename based modules

[ https://issues.apache.org/jira/browse/MJAVADOC-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17780652#comment-17780652 ] Tamas Cservenak edited comment on MJAVADOC-769 at 10/28/23 8:21 PM:

[jira] [Comment Edited] (MJAVADOC-769) javadoc plugin can not deal with transitive filename based modules

[ https://issues.apache.org/jira/browse/MJAVADOC-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17780652#comment-17780652 ] Tamas Cservenak edited comment on MJAVADOC-769 at 10/28/23 8:20 PM:

[jira] [Comment Edited] (MJAVADOC-769) javadoc plugin can not deal with transitive filename based modules

[ https://issues.apache.org/jira/browse/MJAVADOC-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17780652#comment-17780652 ] Tamas Cservenak edited comment on MJAVADOC-769 at 10/28/23 8:37 PM:

[jira] [Closed] (MINDEXER-207) RR backend should handle 404 gracefully

[ https://issues.apache.org/jira/browse/MINDEXER-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MINDEXER-207. Resolution: Fixed > RR backend should handle 404 gracefully >

[jira] [Assigned] (MINDEXER-207) RR backend should handle 404 gracefully

[ https://issues.apache.org/jira/browse/MINDEXER-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MINDEXER-207: Assignee: Tamas Cservenak > RR backend should handle 404 gracefully >

[jira] [Commented] (MINDEXER-206) Search Backend SMO and RR handle different Artifact.extension

[ https://issues.apache.org/jira/browse/MINDEXER-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17781163#comment-17781163 ] Tamas Cservenak commented on MINDEXER-206: -- Counter arguments: * RR backend is really about

[jira] [Created] (MINDEXER-207) RR backend should handle 404 gracefully

Tamas Cservenak created MINDEXER-207: Summary: RR backend should handle 404 gracefully Key: MINDEXER-207 URL: https://issues.apache.org/jira/browse/MINDEXER-207 Project: Maven Indexer

[jira] [Commented] (MINDEXER-206) Search Backend SMO and RR handle different Artifact.extension

[ https://issues.apache.org/jira/browse/MINDEXER-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17781166#comment-17781166 ] Tamas Cservenak commented on MINDEXER-206: -- Maybe the solution is to reveal backend

[jira] [Updated] (MRESOLVER-391) Scope mediation improvements

[ https://issues.apache.org/jira/browse/MRESOLVER-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-391: -- Description: Original issue description was: "As per MNG-5988: if an artifact in

[jira] [Updated] (MRESOLVER-391) Scope mediation improvements

[ https://issues.apache.org/jira/browse/MRESOLVER-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-391: -- Description: Original issue description was: "As per MNG-5988: if an artifact in

[jira] [Updated] (MRESOLVER-391) Scope mediation improvements

[ https://issues.apache.org/jira/browse/MRESOLVER-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-391: -- Description: Original issue description was: "As per MNG-5988: if an artifact in

[jira] [Updated] (MRESOLVER-391) Scope mediation improvements

[ https://issues.apache.org/jira/browse/MRESOLVER-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-391: -- Description: Original issue description was: "As per MNG-5988: if an artifact in

[jira] [Closed] (MINDEXER-205) Align Search API backend factories

[ https://issues.apache.org/jira/browse/MINDEXER-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MINDEXER-205. Assignee: Tamas Cservenak Resolution: Fixed > Align Search API backend factories >

[jira] [Created] (MRESOLVER-426) Move some HTTP configuration properties from transport-http

Tamas Cservenak created MRESOLVER-426: - Summary: Move some HTTP configuration properties from transport-http Key: MRESOLVER-426 URL: https://issues.apache.org/jira/browse/MRESOLVER-426 Project:

[jira] [Created] (MRESOLVER-427) Expose configuration for inhibiting Expect-Continue handshake

Tamas Cservenak created MRESOLVER-427: - Summary: Expose configuration for inhibiting Expect-Continue handshake Key: MRESOLVER-427 URL: https://issues.apache.org/jira/browse/MRESOLVER-427 Project:

[jira] [Created] (MRESOLVER-428) Handle differently the "memoized HTTP 404" cached responses

Tamas Cservenak created MRESOLVER-428: - Summary: Handle differently the "memoized HTTP 404" cached responses Key: MRESOLVER-428 URL: https://issues.apache.org/jira/browse/MRESOLVER-428 Project:

[jira] [Commented] (MRESOLVER-428) Handle differently the "memoized HTTP 404" cached responses

[ https://issues.apache.org/jira/browse/MRESOLVER-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783298#comment-17783298 ] Tamas Cservenak commented on MRESOLVER-428: --- I would leave out the "not yet synced to

[jira] [Updated] (MNG-7909) Upgrade to Resolver 2.0.0-alpha-1

[ https://issues.apache.org/jira/browse/MNG-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-7909: - Summary: Upgrade to Resolver 2.0.0-alpha-1 (was: Upgrade to Resolver 2.0.0) > Upgrade to Resolver

[jira] [Updated] (MNG-7909) Upgrade to Resolver 2.0.0-alpha-1

[ https://issues.apache.org/jira/browse/MNG-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-7909: - Description: Post alpha-8 a release of Resolver 2.0.0-alpha-1 (depending on other work, like

[jira] [Assigned] (MNG-7909) Upgrade to Resolver 2.0.0-alpha-1

[ https://issues.apache.org/jira/browse/MNG-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MNG-7909: Assignee: Tamas Cservenak > Upgrade to Resolver 2.0.0-alpha-1 >

[jira] [Updated] (MNG-7909) Upgrade to Resolver 2.0.0-alpha-1

[ https://issues.apache.org/jira/browse/MNG-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-7909: - Fix Version/s: 4.0.0-alpha-9 (was: 4.0.x-candidate) > Upgrade to Resolver

[jira] [Comment Edited] (MRESOLVER-412) BF collector causes same model to be loaded up multiple times

[ https://issues.apache.org/jira/browse/MRESOLVER-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776271#comment-17776271 ] Tamas Cservenak edited comment on MRESOLVER-412 at 10/17/23 4:37 PM:

[jira] [Commented] (MRESOLVER-412) BF collector causes same model to be loaded up multiple times

[ https://issues.apache.org/jira/browse/MRESOLVER-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776271#comment-17776271 ] Tamas Cservenak commented on MRESOLVER-412: --- [~wecai] the IT is introduced for maven4, yes.

[jira] [Comment Edited] (MRESOLVER-412) BF collector causes same model to be loaded up multiple times

[ https://issues.apache.org/jira/browse/MRESOLVER-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776271#comment-17776271 ] Tamas Cservenak edited comment on MRESOLVER-412 at 10/17/23 4:34 PM:

[jira] [Commented] (MRESOLVER-412) BF collector causes same model to be loaded up multiple times

[ https://issues.apache.org/jira/browse/MRESOLVER-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776276#comment-17776276 ] Tamas Cservenak commented on MRESOLVER-412: --- ModelBuilder is invoked implicitly, whenever

[jira] [Commented] (MRESOLVER-412) BF collector causes same model to be loaded up multiple times

[ https://issues.apache.org/jira/browse/MRESOLVER-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776304#comment-17776304 ] Tamas Cservenak commented on MRESOLVER-412: --- It seems my suspicion was right: this is

[jira] [Updated] (MRESOLVER-406) Update Jetty to 9.4.52.v20230823 (test dependency)

[ https://issues.apache.org/jira/browse/MRESOLVER-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-406: -- Issue Type: Dependency upgrade (was: Task) > Update Jetty to 9.4.52.v20230823

[jira] [Assigned] (MNG-7859) Update to Resolver 1.9.16

[ https://issues.apache.org/jira/browse/MNG-7859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MNG-7859: Assignee: Tamas Cservenak > Update to Resolver 1.9.16 > - > >

[jira] [Created] (MINDEXER-197) Update modernizer plugin to 2.7.0

Tamas Cservenak created MINDEXER-197: Summary: Update modernizer plugin to 2.7.0 Key: MINDEXER-197 URL: https://issues.apache.org/jira/browse/MINDEXER-197 Project: Maven Indexer Issue

[jira] [Assigned] (MINDEXER-197) Update modernizer plugin to 2.7.0

[ https://issues.apache.org/jira/browse/MINDEXER-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MINDEXER-197: Assignee: Tamas Cservenak > Update modernizer plugin to 2.7.0 >

[jira] [Closed] (MINDEXER-197) Update modernizer plugin to 2.7.0

[ https://issues.apache.org/jira/browse/MINDEXER-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MINDEXER-197. Resolution: Fixed > Update modernizer plugin to 2.7.0 >

[jira] [Commented] (MNG-7887) cannot inject ci-friendly revision/sha1/changelist properties via MAVEN_OPTS

[ https://issues.apache.org/jira/browse/MNG-7887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767935#comment-17767935 ] Tamas Cservenak commented on MNG-7887: -- https://github.com/apache/maven-site/pull/452 > cannot inject

[jira] [Commented] (MNG-7885) Plugin dependencies should be part in dependency management

[ https://issues.apache.org/jira/browse/MNG-7885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767942#comment-17767942 ] Tamas Cservenak commented on MNG-7885: -- Hm, reconsidering the second part, i said something silly

[jira] [Updated] (MNG-7895) Support ${project.basedir} in file profile activation

[ https://issues.apache.org/jira/browse/MNG-7895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-7895: - Fix Version/s: 3.9.5 > Support ${project.basedir} in file profile activation >

[jira] [Updated] (MNG-7886) Do not warn (or improve warning message) if a profile exists only in the reactor pom, but not in the selected module.

[ https://issues.apache.org/jira/browse/MNG-7886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-7886: - Fix Version/s: 3.9.5 > Do not warn (or improve warning message) if a profile exists only in the >

[jira] [Commented] (MNG-7885) Plugin dependencies should be part in dependency management

[ https://issues.apache.org/jira/browse/MNG-7885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767940#comment-17767940 ] Tamas Cservenak commented on MNG-7885: -- While this sounds good, I think this is a bad idea... build

[jira] [Commented] (MNG-7883) Also print groupId and version in the Reactor Build Order

[ https://issues.apache.org/jira/browse/MNG-7883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767941#comment-17767941 ] Tamas Cservenak commented on MNG-7883: -- This can already be done (if your goal is really "just"

[jira] [Closed] (MNG-7887) cannot inject ci-friendly revision/sha1/changelist properties via MAVEN_OPTS

[ https://issues.apache.org/jira/browse/MNG-7887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MNG-7887. Resolution: Won't Fix This change that user reported is actually a consequence of "user properties

[jira] [Commented] (MNG-7887) cannot inject ci-friendly revision/sha1/changelist properties via MAVEN_OPTS

[ https://issues.apache.org/jira/browse/MNG-7887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767964#comment-17767964 ] Tamas Cservenak commented on MNG-7887: -- Release notes for 3.9.0-3.9.4 updated

[jira] [Assigned] (MRESOLVER-406) Update Jetty to 9.4.52.v20230823 (test dependency)

[ https://issues.apache.org/jira/browse/MRESOLVER-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MRESOLVER-406: - Assignee: Tamas Cservenak > Update Jetty to 9.4.52.v20230823 (test

[jira] [Closed] (MRESOLVER-406) Update Jetty to 9.4.52.v20230823 (test dependency)

[ https://issues.apache.org/jira/browse/MRESOLVER-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-406. - Resolution: Fixed > Update Jetty to 9.4.52.v20230823 (test dependency) >

[jira] [Created] (MRESOLVER-406) Update Jetty to 9.4.52.v20230823 (test dependency)

Tamas Cservenak created MRESOLVER-406: - Summary: Update Jetty to 9.4.52.v20230823 (test dependency) Key: MRESOLVER-406 URL: https://issues.apache.org/jira/browse/MRESOLVER-406 Project: Maven

[jira] [Updated] (MNG-7859) Update to Resolver 1.9.16

[ https://issues.apache.org/jira/browse/MNG-7859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-7859: - Description: When 1.9.16 is released, update to it. (was: When 1.9.15 is released, update to it.)

[jira] [Closed] (MNG-7859) Update to Resolver 1.9.16

[ https://issues.apache.org/jira/browse/MNG-7859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MNG-7859. Resolution: Fixed > Update to Resolver 1.9.16 > - > > Key:

[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=17768766#comment-17768766 ] Tamas Cservenak commented on MNG-7868: -- Maven: {{$LOCK_FACTORY=rwlock-local}} {{$NAME_MAPPER=gav}}  

[jira] [Commented] (MNG-7373) Maven should not attempt to download the jar when pom

[ https://issues.apache.org/jira/browse/MNG-7373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769955#comment-17769955 ] Tamas Cservenak commented on MNG-7373: -- This issue does not stand at all today (probably

[jira] [Comment Edited] (MNG-7373) Maven should not attempt to download the jar when pom

[ https://issues.apache.org/jira/browse/MNG-7373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769955#comment-17769955 ] Tamas Cservenak edited comment on MNG-7373 at 9/28/23 9:07 AM: --- This issue

[jira] [Comment Edited] (MNG-7373) Maven should not attempt to download the jar when pom

[ https://issues.apache.org/jira/browse/MNG-7373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769955#comment-17769955 ] Tamas Cservenak edited comment on MNG-7373 at 9/28/23 9:09 AM: --- This issue

[jira] [Comment Edited] (MNG-7373) Maven should not attempt to download the jar when pom

[ https://issues.apache.org/jira/browse/MNG-7373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769955#comment-17769955 ] Tamas Cservenak edited comment on MNG-7373 at 9/28/23 9:09 AM: --- This issue

[jira] [Comment Edited] (MNG-7373) Maven should not attempt to download the jar when pom

[ https://issues.apache.org/jira/browse/MNG-7373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769955#comment-17769955 ] Tamas Cservenak edited comment on MNG-7373 at 9/28/23 9:09 AM: --- This issue

[jira] [Commented] (MNG-7873) Export missing Xpp3DomBuilder

[ https://issues.apache.org/jira/browse/MNG-7873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770789#comment-17770789 ] Tamas Cservenak commented on MNG-7873: -- So, is this issue fixed by those releases? No change in Maven

[jira] [Updated] (MNG-7873) Export missing Xpp3DomBuilder

[ https://issues.apache.org/jira/browse/MNG-7873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-7873: - Fix Version/s: (was: 3.9.5) > Export missing Xpp3DomBuilder > - >

[jira] [Commented] (MCOMPILER-546) Maven compiling fails when using JEP 443

[ https://issues.apache.org/jira/browse/MCOMPILER-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769460#comment-17769460 ] Tamas Cservenak commented on MCOMPILER-546: --- Reported as

[jira] [Commented] (MNG-7886) Do not warn (or improve warning message) if a profile exists only in the reactor pom, but not in the selected module.

[ https://issues.apache.org/jira/browse/MNG-7886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769774#comment-17769774 ] Tamas Cservenak commented on MNG-7886: -- You consequence is somewhat wrong: by invoking project like

[jira] [Comment Edited] (MNG-7886) Do not warn (or improve warning message) if a profile exists only in the reactor pom, but not in the selected module.

[ https://issues.apache.org/jira/browse/MNG-7886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769774#comment-17769774 ] Tamas Cservenak edited comment on MNG-7886 at 9/27/23 8:10 PM: --- You

[jira] [Comment Edited] (MNG-7373) Maven should not attempt to download the jar when pom

[ https://issues.apache.org/jira/browse/MNG-7373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769743#comment-17769743 ] Tamas Cservenak edited comment on MNG-7373 at 9/27/23 8:18 PM: --- Maven when

[jira] [Comment Edited] (MNG-7373) Maven should not attempt to download the jar when pom

[ https://issues.apache.org/jira/browse/MNG-7373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769743#comment-17769743 ] Tamas Cservenak edited comment on MNG-7373 at 9/27/23 8:18 PM: --- Maven when

[jira] [Updated] (MNG-7886) Do not warn (or improve warning message) if a profile exists only in the reactor pom, but not in the selected module.

[ https://issues.apache.org/jira/browse/MNG-7886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MNG-7886: - Fix Version/s: (was: 3.9.5) > Do not warn (or improve warning message) if a profile exists

[jira] [Commented] (MNG-7886) Do not warn (or improve warning message) if a profile exists only in the reactor pom, but not in the selected module.

[ https://issues.apache.org/jira/browse/MNG-7886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769778#comment-17769778 ] Tamas Cservenak commented on MNG-7886: -- Regarding "affects version: 3.9.4" set by reported: this

[jira] [Commented] (MNG-7508) Validate usage of true on plugins

[ https://issues.apache.org/jira/browse/MNG-7508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769739#comment-17769739 ] Tamas Cservenak commented on MNG-7508: -- There are cases where loading a "plain" (without extension)

[jira] [Commented] (MNG-7772) Allow to register maven core extension in .m2 directory instead of MAVEN_HOME

[ https://issues.apache.org/jira/browse/MNG-7772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769736#comment-17769736 ] Tamas Cservenak commented on MNG-7772: -- The reason why this was not considered is how easily makes it

[jira] [Comment Edited] (MNG-7373) Maven should not attempt to download the jar when pom

[ https://issues.apache.org/jira/browse/MNG-7373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769743#comment-17769743 ] Tamas Cservenak edited comment on MNG-7373 at 9/27/23 6:37 PM: --- Maven when

[jira] [Commented] (MNG-7373) Maven should not attempt to download the jar when pom

[ https://issues.apache.org/jira/browse/MNG-7373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769743#comment-17769743 ] Tamas Cservenak commented on MNG-7373: -- Maven when reaches out to remote artifacts uses locally

[jira] [Comment Edited] (MCOMPILER-546) Maven compiling fails when using JEP 443

[ https://issues.apache.org/jira/browse/MCOMPILER-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769303#comment-17769303 ] Tamas Cservenak edited comment on MCOMPILER-546 at 9/26/23 6:15 PM:

[jira] [Commented] (MCOMPILER-546) Maven compiling fails when using JEP 443

[ https://issues.apache.org/jira/browse/MCOMPILER-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769303#comment-17769303 ] Tamas Cservenak commented on MCOMPILER-546: --- Vlad, this seems JDK bug. Try without maven,

[jira] [Commented] (MCOMPILER-546) Maven compiling fails when using JEP 443

[ https://issues.apache.org/jira/browse/MCOMPILER-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769304#comment-17769304 ] Tamas Cservenak commented on MCOMPILER-546: --- Funny, here it is reported, and "they cannot

[jira] [Comment Edited] (MCOMPILER-546) Maven compiling fails when using JEP 443

[ https://issues.apache.org/jira/browse/MCOMPILER-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769304#comment-17769304 ] Tamas Cservenak edited comment on MCOMPILER-546 at 9/26/23 6:28 PM:

[jira] [Comment Edited] (MCOMPILER-546) Maven compiling fails when using JEP 443

[ https://issues.apache.org/jira/browse/MCOMPILER-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769304#comment-17769304 ] Tamas Cservenak edited comment on MCOMPILER-546 at 9/26/23 6:29 PM:

[jira] [Commented] (MCOMPILER-546) Maven compiling fails when using JEP 443

[ https://issues.apache.org/jira/browse/MCOMPILER-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769316#comment-17769316 ] Tamas Cservenak commented on MCOMPILER-546: --- Reproducer

[jira] [Commented] (MDEPLOY-312) [REGRESSION] deploy no longer updates project model

[ https://issues.apache.org/jira/browse/MDEPLOY-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17774598#comment-17774598 ] Tamas Cservenak commented on MDEPLOY-312: - What are you trying to resolve here? The PR is IMHO

[jira] [Assigned] (MRESOLVER-407) Upgrade to Maven 3.9.5

[ https://issues.apache.org/jira/browse/MRESOLVER-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MRESOLVER-407: - Assignee: Tamas Cservenak > Upgrade to Maven 3.9.5 > --

[jira] [Created] (MRESOLVER-407) Upgrade to Maven 3.9.5

Tamas Cservenak created MRESOLVER-407: - Summary: Upgrade to Maven 3.9.5 Key: MRESOLVER-407 URL: https://issues.apache.org/jira/browse/MRESOLVER-407 Project: Maven Resolver Issue Type:

[jira] [Updated] (MRESOLVER-407) Upgrade to Maven 3.9.5

[ https://issues.apache.org/jira/browse/MRESOLVER-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-407: -- Fix Version/s: 2.0.0 1.9.x > Upgrade to Maven 3.9.5 >

[jira] [Assigned] (MRESOLVER-324) Make the BF algorithm as the default option to speed up maven dependency resolution and downloading

[ https://issues.apache.org/jira/browse/MRESOLVER-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak reassigned MRESOLVER-324: - Assignee: Tamas Cservenak > Make the BF algorithm as the default option to

[jira] [Closed] (MRESOLVER-324) Make the BF algorithm as the default option to speed up maven dependency resolution and downloading

[ https://issues.apache.org/jira/browse/MRESOLVER-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-324. - Resolution: Fixed > Make the BF algorithm as the default option to speed up maven

[jira] [Created] (MRESOLVER-408) Prepare for 2.0.0 version

Tamas Cservenak created MRESOLVER-408: - Summary: Prepare for 2.0.0 version Key: MRESOLVER-408 URL: https://issues.apache.org/jira/browse/MRESOLVER-408 Project: Maven Resolver Issue Type:

[jira] [Closed] (MRESOLVER-407) Upgrade to Maven 3.9.5

[ https://issues.apache.org/jira/browse/MRESOLVER-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-407. - Resolution: Fixed > Upgrade to Maven 3.9.5 > -- > >

[jira] [Closed] (MRESOLVER-408) Prepare for 2.0.0 version

[ https://issues.apache.org/jira/browse/MRESOLVER-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-408. - Assignee: Tamas Cservenak Resolution: Fixed > Prepare for 2.0.0 version >

[jira] [Created] (MRESOLVER-415) New transport: JDK11 HTTP/2 capable

Tamas Cservenak created MRESOLVER-415: - Summary: New transport: JDK11 HTTP/2 capable Key: MRESOLVER-415 URL: https://issues.apache.org/jira/browse/MRESOLVER-415 Project: Maven Resolver

[jira] [Updated] (MRESOLVER-412) BF collector causes same model to be loaded up multiple times

[ https://issues.apache.org/jira/browse/MRESOLVER-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-412: -- Fix Version/s: (was: 2.0.0) > BF collector causes same model to be loaded up

[jira] [Closed] (MRESOLVER-412) BF collector causes same model to be loaded up multiple times

[ https://issues.apache.org/jira/browse/MRESOLVER-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-412. - Resolution: Fixed This issue is not a resolver issue, but Maven Model Builder issue,

[jira] [Commented] (MRESOLVER-412) BF collector causes same model to be loaded up multiple times

[ https://issues.apache.org/jira/browse/MRESOLVER-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776396#comment-17776396 ] Tamas Cservenak commented on MRESOLVER-412: --- Also, tested resolver + this PR

[jira] [Created] (MRESOLVER-416) New transport: Jetty, HTTP/2 capable

Tamas Cservenak created MRESOLVER-416: - Summary: New transport: Jetty, HTTP/2 capable Key: MRESOLVER-416 URL: https://issues.apache.org/jira/browse/MRESOLVER-416 Project: Maven Resolver

[jira] [Commented] (MRESOLVER-384) Support HTTP/2 in maven-resolver-transport-http

[ https://issues.apache.org/jira/browse/MRESOLVER-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776406#comment-17776406 ] Tamas Cservenak commented on MRESOLVER-384: --- To be solves as MRESOLVER-414 and MRESOLVER-415

[jira] [Comment Edited] (MRESOLVER-384) Support HTTP/2 in maven-resolver-transport-http

[ https://issues.apache.org/jira/browse/MRESOLVER-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776406#comment-17776406 ] Tamas Cservenak edited comment on MRESOLVER-384 at 10/17/23 9:50 PM:

[jira] [Updated] (MRESOLVER-417) Create HTTP test suite a la "TCK"

[ https://issues.apache.org/jira/browse/MRESOLVER-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-417: -- Description: Now that we have 3 (4 w/ Wagon) HTTP capable resolver transports, we

[jira] [Created] (MRESOLVER-417) Create HTTP test suite a la "TCK"

Tamas Cservenak created MRESOLVER-417: - Summary: Create HTTP test suite a la "TCK" Key: MRESOLVER-417 URL: https://issues.apache.org/jira/browse/MRESOLVER-417 Project: Maven Resolver

[jira] [Updated] (MRESOLVER-417) Create HTTP test suite a la "TCK"

[ https://issues.apache.org/jira/browse/MRESOLVER-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak updated MRESOLVER-417: -- Description: Now that we have 3 (4 w/ Wagon) HTTP capable resolver transports, we

[jira] [Commented] (MRESOLVER-372) Download fails if file is currently in use under windows

[ https://issues.apache.org/jira/browse/MRESOLVER-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17773821#comment-17773821 ] Tamas Cservenak commented on MRESOLVER-372: --- This is very cool! Thank you for your

[jira] [Closed] (MRESOLVER-418) Migrate to Junit5

[ https://issues.apache.org/jira/browse/MRESOLVER-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Cservenak closed MRESOLVER-418. - Resolution: Fixed > Migrate to Junit5 > - > > Key:

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