buildr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Assaf Arkin (JIRA)" <j...@apache.org>
Subject [jira] Closed: (BUILDR-83) Dependency checks as part of the release process
Date Fri, 26 Sep 2008 21:19:44 GMT

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

Assaf Arkin closed BUILDR-83.
-----------------------------

    Resolution: Fixed

Added tests for the other platform (i.e. JRuby when staging on Ruby and vice versa).
As far as I can tell, no way to tell (given RubyGems API) which platforms we're looking at
for a given Gem, so we'll have to trust the manual process to uncover that.

> 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
>            Assignee: Assaf Arkin
>             Fix For: 1.3.3
>
>
> 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.


Mime
View raw message