gnodet commented on pull request #607: URL: https://github.com/apache/maven/pull/607#issuecomment-975573511
> > Yes, I have the same problem. The `ClassCastException` happens when adding the following to the pom.xml: > > ``` > > <dependency> > > <groupId>org.apache.maven.scm</groupId> > > <artifactId>maven-scm-manager-plexus</artifactId> > > <version>1.12.0</version> > > </dependency> > > ``` > > Provided scope seems to be the right one for this xtension. The cache is supposed to be a wrapper over core maven logic. If execution will be provided by separate dependency from a seprate classloader - it seems not right and could lead to different executions from extension and without it. Though question of using dependencies is a good one on it's own, it seems that the right way of using maven core from the extension is the provided scope Not really, the scm jars are not provided by maven-core. Plugins such as `maven-release-plugin` do have direct dependencies on those jars. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
