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/08/04 06:15:44 UTC
[jira] Created: (BUILDR-121) allow partial checkout
allow partial checkout
----------------------
Key: BUILDR-121
URL: https://issues.apache.org/jira/browse/BUILDR-121
Project: Buildr
Issue Type: Improvement
Components: Dependency management
Reporter: Ittay Dror
In a group environment, not all team members will be interested in all modules in the source tree. Also, building those modules may take long. An option is for each team member to checkout only those modules he is working on and take the rest from the repository. So when defining dependencies, if the project's source exist, use the project's packages tasks as dependencies (as today), but if the project was not checked out, use it as a repository artifact.
The fix is simple in the method artifacts:
when Project
if not File.exists?(spec.base_dir)
set |= artifacts("#{project.group}:#{project.name.split(':').last}:jar:#{project.version})
else
set |= artifacts(spec.packages)
....
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-121) allow partial checkout
Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839469#action_12839469 ]
Antoine Toulme commented on BUILDR-121:
---------------------------------------
I would rather not work in such an environment. I need to know what I am working with and partial checkout blurs the line between what code and what jars are running.
I would recommend to avoid this kind of configuration and keep code separated in small, manageable repositories. I would recommend also to make sure that the code, if it is released together is built and checked out together.
> allow partial checkout
> ----------------------
>
> Key: BUILDR-121
> URL: https://issues.apache.org/jira/browse/BUILDR-121
> Project: Buildr
> Issue Type: Improvement
> Components: Dependency management
> Reporter: Ittay Dror
>
> In a group environment, not all team members will be interested in all modules in the source tree. Also, building those modules may take long. An option is for each team member to checkout only those modules he is working on and take the rest from the repository. So when defining dependencies, if the project's source exist, use the project's packages tasks as dependencies (as today), but if the project was not checked out, use it as a repository artifact.
> The fix is simple in the method artifacts:
> when Project
> if not File.exists?(spec.base_dir)
> set |= artifacts("#{project.group}:#{project.name.split(':').last}:jar:#{project.version})
> else
> set |= artifacts(spec.packages)
> ....
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.