I think the place where we store the version.properties is not the
place where it should live. Right now it lives in gradle-core. But in
fact the version is the version of the distribution not of the
library. That means that we would need to check for the changed input
properties of all our archives to see whether we need a new version
file. That would be possible. But I think a simpler approach would
work as well. I think we should get rid of the version.properties file
all together. Instead the GradleVersion class could read the version
from one of the gradle libraries in GRADLE_HOME/lib. We would have to
give up of the buildTime attribute in gradle -v. But I don't think
this attribute is relevant. Either you have a released version or you
have a version with a timestamp. The latter gives you all the
information you need for a snapshot.
In a snapshot build we would then always use a new timestamped version
(as we do now). But it would only affect the naming of the archives
not the content. With Adam's planned optimization for output file
changes only (which in the case of an archive just renames the
archive), our build could then make full use of the incremental build
optimization. In fact the output file changes optimization is
necessary to make all that work. Otherwise our (unchanged) archives
are not in sync with the current timestamped version.
- Hans
--
Hans Dockter
Gradle Project Manager
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
