You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Daniel Harrington (JIRA)" <ji...@apache.org> on 2009/11/12 18:07:39 UTC
[jira] Created: (BUILDR-339) Use Rubyforge dependency >= 2.0.0
Use Rubyforge dependency >= 2.0.0
---------------------------------
Key: BUILDR-339
URL: https://issues.apache.org/jira/browse/BUILDR-339
Project: Buildr
Issue Type: Improvement
Reporter: Daniel Harrington
Priority: Critical
Depending on Rubyforge 1.0.5 causes problems with Jeweler, because Jeweler depends on Rubyforge >= 2.0.0.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (BUILDR-339) Use Rubyforge dependency >= 2.0.0
Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antoine Toulme resolved BUILDR-339.
-----------------------------------
Fix Version/s: 1.4
Resolution: Fixed
This was fixed in 1.4 (or 1.3.5 ?), we now run with rubyforge 2.0.3.
> Use Rubyforge dependency >= 2.0.0
> ---------------------------------
>
> Key: BUILDR-339
> URL: https://issues.apache.org/jira/browse/BUILDR-339
> Project: Buildr
> Issue Type: Improvement
> Reporter: Daniel Harrington
> Priority: Critical
> Fix For: 1.4
>
>
> Depending on Rubyforge 1.0.5 causes problems with Jeweler, because Jeweler depends on Rubyforge >= 2.0.0.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.