[ https://issues.apache.org/jira/browse/ARCHETYPE-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17186724#comment-17186724 ]
Josh Reagan commented on ARCHETYPE-565: --------------------------------------- [https://github.com/apache/maven-archetype/pull/58] > Unable to resolve groovy.json classes when planting > --------------------------------------------------- > > Key: ARCHETYPE-565 > URL: https://issues.apache.org/jira/browse/ARCHETYPE-565 > Project: Maven Archetype > Issue Type: Bug > Components: Archetypes > Affects Versions: 3.1.0 > Reporter: Edgar Cantu > Priority: Major > > With the latest release of the archetype generator, projects that have a > post-generation script that import from other packages not in groovy core > fail to build with an error similar to the following: > {code:bash} > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-archetype-plugin:3.1.0:generate (default-cli) > on project standalone-pom: startup failed: > [ERROR] Script1.groovy: 1: unable to resolve class groovy.json.JsonException > [ERROR] @ line 1, column 1. > [ERROR] import groovy.json.JsonException > [ERROR] ^ > [ERROR] > {code} > This used to work in the previous version: 3.0.1 of the archetype-plugin. > Suspected change that introduced this backwards incompatibility: > https://github.com/apache/maven-archetype/commit/11cb603da9d3da813c0a34a9e2532cc2c85f940b#diff-a6aa95e2d0a1da7b4460e2506c2e67daR56 > Essentially, with https://issues.apache.org/jira/browse/ARCHETYPE-536 it > looks like the {{groovy}} dependency went from 1.8.3 to 2.4.16 and groovy > split modules from groovy core with the 2.x release. There is a > {{groovy-all}} package that could be used. -- This message was sent by Atlassian Jira (v8.3.4#803005)