slawekjaranowski commented on pull request #113:
URL: https://github.com/apache/maven-enforcer/pull/113#issuecomment-968907971
Interesting case ....
`maven-enforcer-extension` - add to project `build/plugins` execution of
`maven-enforcer-plugin` and configure it according to
`.mnv/enforcer-extension.xml`
everything is doing by string coding 😄 ... and `maven-enforcer-plugin` is
needed in runtime
`maven-enforcer-extension` - doesn't have on dependency
`maven-enforcer-plugin` so local-repo doesn't have it and the latest snapshot
from remote repository is dowloaded during it test .... and what is in remote
snapshot repository is not compatible with your change - we testing **current**
project with **old** plugin ...
workaround .... add to project `maven-enforcer-extension` dependency:
```xml
<dependency>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-enforcer-plugin</artifactId>
<version>${project.version}</version>
<scope>runtime</scope>
<exclusions>
<exclusion>
<groupId>*</groupId>
<artifactId>*</artifactId>
</exclusion>
</exclusions>
</dependency>
```
exclusion is needed because we have maven core component in different scope
in plugin and extensions ...
it should be the same - maven core artifacts should be as provided
--
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]
