Sorry but I don't see why I am assigned on this.
To me, this is a major regression that must be adressed as soon as possible. The API doc is not decorative and something nice to have, it is needed for debugging and used quite commonly in all our demonstration

I haven't understood why I was assigned to it too.
This was not discussed during Sprint Planning so you need to be warned as a PO and I can't add you as a simple watcher...
In my opinion, every developper should know how to declare such features. If not, I'd be happy to explain it.

Anyway, I've reassigned it to me and I've finished the job to create a separate feature in 97690 PS2.

Note there is no point to declare this new feature in integration/distribution.
Swagger can already be installed in official packages since it is inherited from netconf.
Thus it is still present in official distros.
If I agree it is problematic for people donwloading and debugging code base,
the term "major regression" is improper here IMO for this reason and also because  it is not really a tpce feature.

I modified the initial description not to say it is decorative but because we do not strictly need it to run the controller.
Separating the minium set of vital dependencies from optional ones is a common best practice.
Eventually the controller now works but swagger still not. It raises warnings after installation when trying to parse an ospf model.
I filled a bug in https://jira.opendaylight.org/browse/TRNSPRTPCE-545 for more details.
That's the best I can do at this stage.