On Sat, Mar 27, 2010 at 3:01 PM, Geronimo M. H. <[email protected]>wrote:
> Hello,
>
> I'm stuck with gradles handling of jarfiles and/or my (missing) knowledge.
> When I worked out the gradle buildscripts for my projects I realized, that
> gradle did not update the jarfiles in its internal cache and thought, that
> it
> could be, that gradle uses some checksums to get rid of changed files.
> As my files did not change at that point, I did not spent further
> investigations.
>
> Now that my build works, I can continue working on my stuff and I realized,
> that gradle did not update its internal cache for changed jarfiles either.
>
> So I need to work with jarfiles, that contains timestamps in the name - and
> that leaded to the next problem (most probabely my misunderstanding):
>
> The build.gradle contains this section:
>
> version = new Version(project)
> allprojects {
> apply url: file(rootProject.projectDir).absolutePath
> + '/../common/base.gradle'
> version = this.version
>
task info << {
> prjrelease = version.toString()
> println "\t${project.name} - Version: $prjrelease"
> println "\ttarget: ${tasks['jar'].archivePath}"
> }
> }
>
When playing with this behavior I run into similar issues. The default jar
has the proper timestamp. But additional jars which are project dependencies
don't. Which is a bug we will try to fix very soon.
I have added a Jira: http://jira.codehaus.org/browse/GRADLE-891
- Hans
--
Hans Dockter
Founder, Gradle
http://www.gradle.org, http://twitter.com/gradleorg
CEO, Gradle Inc. - Gradle Training, Support, Consulting
http://www.gradle.biz
