On 08/25/16 20:02, Markus Koschany wrote:
I think the issue is not unrelated to protobuf 3.0.0. Yesterday I filed
https://bugs.debian.org/835358 because protobuf used a wrong pom.xml
file which provides important information like groupids or artifactids.

So this bug got resolved today but now I see that the new pom.xml file
differs in one important aspect from earlier ones, e.g. from  version
2.6.1 [1]. The pom.xml file for version 3.0.0 [2] declares junit and
easymock as dependencies while the older one sets the scope to test
only. At the moment the dependencies are required at build time and I
think that shouldn't be necessary.

I'm attaching a patch that should address this issue for all
reverse-dependencies but it must be applied in src:protobuf. If there
are no objections, I'm going ahead and file another bug report tomorrow.

That sounds good, please go ahead and file the protobuf bugreport. Since libprotobuf-java pulls in those dependencies, it should either depend on the respective packages or not require them as per your patch.

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

__
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.

Reply via email to