[ 
https://issues.apache.org/jira/browse/ARCHETYPE-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tamas Cservenak updated ARCHETYPE-635:
--------------------------------------
    Description: 
The fix for issue ARCHETYPE-565 was to change artifactId from {{groovy}} to 
{{{}groovy-all{}}}, hence the Groovy version pulled in by archetype-common does 
NOT override anymore the version of Groovy used by maven-script-interpreter (it 
uses groovy:2.0.1).

The proper fix for ARCHETYPE-565 would be to along of changing artifactId of 
groovy dependency, add an exclusion on "old" artifactId on 
maven-script-interpreter dependency OR to re-add "plain" groovy artifact as 
well (would be redundant, but would achieve same goal).

  was:
The fix for issue ARCHETYPE-565 was to change artifactId from {{groovy}} to 
{{{}groovy-all{}}}, hence the Groovy version pulled in by archetype-common does 
NOT override anymore the version of Groovy used by maven-script-interpreter (it 
uses groovy:2.0.1).

The proper fix for ARCHETYPE-565 would be to along of changing artifactId of 
groovy dependency, add an exclusion on "old" artifactId on 
maven-script-interpreter dependency.


> Groovy present twice on classpath of m-archetype-p
> --------------------------------------------------
>
>                 Key: ARCHETYPE-635
>                 URL: https://issues.apache.org/jira/browse/ARCHETYPE-635
>             Project: Maven Archetype
>          Issue Type: Bug
>          Components: Plugin
>    Affects Versions: 3.2.1
>            Reporter: Tamas Cservenak
>            Priority: Major
>             Fix For: 3.2.2
>
>
> The fix for issue ARCHETYPE-565 was to change artifactId from {{groovy}} to 
> {{{}groovy-all{}}}, hence the Groovy version pulled in by archetype-common 
> does NOT override anymore the version of Groovy used by 
> maven-script-interpreter (it uses groovy:2.0.1).
> The proper fix for ARCHETYPE-565 would be to along of changing artifactId of 
> groovy dependency, add an exclusion on "old" artifactId on 
> maven-script-interpreter dependency OR to re-add "plain" groovy artifact as 
> well (would be redundant, but would achieve same goal).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to