You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Gerolf Seitz (JIRA)" <ji...@apache.org> on 2010/04/27 15:54:34 UTC
[jira] Updated: (BUILDR-428) Let Repositories read release_to
property from Buildr.settings.build
[ https://issues.apache.org/jira/browse/BUILDR-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gerolf Seitz updated BUILDR-428:
--------------------------------
Summary: Let Repositories read release_to property from Buildr.settings.build (was: Let Repositories read release_to properties from Buildr.settings.build )
> Let Repositories read release_to property from Buildr.settings.build
> ---------------------------------------------------------------------
>
> Key: BUILDR-428
> URL: https://issues.apache.org/jira/browse/BUILDR-428
> Project: Buildr
> Issue Type: Improvement
> Components: Core features
> Affects Versions: 1.3.5, 1.4
> Reporter: Gerolf Seitz
> Priority: Minor
> Attachments: release_to.patch
>
>
> Repositories.release_to reads the repository settings from Buildr.settings.user, but not from Buildr.settings.build (coming from build.yaml next to the build file). This is also inconsistent to how Repositories.remote behaves.
> The attached patch first reads the release_to property from settings.user. If no such setting exists, settings.build is used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.