Allow setting TargetVersion+Category to null / access names from Memberships

[matthiasblaesing]

This is the result of moving redminenb to the new major version of redmine-java-api.

Most changes are very smooth and work quite good. These two changesets address two issues:

• Memberships are used to enumerate Users per project in redminenb, so I used the Memberships directly in the past, as these already contain the necessary data (the id and name of the group/user). In the current incarnation this information is discarded by the bindings. With this changeset the names of the groups and users are extracted from the reply
• The two attributes category and and targetVersion could not be unset - the null value was discarded from the updateset. This is attributed in the second changeset by introducing a generic setter for "Identifiable" attribute values.

Please note: The first change was tested by the added unittests, the second set is currently untested, as the testsystem is unresponsive. I ran the second set through manual tests, that showed these change to be working.

Please check if the added unittests for the second part work as expected. Thanks!

[alexeyOnGitHub]

I brought the dev VM with the test Redmine back.

let's use one PR per commit/feature to simplify both review and merge?

[matthiasblaesing]

Thank you for merging this. For you comments: I agree mostly. I had the basics of a followup PR prepared, but I just compared the diffs and while the names of the tests might not match 100%, separating the tests nearly doubles the code - I suggest to keep it this way.

[alexeyOnGitHub]

@matthiasblaesing does the current version work for you? I will release it as 3.0.0 if yes

[matthiasblaesing]

It looks good - my client currently shows some issues I have to tackle before I can think about moving to 3.0.0 fully (not related to the api!), but I checked:

• all issue fields that should be settable are settable
• all issue fields, that should be unsettable/eraseable were erasable (parent task, start/due date, assignee, category, target version, estimated time)
• issues are correctly updated and retrieved
• custom text fields could be updated
• custom multi select lists were updated
• custom boolean values were updated and erasable
• time entries could be done
• watchers were editable
• basic searching works
• executing server side queries works

So I would say: I think this is good to go. I really look forward to move back to the master branch! Thank you for your work.

[alexeyOnGitHub]

alright, I will release this as 3.0.0