On Tue, Dec 9, 2008 at 2:36 AM, Hervé Giraud <[EMAIL PROTECTED]> wrote:
> I have the following "problems" with the release task.
>
> The repo_url is defined like this :
>
> def repo_url
> svn('info').scan(/URL: (.*)/)[0][0]
> end
>
> On my system, "svn info" gives me "URL : http://..."; : there is a space
> after "URL".
> A better regexp could be : /URL\s?: (.*)/
For reference, could you provide the output of "svn -version" and "svn
info" ?
Next, our commit messages have a special format (we start with keywords),
> and
> we cannot use the buildr release without modifications.
> I can patch the Release class in my buildfile, but perhaps something
> similar to
> the release attribute in buildr 1.3.3 would be possible, like in the
> following exemple ?
>
> Release.tag_name = lambda { |ver| "foo-#{ver}" }
> Release.commit_format = lambda { |msg| "ADD: #{msg}" }
I think this would be a welcome enhancement. Do you want to submit a
patch?
Last point, it seems there is a problem with the 1.5.x version of the svn
> client.
> I'm using the command line svn client (1.5.4), and the scn.copy does not
> work.
>
> I think this message explains it :
> http://www.nabble.com/Error-when-creating-tags-from-working-copy-td19913357.html
> I did what they recommend, and it worked when I modify the "tag_release"
> method and I do a update just before the copy
I'm not sure if you're just sharing this information, or asking if this
should become standard in Buildr. It seems like a bug on Subversion's side
and doing a "svn update" before tagging, as opposed to earlier in the build
process, seems to be wrong... It creates a race condition and I wouldn't
want to tag different content than what was used during the release.
alex
