Feature request: mechanism to do 'svn update'

[wenslayer]

Part of my build requires obtaining some binaries in a Subversion path. While I can use the SvnCheckout task to first retrieve the material, I only want to do a 'svn update' for subsequent runs (since it takes a fair amount of time), but SvnCheckout insists on the workspaceDir being empty.

Is there a way to effectively do an 'svn update' with this plugin (does it need a new option to support this), or would this be a different task type?

Thanks for your help.

[martoe]

Currently there is no "svn update" tasks, but I think this is a good idea. I guess I can implement it by the end of the week, configuration just like the "checkout" task - ok for you?

[wenslayer]

Thanks, I think that would work. I need to effectively do a checkout (if it doesn't exist) or update (if it does), so if I don't need too much logic to achieve that, that would be ideal.

Perhaps if I can call both SvnCheckout followed by SvnUpdate, without SvnCheckout complaining if the workspaceDir already exists (optional flag?), that would be great? (Or can I achieve that by declaring the workspace as an output.file for the SvnCheckout task so it skips if it's already there?)

[pjean]

+1 for the "svn update" and if you have more time, I'm interested for "svn switch" too :)

[martoe]

@wenslayer plugin version 1.3 released - you may either use the new "SvnUpdate" task or - preferrably - do a SvnCheckout with "update=true"
Pls check if this works out for you...

[pjean]

Works like a charm but without output. Is it possible to get output from SVNKit ?

[martoe]

@pjean I'll check. Could you open a new issue for that? Thx!

[wenslayer]

Works great -- thank you very much! (And kudos for the corresponding doc updates)