Thanks for the tip but even with changing='true' i still find myself
having to clear the cache manually for the new newly published SNAPSHOT
jar to be picked up.
Just now i was iterating over the design of a swing widget created in a
separate utility project. I used
@Grab(value='se.alipsa:swing-widgets:1.0.1-SNAPSHOT', changing='true')
in a groovy script to check the changes but if i don't clear the cache
before running the script, i don't see them.
Regards,
Per
On 3/17/26 00:15, Paul King wrote:
You can add changing as an annotation attribute or embedded in the
short-form version:
E.g. in the Groovy codebase, ExtensionModuleTest:
@Grab(value='module-test:module-test:1.4', changing='true')
E.g. STCExtensionMethodsTest:
@Grab('module-test:module-test:1.4;changing=true')
On Tue, Mar 17, 2026 at 7:37 AM Per Nyfelt<[email protected]> wrote:
I have tried to create a reproducible example but did not succeed, hence no
JIRA tocket. The reason is that -SNAPSHOT often works but far from always.
Maybe it's a time thing (short duration between published snapshots), maybe its
something else but I find it unreliable and the only reliable way i found is to
clear the cache after publishing the snapshot. That being said, i have not
tried changing=true. Where do i add that? To @GrabConfig or in the @Grab
statement itself?
On 3/15/26 16:18, Milles, Eric (TR Technology) via dev wrote:
GrapeIvy does not detect new snapshot versions well so you end up having to
clear the cache after each publish for GrapeIvy to find the new one
Is there a JIRA ticket for this issue? Ivy should be seeing "abc-1.0.0SNAPSHOT.jar" as a snapshot not
release and so it checks the repository for new artifacts. However, if you are pushing a new "abc-1.0.0.jar"
to your repo, that is not automatically checked if cached. You can add "changing=true" attribute to your
dependency or there are other config options to make this happen. Gradle behaves this same way unless you use
"--refresh-dependencies" command-line argument.
