[
https://issues.apache.org/jira/browse/BUILDR-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12610380#action_12610380
]
Assaf Arkin commented on BUILDR-83:
-----------------------------------
[ ] Test with both MRI and JRuby specs, since they use different dependency
sets.
[x] For each dependency, verify that the Gem is available on the RubyForge
server.
[ ] That goes for platform variance, e.g. RJB has both ruby and win32 platform,
both must be checked for existence.
[x] From dependency list determine the order in which dependencies will be
loaded, and make sure the dependency list is in that order.
> Dependency checks as part of the release process
> ------------------------------------------------
>
> Key: BUILDR-83
> URL: https://issues.apache.org/jira/browse/BUILDR-83
> Project: Buildr
> Issue Type: Improvement
> Components: Core features
> Affects Versions: 1.3.1
> Reporter: Assaf Arkin
> Fix For: 1.3.2
>
>
> Add automated tasks to release process to make sure we have the right set of
> dependencies:
> - Test with both MRI and JRuby specs, since they use different dependency
> sets.
> - For each dependency, verify that the Gem is available on the RubyForge
> server.
> - That goes for platform variance, e.g. RJB has both ruby and win32
> platform, both must be checked for existence.
> - From dependency list determine the order in which dependencies will be
> loaded, and make sure the dependency list is in that order.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
