I've run into this before, try setting the snapshot timeout.
buildscript {
repositories {
mavenLocal()*.setSnapshotTimeout(0)*
}
dependencies {
classpath('no.org:myplugin:14-SNAPSHOT')
}
}
Hope this helps.
Vinod
On Mon, Oct 3, 2011 at 9:32 AM, Thor Åge Eldby <[email protected]>wrote:
> Hi.
>
> I have a module (a plugin) I need to develop new extensions to now and
> then. This module has its own project. When developing it I try to use the
> maven plugin to install (gradle install) new versions to the local maven
> repository (~/.m2/repository):
>
> apply plugin: 'java'
> apply plugin: 'maven'
> group = 'no.org'
> version = '14-SNAPSHOT'
>
> Then I try to test the updated version from the other project:
>
> buildscript {
> repositories {
> mavenLocal()
> }
> dependencies {
> classpath('no.org:myplugin:14-SNAPSHOT')
> }
> }
>
>
> The first time of course is ok, but after that I will always get the same
> stale jar. I assume this is because it gets stuck in the ivy repository. If
> I delete ~/.gradle I will get a new version again. However its a little bit
> cumbersome to have to remove the global cache each time. Is there anyway
> around this?
>
> See example projects in zip
>
> Thanks
> Thor Åge Eldby
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
