-
Notifications
You must be signed in to change notification settings - Fork 428
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Archetype generation fails with maven-archetype-plugin 3.2.1 #857
Comments
…ontains "groovy-all" dependency by default
@stefanseifert thanks, but which command should i do? to get download project without errors? |
@stefanseifert |
workaround: until the PR #858 is merged and released specify the maven archetype plugin version on the command line to create a new AEM project. example:
|
@stefanseifert thanks a lot |
…ns "groovy-all" dependency by default (#858)
…ns "groovy-all" dependency by default (#858)
When creating a new AEM project without actually specifying an archetype plugin version on the command line, Maven uses the latest by default. And this is currently failing with the latest version 3.2.1 released a few days ago.
Exception:
root cause is the change in the plugin dependencies for groovy in https://issues.apache.org/jira/browse/ARCHETYPE-565
The text was updated successfully, but these errors were encountered: