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.

Create compatibility layers for Redmine in an optional (non-core) plugin (Feature #247)

Added by Holger Just at 2011-03-01 10:00 am. Updated at 2011-03-02 11:54 pm.

Status:Open Start date:2011-03-01
Priority:Normal Due date:
Assignee:- % Done:

0%
Category:-
Target version:-
Remote issue URL: Affected version:

Description

This plugin could ease migration of Plugins from Redmine to ChiliProject by offering compatibility layers and emulating the existing APIs. We should not soil the internals of ChiliProject with legacy APIs.

Associated revisions

Revision f271e772
Added by Jean-Philippe Lang at 2008-03-16 05:52 pm

Add the following headers to email notifications (#830, #247):
  • X-Redmine-Host: host name defined in application settings
  • X-Redmine-Site: application title defined in settings
  • X-Redmine-Project: identifier of the project that the notification is related to, if any
  • X-Redmine-Issue-Id, -Author, -Assignee: ticket related info
  • X-Redmine-Topic-Id: identifies the thread a message belongs to

git-svn-id: http://redmine.rubyforge.org/svn/trunk@1265 e93f8b46-1217-0410-a6f0-8f06a7374b81

History

#1
Updated by Ian Freeman at 2011-03-01 09:36 pm

This plugin could also offer usability for future RedMine work without modifying core ChiliProject code.

#2
Updated by Eric Davis at 2011-03-02 12:28 am

I think this should be a core plugin, at least for 1.x and 2.x.

#3
Updated by Sergey Belov at 2011-03-02 07:44 am

why do you make it as a plugin? Is it not possible to keep old API and just write new APIs for Chili ?

#4
Updated by Felix Schäfer at 2011-03-02 08:25 am

Sergey Belov wrote:

why do you make it as a plugin? Is it not possible to keep old API and just write new APIs for Chili ?

I'm not sure we will keep all the current API (or at least probably not in the current form), we need to make clear that the supported bits are the current Redmine APIs, nothing that will be added later is guaranteed to be ported, and having stuff in a "Redmine" namespace in a project called ChiliProject, well, that might raise more questions than solve problems :-)

#5
Updated by Sergey Belov at 2011-03-02 08:35 am

I see :)
Well, I think that popular plugins will be ported to ChiliProject any way.

#6
Updated by Eric Davis at 2011-03-02 11:54 pm

Just for clarity, I'm talking about the internal API here not the external REST API. So the different methods defined on the classes, etc.

Also available in: Atom PDF