Interactive API documentation

Supersedes !5.

> This feature supports developers with an interactive documentation of
> the REST API from the ARSnova Backend.

Changes & Todos:
* Branch & code clean up
  * Rebase on master
  * Squash related commits authored by the same developer
  * Remove commits whose code has been reverted later on
  * Fix whitespaces
* Remove implementation notes (Java signatures are not helpful)
* Improve documentation of responses (Tom Käsler)
  * Do not define status messages for methods individually (DRY)
* Create JSON at compile-time by using
  [swagger-maven-plugin](https://github.com/kongchen/swagger-maven-plugin) (Tom Käsler)

See merge request !10

remove swagger annotation from feedbackcontroller, coursecontroller and getter and setter for sortOrder

add swagger maven plugin configuration

remove spingfox for ApiIgnore direction
use swagger-maven-plugin to generate swagger.json before compiling rather than
 dynamically generate it on request

Daniel Gerhardt authored 9 years ago and Tom Käsler committed 9 years ago

Reasons:
* not used consistently
* Java signatures are not helpful
* Return type should not be hard-coded in a String

Statistics model now correctly uses value instead of notes for
documentation of properties.

Daniel Gerhardt authored 9 years ago and Tom Käsler committed 9 years ago

* Fix inconsistent whitespaces
* Remove unused imports

Tjark Wilhelm Hoeck authored 9 years ago and Tom Käsler committed 9 years ago

added labeled deprecated rest endpoints to api documentation, commentet and included the feedbackController

Tjark Wilhelm Hoeck authored 9 years ago and Tom Käsler committed 9 years ago

Edited tests to support the new EnableWebMvc Annotation from the ExtraConfig file. No more test errors.

The config parameter is now used instead of the hard-coded value '5'.

Conflicts:
	pom.xml

All feature settings are replaced by the received object so the use of
PATCH does not make sense here. The session is "patched" but the HTTP
verb always relates to the URL which refers explicitly to features in
this case.

See https://tools.ietf.org/html/rfc5789.