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 2010/09/30 06:53:32 UTC
[jira] Resolved: (BUILDR-518) Load _buildr.rb or .buildr.rb from
same directory as Buildfile if they exist
[ https://issues.apache.org/jira/browse/BUILDR-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Boisvert resolved BUILDR-518.
----------------------------------
Assignee: Alex Boisvert
Resolution: Fixed
Patch applied. Thanks Peter!
boisvert@smudge:~/svn/buildr-trunk$ svn commit -m "BUILDR-518 Load _buildr.rb or .buildr.rb from same directory as Buildfile if they exist (Peter Donald)" .
Sending CHANGELOG
Sending lib/buildr/core/application.rb
Sending spec/core/application_spec.rb
Transmitting file data ...
Committed revision 1002948.
> Load _buildr.rb or .buildr.rb from same directory as Buildfile if they exist
> ----------------------------------------------------------------------------
>
> Key: BUILDR-518
> URL: https://issues.apache.org/jira/browse/BUILDR-518
> Project: Buildr
> Issue Type: New Feature
> Affects Versions: 1.4.3
> Reporter: Peter Donald
> Assignee: Alex Boisvert
> Fix For: 1.4.3
>
> Attachments: LoadBuildrFileFromLocalDir.diff
>
>
> Currently you can load user specific customizations from the home directory (i.e. ~/.buildr/buildr.rb) but you can not load per project customizations. The attached patch does just this. The file ".buildr.rb" or "_buildr.rb" is loaded from the same directory as the buildfile. The choice was made not to use a file named "buildr" because this can shadow the buildr script on systems that allow you to execute ruby files without their extensions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.