Hello,

antlr4-maven-plugin provides maven coordinates carrying package version
only:

/usr/share/maven-repo/org/antlr/antlr4-maven-plugin/4.9.2/antlr4-maven-plugin-4.9.2.jar
/usr/share/maven-repo/org/antlr/antlr4-maven-plugin/4.9.2/antlr4-maven-plugin-4.9.2.pom

This is difficult to depend on, as each version bump affects the path.
Thus it would be nice to have debian-versioned coordinates as well:

/usr/share/maven-repo/org/antlr/antlr4-maven-plugin/debian/antlr4-maven-plugin-debian.jar
/usr/share/maven-repo/org/antlr/antlr4-maven-plugin/debian/antlr4-maven-plugin-debian.pom

Or is there a reason why debian-versioned coordinates are not provided?

Andrius

severity 1065660 serious
tags 1065660 + ftbfs
thanks

Hello.

I noticed that chemicaltagger currently FTBFS and I believe it is because
of this problem, so to avoid duplicate reports, I'm raising this one to serious.

A build log for chemicaltagger is available here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/chemicaltagger.html

By raising the severity of this bug, I'm assuming that this will be eventually fixed
in antlr4-maven-plugin and chemicaltagger will not need to be changed to build again,
but I really have no idea if such thing will happen. If it does not, we would need
a different FTBFS bug for chemicaltagger so that it's fixed there.

Thanks.

Hi,

I think this FTBFS is caused by change in some other dependency as
antlr4-maven-plugin did not change since last successful build of
chemicaltagger.

chemicaltagger could in principle be adapted to detect the version of
antlr4-maven-plugin and build against that, but I would like to
understand why antlr4-maven-plugin exports only the strictly versioned
maven coordinates. This seems quite unusual for Java packages, but as
said, there might be a reason for this.

Best,
Andrius

Hi,

I have just fixed the FTBFS bug in chemicaltagger/1.6.2-4, it was a
separate issue, unrelated to antlr4-maven-plugin.

Best,
Andrius