Merge output parameters
Merge pull request #272 from sroze/patch-1

Merge output parameters
Add support of `All` constraint
Merge pull request #274 from sroze/patch-2

Add support of `All` constraint
Fix typo

$route parameter of ApiDocExtractor::get is a string. Passing a Route object throw an error.
Rework documentation, add reference config
Fix travis-ci config
Fix DumpCommand to generate html with/out sandbox

api:doc:dump --format=html always disables the Sandbox since the check in
DumpCommand seems to be wrong. Fixed that as well as introduce a dummy
Request Object as the layout.html.twig expects an app.request object.
Suppressed the auto-scrolling on click and fixed initial-jump issues.

For the initial auto-scrolling to the selected route in location.hash:
 - Fixed typo in the calculation of the offset-top position.
 - Fixed requesting the selected route that has special chars (e.g. "/content/{page}")
 - Fixed for refreshes with F5. It needs a setTimeout workaround to get that working in Webkit.
    It needs also in Firefox a other dom element to fire scrollTop at.

Fixed also some old .delegation calls, which are deprecated in jQuery 1.7.

Why suppressing auto-scrolling on click:
When clicking through all methods it's very annoying when the browser always jumps to the clicked method,
especially when you go through all methods from bottom to up. This jump is unexpected and disturbing.
Merge pull request #293 from marcj/patch-1

Remove the annoying scroll-jumping on method-click.
Outsourced the parsing of the classic phpDoc into a extra handler.

This makes it possible to overwrite route-requirements/description through a own handler.
Otherwise it's impossible e.g. to overwrite a `@param string $page` annotation via a own handler.
Merge pull request #294 from marcj/outsource-classic-phpdoc

Outsourced the parsing of the classic phpDoc into a extra handler.
cs
Merge pull request #290 from rajasaur/dumpcommand_bugfix

Fix DumpCommand to generate html with/out sandbox
Fix undefined index in AbstractFormatter
Use only JMS/GroupExclusion if groups are there

When no groups are given in the ApiDoc, there should be no GroupExclusion and the Entity should be parsed wihtout exclusions.

Otherwise only the "Default" group of the Entity would be parsed, which may not be used.

The ApiDoc should not enforce the Entity to be grouped with "Default", to generate a "full-view" of it.
Merge pull request #304 from h4cc/patch-2-squashed

Use only JMS/GroupExclusion if groups are there
[Test] Extended Class test case
Merge PR #298 from 'skler/extended_class
select used parsers