You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Alex Boisvert (JIRA)" <ji...@apache.org> on 2009/03/02 21:14:56 UTC

[jira] Resolved: (BUILDR-223) Release Task: customizable commit message

     [ https://issues.apache.org/jira/browse/BUILDR-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Boisvert resolved BUILDR-223.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.3.4

Patch applied.  Many thanks!

boisvert@sixtine:~/svn/buildr-222$ svn commit                                     
Sending        CHANGELOG
Sending        lib/buildr/core/build.rb
Sending        spec/core/build_spec.rb
Transmitting file data ...
Committed revision 749429.


> Release Task: customizable commit message
> -----------------------------------------
>
>                 Key: BUILDR-223
>                 URL: https://issues.apache.org/jira/browse/BUILDR-223
>             Project: Buildr
>          Issue Type: New Feature
>          Components: Core features
>            Reporter: Alexis Midon
>             Fix For: 1.3.4
>
>
> From a request on nuildr-dev mailing list:
> 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}" }

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.