Jredmine does not handle Redmine plug-ins that modify database
|Assignee:||Tony Chemit||% Done:|
As in subject.
Jredmine does not like Redmine plug-ins that modify redmine's tables/objects.
Actually, I had problems with backlogs (http://www.redminebacklogs.net/) and
DMSF (http://code.google.com/p/redmine-dmsf) plugins, but the problem seems generic
for me and can be stated as follows:
if Redmine tables contains any extra-columns (installed by plug-ins), then jredmine fails.
For backlogs and dmsf this concerns Version, Issue and project entities.
I modified jredmine code to handle those specific extra-columns, but this is
no-solution: any new plug-in that modifies database will break it.
I think The Right Way would be just to ignore unknown project/issue/whatever
properties retrieved from Redmine.
To reproduce, it is enough to install DMFS or backlogs plugin and e.g. try to
create or update version in Redmine using jredmine.
#2 Updated by Tony Chemit about 1 year ago
Maciej Maczynski a écrit :
Ahhh...sorry - I've just noticed this may be duplicate of #2039.
And this may indeed be easier to prepare proper data set at Redmine side then to handle unknown elements in Java part.
No problem I will try to fix this big problem (to me) next week and then launch a release :)
Anyway thanks for report.