Open papanito opened 4 years ago
Suggestion from https://github.com/groovy/GMavenPlus/issues/84#issuecomment-411344473 did not help
So if I define the dependency globally then it does not work, but when defined as part of the plugin
as follows, it seems to work...
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>build-helper-maven-plugin</artifactId>
<dependencies>
<dependency>
<groupId>org.codehaus.groovy</groupId>
<artifactId>groovy-all</artifactId>
<version>3.0.4</version>
<type>pom</type> <!-- required JUST since Groovy 2.5.0 -->
</dependency>
</dependencies>
Did I understand something wrong? Please advice, thanks
It looks to me like this is a multimodule project. The plugin would need Groovy to be a dependency of the submodule(s) in which it runs
Although it also looks like it is finding Groovy as a dependency, are you sure when it's working that Maven is choosing the same version (mvn dependency:tree
)?
@keeganwitt no it's a single module project.
But as you suspected, it actually takes different versions.
dependency as part of plugin
$ mvn dependency:tree |grep groovy
[INFO] +- org.codehaus.groovy:groovy-all:pom:3.0.4:compile
dependency defined globally
When done as commented above it looks as follows:
$ mvn dependency:tree |grep groovy
[INFO] | +- org.codehaus.groovy:groovy-all:jar:2.4.11:compile
However I tried to reproduce the issue again and I am not able. There is definitely something odd, but unless I cannot properly reproduce the issue I may close the issue.
Just to rule out the obvious, there's no possibility that there's profiles affecting results here?
I can definitively rule out this - so no, there is no profile which can affect the result
I have a project which was build successfully in the past. as of a sudden it fails with
My configuration looks like this:
and