Walter, maybe I didn't make myself clear.
The point is that SvnKit plugin (AFAIK) can be used to manipulate the same project that you use it on, right? What I'm suggesting is to make it possible to use this plugin to access and work with any SVN resources - i.e. completely outside the "current" project. >> I'm asking because I'm interested in the following scenario. I would >> like to fetch some other (maven project) from svn to some temp dir and >> then do some nasty things with it. Can I use SvnKit plugin for this? > > What about to define a project for your nasty things? ;) Then you > could associate the SvnKit plugin to it. This another maven-based project that I'm not allowed to change in any way. But I want to fetch it, run it, do something with results etc. Another example. I have a project on google code. It has a wiki page that is accessible via SVN (which means I can checkout wiki pages, amend it, and commit). Now consider some *other* gradle build that would do exactly this: - checkout wiki pages from arbitrary url (http://google.code/whatever/mywiki/file.txt) - do something with it - commit it Is it something that SvnKit plugin can help me with? Or is it only intended to commit, tag, branch the "current" project? -- Regards / Pozdrawiam Tomek Kaczanowski --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
