Etienne Studer wrote: > > Are you saying that if I write a custom Task and put it into a script that > I put on a server, then that custom Task will be cached in my project and > hence, it will also be available when I'm offline. > And, if so, I could offer the properties through getters of the task > (rather than as properties in a properties file). >
No, I'm just saying that it might be better to share higher-level elements (a repository declaration, a preconfigured task, etc.) than low-level properties which need to be applied in each and every build. Of course this is just a general remark and I can't tell if it applies to your situation. Regarding the caching of shared scripts, watch http://issues.gradle.org/browse/GRADLE-1768. -- Peter Niederwieser Principal Engineer, Gradleware http://gradleware.com Creator, Spock Framework http://spockframework.org Twitter: @pniederw -- View this message in context: http://gradle.1045684.n5.nabble.com/How-to-share-properties-across-projects-tp4744577p4744770.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
