This is getting awkward... Maven Bundle Plugin does not only rely on old Maven Dependency Tree, but also targets Maven 2.x [1]. What's worse, Maven Dependency Tree 2.x also relies on Maven 2.x [2].
I tried building Maven Dependency Tree 2.2 against Maven 3.x and found that it uses removed APIs, and that patching it would make a huge code change. Maybe someone else would have a better skill than me to do the job, but I simply don't think this is a good or sustainable idea... [1]: https://github.com/apache/felix/blob/ae8f8bbeb6ecaae8e2d27824077c5d39c54e54a5/pom.xml#L182 [2]: https://github.com/apache/maven-dependency-tree/blob/maven-dependency-tree-2.2/pom.xml#L53
signature.asc
Description: OpenPGP digital signature
__ This is the maintainer address of Debian's Java team <http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>. Please use debian-j...@lists.debian.org for discussions and questions.
