There are some issues that I'd really like to see fixed before 1.0 is released.
The most important ones are all variations of the same general problem:
GRADLE-1298 - Change in filtered resource not picked up by archive tasks
GRADLE-1646 - Copy tasks do not consider filter/expansion properties in
up-to-date checks
GRADLE-1276 - processResources task considered up-to-date although its spec has
changed
I consider these quite crucial since they cause a certain distrust in the
intelligence of the whole Gradle UP-TO-DATE detection - one of the biggest and
most important Gradle feature.
The 1.0 release will likely spark a broader adoption by people that care about
a non-zero major version. I'd rather do an M6 and M7 than release Gradle with
this feature in a broken state.
Also on my personal list - ordered by importance - are
GRADLE-971 - fileMode not working for the copy task
GRADLE-443 - Generated POM dependencies do not respect custom artifactIds
GRADLE-1200 - Generated POM does not contain packaging, organization is simply
org.apache.maven.model.Organization.toString()
But those are much less critical, merely nice to have, in comparison to the one
big problem above.
Thanks for all of your hard work,
Joern.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
