You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "cstamas (via GitHub)" <gi...@apache.org> on 2026/05/11 16:02:27 UTC
[I] Back out of Resolver 2.x ScopeManager use completely [maven]
cstamas opened a new issue, #12034:
URL: https://github.com/apache/maven/issues/12034
### Affected version
3.10.x
### Bug description
We are far from making this possibly (truly dynamic scopes). I spend 24h on this, and almost all went well, except the `maven-artifact` and `MavenProject` that simply smears whatever we do into 'old way' of things. So, am giving up.
Maven 3.10.x will use Resolver 2.x is "full Maven 3 compat mode", no scope manager and no new scopes.
--
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-unsubscribe@maven.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Back out of Resolver 2.x ScopeManager use completely [maven]
Posted by "cstamas (via GitHub)" <gi...@apache.org>.
cstamas closed issue #12034: Back out of Resolver 2.x ScopeManager use completely
URL: https://github.com/apache/maven/issues/12034
--
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-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Back out of Resolver 2.x ScopeManager use completely [maven]
Posted by "cstamas (via GitHub)" <gi...@apache.org>.
cstamas commented on issue #12034:
URL: https://github.com/apache/maven/issues/12034#issuecomment-4422699447
Yup, in fact we need to ditch the scope manager too.
--
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-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Back out of Resolver 2.x ScopeManager use completely [maven]
Posted by "cstamas (via GitHub)" <gi...@apache.org>.
cstamas commented on issue #12034:
URL: https://github.com/apache/maven/issues/12034#issuecomment-4422428821
Probably we still need Resolver 2.0.18, and here we can _undeprecate_ the class or classes @slawekjaranowski found as deprecated.
--
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-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Back out of Resolver 2.x ScopeManager use completely [maven]
Posted by "slawekjaranowski (via GitHub)" <gi...@apache.org>.
slawekjaranowski commented on issue #12034:
URL: https://github.com/apache/maven/issues/12034#issuecomment-4422639201
So we add scope - `compile-only` in `org.apache.maven.repository.internal.scopes.Maven3ScopeManagerConfiguration`
should this scope be removed from Maven 3.x?
--
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-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org