On 15 September 2010 15:20, Tomek Kaczanowski
<[email protected]> wrote:
> 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?
Yes. In my case I want a gradle project to be manipulated with task
like svn_checkout_trunk, svn_update, etc
> 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.
The plugin uses the SvnKit java library, so everything could be done.
The problem is that for each repository you must define the URL,
athorizations info, local folder eth. In my case I have used the
gradle project has container for such info. In your scenario, I think,
you should setup some variables and then call, directly, the SvnKit
library. Otherwise, you should wrap it with a gradle 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.
You don't need to change the maven-based project. I would wrap it with
a gradle project, setting up SvnKit plugin variables. Then I would add
a task, which depends from the checkout task, to run it. Something
like
build.gradle:
...
project("nasty_things") {
apply plugin: "SvnKit"
svnkit_root='https:\\....."
....
svnkit_username="...."
svnkit_password="...."
svnkit_project ='...'
task runit( dependsOn: 'svn_checkout_trunk' ) << {
...
// call ant or batch commands
}
}
>
> 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?
I think it can help if it is clear what a "current" project is. I am
not a Gradle expert but I have considered a Gradle project as a set of
tasks and artifacts which can be used to achive a goal. When you say
that you have to checkout wiki pages (artifacts), do something and
commit it (tasks), I think that such process can by achived by a
Gradle project composed by the Maven plugin and the SvnKit plugin.
This can be done without touching the remote repository. Some tasks
are provided by the plugins, some other task have to be created and
assembled together by you.
Hope I have been a little bit more clear
Ciao
Walter
>
> --
> Regards / Pozdrawiam
> Tomek Kaczanowski
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
