Hi,
thanks for the hints. I searched for a similar bug before creating my
jira issue. didn't noticed your one. sorry.
regards,
René
Am 15.05.11 18:42, schrieb Robert Fischer:
I opened a ticket for this already which contains a simple work-around:
http://issues.gradle.org/browse/GRADLE-1227
~~ Robert.
On Sun, May 15, 2011 at 5:27 AM, Ric Klaren<[email protected]> wrote:
Hi,
On 14 May 2011 15:16, Rene Groeschke<[email protected]> wrote:
We're actually working on the gpars build. I tried to get each up-to-date check
work properly when I noticed a bug for the jar tasks up-to-date check when the
osgi plugin is applied.
Is anybody aware of an convenient workarround for this issue:
http://issues.gradle.org/browse/GRADLE-1545
Ran into the same problem, I found a work around in the groovy build
scripts they filter the offending attribute out of the manifest (would
be nice if this was default behaviour):
http://svn.codehaus.org/groovy/trunk/groovy/groovy-core/gradle/assemble.gradle
Relevant snippet:
commonOsgiManifest = {
// We exclude the Bnd-LastModified attribute as it always triggers
a rebuild without being really needed.
from(allManifest) {
eachEntry {details ->
if (details.key == 'Bnd-LastModified') {
details.exclude()
}
}
}
....
}
Hope this helps,
Ric
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
-----------------------
regards René
rene groeschke
http://www.breskeby.com
@breskeby
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
