[GRADLE-68] Functionality to update gradle from svn trunk. Created: 25/Apr/08 Updated: 04/Jan/13 Resolved: 17/Oct/11
|Comment by Hans Dockter [ 29/Apr/08 ]|
Russel has written the following script for this functionality
#! /bin/sh gradleSvn=/home/Checkouts/Subversion/Gradle_Core_Trunk gradleExplodedDist=$gradleSvn/build/distributions/exploded gradleHome=$HOME/lib/JavaPackages/gradle-trunk items='' for item in bin gradle-imports lib LICENSE NOTICE plugin.properties README.txt do items="$items $gradleExplodedDist/$item" done ( cd $gradleSvn && rm -rf $gradleSvn/build $gradleSvn/build-resolver && ./gradlew -Dskip.test=true explodedDist ) rm -rf $gradleHome mkdir $gradleHome chmod 700 $gradleHome cp -rp $items $gradleHome
|Comment by Jon Cox [ 23/Jan/09 ]|
Ideally, it seems like this ought to be a groovy script
It would be nice if Gradle's core dependencies were kept to an
Personally, I believe that a developer on Windows would be a bit
Anyway, thanks for the script Russel. It is a nice contribution, and I may
Any thoughts on that?
|Comment by Hans Dockter [ 26/Jan/09 ]|
That is the way we say it in German.
The long term goal to implement this feature, is to provide a new 'version control system' project type where updating the project is part of the build if this is wanted.
|Comment by Russel Winder [ 20/Aug/09 ]|
On the one hand the script here - - which I have now changed almost beyond recognition – is out of date, so the issue can be marked as something and closed.
On the other hand, Gradle no longer builds when the equivalent of this script is used
|Comment by Adam Murdoch [ 16/Oct/11 ]|
Do we still need this?