You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Ittay Dror (JIRA)" <ji...@apache.org> on 2008/10/29 10:18:44 UTC
[jira] Created: (BUILDR-191) allow 'default' task per project
allow 'default' task per project
--------------------------------
Key: BUILDR-191
URL: https://issues.apache.org/jira/browse/BUILDR-191
Project: Buildr
Issue Type: Wish
Affects Versions: 1.3.2
Reporter: Ittay Dror
Fix For: 1.3.4
Currently, the 'default' task is only a top level task. This means that I can't set default tasks per project that will be called when the user just runs the build. If all projects are in the same "family" (e.g., all are java), it isn't such an issue, because of recursive tasks. But if projects are not of the same family, then they may not have the same set of tasks (or they may not make sense).
I suggest making 'default' a recursive task, with an ability to change its dependencies in the project definition
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-191) allow 'default' task per project
Posted by "Assaf Arkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643521#action_12643521 ]
Assaf Arkin commented on BUILDR-191:
------------------------------------
The default task is 'build', which makes a lot of sense given that Buildr is a build system. We use Rake's 'default' task to invoke 'build', which gives additional flexibility if you decide to do something different from the default (no pun intended) behavior. But the default behavior already provides a top-level task which executes the same task in every project, recursively.
> allow 'default' task per project
> --------------------------------
>
> Key: BUILDR-191
> URL: https://issues.apache.org/jira/browse/BUILDR-191
> Project: Buildr
> Issue Type: Wish
> Affects Versions: 1.3.2
> Reporter: Ittay Dror
> Fix For: 1.3.4
>
>
> Currently, the 'default' task is only a top level task. This means that I can't set default tasks per project that will be called when the user just runs the build. If all projects are in the same "family" (e.g., all are java), it isn't such an issue, because of recursive tasks. But if projects are not of the same family, then they may not have the same set of tasks (or they may not make sense).
> I suggest making 'default' a recursive task, with an ability to change its dependencies in the project definition
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (BUILDR-191) allow 'default' task per project
Posted by "Assaf Arkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Assaf Arkin closed BUILDR-191.
------------------------------
Resolution: Fixed
> allow 'default' task per project
> --------------------------------
>
> Key: BUILDR-191
> URL: https://issues.apache.org/jira/browse/BUILDR-191
> Project: Buildr
> Issue Type: Wish
> Affects Versions: 1.3.2
> Reporter: Ittay Dror
> Fix For: 1.3.4
>
>
> Currently, the 'default' task is only a top level task. This means that I can't set default tasks per project that will be called when the user just runs the build. If all projects are in the same "family" (e.g., all are java), it isn't such an issue, because of recursive tasks. But if projects are not of the same family, then they may not have the same set of tasks (or they may not make sense).
> I suggest making 'default' a recursive task, with an ability to change its dependencies in the project definition
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.