Hi René,
it seems that the UP-TO-DATE check has often problems with changes to
the gradle files.
http://jira.codehaus.org/browse/GRADLE-1346
http://jira.codehaus.org/browse/GRADLE-1007
regards,
Mathias Kalb
Am 14.02.2011 23:19, schrieb Rene Groeschke:
Hi there,
I've noticed, that when changing the version in my project, The jar task
isn't executed again since it is marked as up to date. This ends up with
a jar file in my build/lib directory with up to date content, but with a
wrong name (project + old version +".jar"). As a workaround I've added
the following snippet to my build:
-------
jar{
inputs.properties([version:version])
}
-------
but shouldn't the version be used as input property per default or is
this intended behaviour? I couldn't find an jira issue for that problem,
but sure that I am not the only one who runs into this problem. Should i
raise one?
regards,
René
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
