[jira] [Closed] (BUILDR-142) Allow running project tasks from a top directory in the same way as after 'cd' to the project's base dir

["Peter Donald (JIRA)" <ji...@apache.org>]

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

Peter Donald closed BUILDR-142.
-------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 1.5)
                   1.3.4

It looks like this was implemented a long time ago in 1.3.4 so closing the issue

> Allow running project tasks from a top directory in the same way as after 'cd' to the project's base dir
> --------------------------------------------------------------------------------------------------------
>
>                 Key: BUILDR-142
>                 URL: https://issues.apache.org/jira/browse/BUILDR-142
>             Project: Buildr
>          Issue Type: New Feature
>          Components: Core features
>    Affects Versions: 1.3.2
>            Reporter: Ittay Dror
>            Assignee: Victor Hugo Borja
>             Fix For: 1.3.4
>
>         Attachments: 0001-rspec-for-p-switch.patch, 0002-added-p-switch.patch, 0003-allow-project-names-with-path-separators.patch, 0004-list-project-names-with-file-separator.patch
>
>
> Currently, to run a specific project's tasks, there are two alternatives:
> 1. cd to the project's base dir and run 'buildr' or 'buildr <tasks>'. 
> 2. run 'buildr <project name>:<task1> <project name>:<task2>'
> The first one requires 'cd' and is not comfortable to run from an IDE. The second one is verbose, cannot rely on default tasks and is confusing to new users. 
> Users usually expect the behavior as in 'make' or 'tar'. That is, a switch (usually -C) that first does a 'cd' for you and then continues to run as usual. This is an issue I'm faced with right now. People are confused when I tell them to run 'buildr top_project:sub_project:build'. Also, people don't think of projects as tasks. This is an implementation detail of Buildr, not something that people comprehend intuitively (at least my users)
> Moreover, several projects may share the same base directory (I intend to use this to compile the same source tree with different configurations), so a 'cd' will cause both to compile.
> Suggestion: add a '-p' switch that tells buildr the "local project" to use when running. Then users simply invoke 'buildr -p top_project:sub_project' and all default tasks run. 
> Suggestion 2: since project names will usually correspond with a directory layout, allow to specify them with File::SEPARATOR. this way, command line completion is easy (especially in windows).



--
This message was sent by Atlassian JIRA
(v6.1#6144)