looks like a good idea
+1

Regards,

Hervé

Le samedi 14 mai 2022, 15:47:25 CEST Slawomir Jaranowski a écrit :
> Hi,
> 
> currently in m-invoker-p we have a dependency with a lot of exclusions ...
> 
>     <dependency>
>       <groupId>org.codehaus.groovy</groupId>
>       <artifactId>groovy-all</artifactId>
>       <version>3.0.9</version>
>       <type>pom</type>
>       <scope>runtime</scope>
>       <exclusions>
>         <exclusion>
>           <groupId>org.codehaus.groovy</groupId>
>           <artifactId>groovy-groovysh</artifactId>
>         </exclusion>
>         <exclusion>
>           <groupId>org.codehaus.groovy</groupId>
>           <artifactId>groovy-test</artifactId>
>         </exclusion>
>         <exclusion>
>           <groupId>org.codehaus.groovy</groupId>
>           <artifactId>groovy-test-junit5</artifactId>
>         </exclusion>
>         <exclusion>
>           <groupId>org.codehaus.groovy</groupId>
>           <artifactId>groovy-testng</artifactId>
>         </exclusion>
>       </exclusions>
>     </dependency>
> 
> but anyway, dependency tree is:
> 
> +- org.codehaus.groovy:groovy-all:pom:3.0.9:runtime
> 
> |  +- org.codehaus.groovy:groovy:jar:3.0.9:runtime
> |  +- org.codehaus.groovy:groovy-ant:jar:3.0.9:runtime
> |  
> |  |  +- org.apache.ant:ant:jar:1.10.11:runtime
> |  |  +- org.apache.ant:ant-junit:jar:1.10.11:runtime
> |  |  
> |  |  |  \- com.sun:tools:jar:1.8.0:system
> |  |  
> |  |  +- org.apache.ant:ant-launcher:jar:1.10.11:runtime
> |  |  \- org.apache.ant:ant-antlr:jar:1.10.11:runtime
> |  
> |  +- org.codehaus.groovy:groovy-astbuilder:jar:3.0.9:runtime
> |  +- org.codehaus.groovy:groovy-cli-picocli:jar:3.0.9:runtime
> |  
> |  |  \- info.picocli:picocli:jar:4.6.1:runtime
> |  
> |  +- org.codehaus.groovy:groovy-console:jar:3.0.9:runtime
> |  +- org.codehaus.groovy:groovy-datetime:jar:3.0.9:runtime
> |  +- org.codehaus.groovy:groovy-docgenerator:jar:3.0.9:runtime
> |  
> |  |  \- com.thoughtworks.qdox:qdox:jar:1.12.1:runtime
> |  
> |  +- org.codehaus.groovy:groovy-groovydoc:jar:3.0.9:runtime
> |  
> |  |  \- com.github.javaparser:javaparser-core:jar:3.23.0:runtime
> |  
> |  +- org.codehaus.groovy:groovy-jmx:jar:3.0.9:runtime
> |  +- org.codehaus.groovy:groovy-json:jar:3.0.9:runtime
> |  +- org.codehaus.groovy:groovy-jsr223:jar:3.0.9:runtime
> |  +- org.codehaus.groovy:groovy-macro:jar:3.0.9:runtime
> |  +- org.codehaus.groovy:groovy-nio:jar:3.0.9:runtime
> |  +- org.codehaus.groovy:groovy-servlet:jar:3.0.9:runtime
> |  +- org.codehaus.groovy:groovy-sql:jar:3.0.9:runtime
> |  +- org.codehaus.groovy:groovy-swing:jar:3.0.9:runtime
> |  +- org.codehaus.groovy:groovy-templates:jar:3.0.9:runtime
> |  \- org.codehaus.groovy:groovy-xml:jar:3.0.9:runtime
> 
> So every user of m-invoker-p downloads a lot of unneeded stuff.
> 
> I don't believe that someone needs sql, servlet, swing .. etc in invoker
> verify scripts.
> I'm not feel good about adding the next exclusions.
> 
> My prefer way is add only some of common used modules like:
> - groovy-xml
> 
> If someone needs a more special case can add it in your projects to plugin
> dependencies.
> 
> What do you think?
> What special groovy modules are you used in invoker groovy scripts?





---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to