[
https://issues.apache.org/jira/browse/GROOVY-8037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904669#comment-15904669
]
Romain Manni-Bucau commented on GROOVY-8037:
--------------------------------------------
[~paulk] create a maven lib with a method printing "hello", install with
version 1.0-SNAPSHOT, then use grapes to print the message. Now update the lib
to print "foo" and re-install (mvn install). Re-run your script and you will
get "hello" cause ivy cached the jar. Using changing=true is a workaround but
would be nice to check mvn metadata in local repos (file) at least.
> support aether/maven Grapes resolution
> --------------------------------------
>
> Key: GROOVY-8037
> URL: https://issues.apache.org/jira/browse/GROOVY-8037
> Project: Groovy
> Issue Type: Improvement
> Reporter: Romain Manni-Bucau
>
> This is quite bothering to work with ivy/grapes on development cause it
> doesn't support well snapshots, it would be very convenient to support maven
> SNAPSHOT out of the box.
> One solution I see is to reuse eiather grape engine from spring boot
> (https://github.com/spring-projects/spring-boot/blob/master/spring-boot-cli/src/main/java/org/springframework/boot/cli/compiler/grape/AetherGrapeEngine.java)
> with a few adaptations probably + enable to select the grape engine in its
> groovy distribution or groovy JVM or to just add full support for snapshots
> policy out of the box.
> wdyt?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
