buildr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antoine Toulme (JIRA)" <>
Subject [jira] Commented: (BUILDR-121) allow partial checkout
Date Sun, 28 Feb 2010 18:50:06 GMT


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:
>             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
> The fix is simple in the method artifacts: 
> when Project
>   if not File.exists?(spec.base_dir)
>     set |= artifacts("#{}:#{':').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.

View raw message