ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Implement requires_chiliproject and requires_chiliproject_plugin methods (Feature #275)

Added by Holger Just at 2011-03-13 03:44 pm. Updated at 2011-08-27 03:32 pm.

Status:Closed Start date:2011-03-13
Priority:Normal Due date:
Assignee:Holger Just % Done:

0%
Category:Plugin API
Target version:2.2.0
Remote issue URL: Affected version:master

Description

These methods are used for dependencies in plugins.

I propose to change the syntax for those and adopt the rubygems dependency syntax. Besides much more flexibility we can also reuse their code. And we can use the spermy operator in dependency definitions

1requires_chiliproject "~> 1.1.1"

A pull request is going to get attached here.

@Eric: please review it quickly once I'm done.

Related issues

related to Bug #256: requires_redmine_plugin should defer loading plugins if n... Closed 2011-03-03
related to Task #596: Document plugin dependency mechanisms with rubygems/rails 3 Open 2011-08-27

Associated revisions

Revision 1796fddd
Added by Holger Just at 2011-08-21 02:47 pm

[#275] Add requires_chiliproject. We now use the rubygems dependency syntax.

Revision eae5c9af
Added by Holger Just at 2011-08-21 03:16 pm

[#275] Use ChiliProject::VERSION for new code

History

#1
Updated by Holger Just at 2011-03-13 03:47 pm

Oh, one important change is the semantic of requires_chiliproject "1.1.0" compared to requires_redmine "1.1.0".

The former means: "I need exactly ChiliProject 1.1.0, and 1.1.1 does not qualify". The latter however means: "I need any Redmine version >= 1.1.0".

#2
Updated by Felix Schäfer at 2011-08-02 10:18 am

I've just come across a plugin I'd need this for, especially considering the switch to aaj in 2.0.

  • Target version set to 2.2.0
  • (deleted custom field) set to master

#3
Updated by Holger Just at 2011-08-21 01:34 pm

I pushed the code for requires_chiliproject to master. Still missing is the code for requires_chiliproject_plugin. But here, I'd first like to pull #256.

Also I moved Redmine::VERSION to ChiliProject::VERSION as the single point of truth. Redmine::VERSION is still available as a compatibility API.

#4
Updated by Holger Just at 2011-08-27 03:17 pm

Closing this for now.

The plugin requirements, i.e. requires_chiliproject_plugin should be properly done using the plugin's Gemfile once we have all our plugins as gems. This will come with the switch to Rails 3.1 engines. Which will be just awesome btw.

  • Status changed from Open to Closed

#5
Updated by Felix Schäfer at 2011-08-27 03:32 pm

Holger Just wrote:

The plugin requirements, i.e. requires_chiliproject_plugin should be properly done using the plugin's Gemfile once we have all our plugins as gems. This will come with the switch to Rails 3.1 engines. Which will be just awesome btw.

Added #596 to make sure to document it properly.

Also available in: Atom PDF