[jira] Resolved: (BUILDR-153) Tags aren't customizable anymore

["Assaf Arkin (JIRA)" <ji...@apache.org>]

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

Assaf Arkin resolved BUILDR-153.
--------------------------------

    Resolution: Fixed

Added Release.tag_name.  Use it to specify a different tag name for tagging the release in source control.

You can set the tag name or a proc that will be called with the version number, for example:

Release.tag_name = lambda { |ver| "foo-#{ver}" }

> Tags aren't customizable anymore
> --------------------------------
>
>                 Key: BUILDR-153
>                 URL: https://issues.apache.org/jira/browse/BUILDR-153
>             Project: Buildr
>          Issue Type: Bug
>          Components: Core features
>    Affects Versions: 1.3.2
>            Reporter: Matthieu Riou
>            Assignee: Assaf Arkin
>             Fix For: 1.3.3
>
>
> In Apache ODE we used to customize our tags on release by elegantly monkey-patching the tag method in Release (you know a monkey-patch is elegant when it works for you):
> class Release
>   class << self
>     def tag_with_apache_ode(version)
>       tag_without_apache_ode("APACHE_ODE_#{version.upcase}")
>     end
>     alias :tag_without_apache_ode :tag
>     alias :tag :tag_with_apache_ode
>   end
> end
> Apparently the tag method has been removed and now the tag name is directly the version. The bug isn't that much that this changed but more that there's no easy way anymore to tweak the name of your tag. Most Apache project should use the APACHE_FOO_X.X naming for their tag (btw do you?).

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