Thank you for reporting this issue, I have been able to reproduce it.
This is caused by an incompatibility between the dependency plugin 2.7
and Maven 3.3. You can work around this issue by forcing the use of a
more recent version of the plugin (2.8 or later):
To fix this we have to cancel the modification of the super pom
downgrading the version of the dependency plugin from 2.8 to 2.7:
This is the maintainer address of Debian's Java team
debian-j...@lists.debian.org for discussions and questions.