[
https://issues.apache.org/jira/browse/GROOVY-10649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17550476#comment-17550476
]
Tommy Svensson commented on GROOVY-10649:
-----------------------------------------
Never mind, I was dumb enough to trust IDEA about latest version of
maven-plugin-plugin ...
> Groovy 4.0.1 makes maven plugin fail when Groovy 4.0.1 code is on the
> classpath.
> --------------------------------------------------------------------------------
>
> Key: GROOVY-10649
> URL: https://issues.apache.org/jira/browse/GROOVY-10649
> Project: Groovy
> Issue Type: Bug
> Affects Versions: 4.0.1
> Environment: Mac OS X Monteray 12.4.
> Reporter: Tommy Svensson
> Priority: Major
>
> With groovy 3.0.x my maven plugin built and ran without problems, but when I
> upgraded to 4.0.1 the compilation of the maven plugin fails:
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-plugin-plugin:3.4:descriptor
> (default-descriptor) on project markdowndoc-maven-plugin: Execution
> default-descriptor of goal
> org.apache.maven.plugins:maven-plugin-plugin:3.4:descriptor failed.:
> IllegalArgumentException -> [Help 1]
> All that is needed for this failure to happen is to have Groovy 4.0.1 code on
> the classpath. The plugin itself is written in Java, but it calls code
> compiled with in Groovy 4.0.1, but with Groovy 4.0.1 code on the classpath it
> doesn't even get so far that it actually compiles the plugin. It fails before
> that it seems. So something in Groovy 4 interferes with Maven plugin.
> With Groovy 3.x it works fine. The only thing that is new is the version of
> groovy.
> Checkout https://github.com/tombensve/MarkdownDoc, branch MarkdownDoc-40 and
> then do an mvn install you will see the very unclear failure. The main branch
> uses Groovy 3 and it builds fine.
> The only way to currently get around this is to make a server where the
> MarkdownDoc library can be triggered remotely over the network running in a
> different process, which would require no dependencies to Groovy 4 from the
> plugin. But this feels like a really annoying workaround.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
