On Mon, 2016-02-01 at 12:18 +0100, Andreas Tille wrote: > I admit I have no idea how > to > craft the suggested publishedRule. The maven.publishedRules usually gets generated with comments to help you if you used mh_make. If not, check another project for reference such as [1]. Adding the line below should work: org.apache.maven maven-core jar s/.*/3.x/ > > However, what makes me really suspicious is: > > $ grep maven.*-core-java maven-scala-plugin_3.2.2-1_amd64.build > Selecting previously unselected package libmaven2-core-java. > Preparing to unpack .../libmaven2-core-java_2.2.1-24_all.deb ... > Unpacking libmaven2-core-java (2.2.1-24) ... > Selecting previously unselected package libmaven3-core-java. > Preparing to unpack .../libmaven3-core-java_3.3.9-3_all.deb ... > Unpacking libmaven3-core-java (3.3.9-3) ... > Setting up libmaven2-core-java (2.2.1-24) ... > Setting up libmaven3-core-java (3.3.9-3) ... > > > Is there any reason that libmaven2-core-java is implicitly dragged in > by > other Build-Depends and may be this is creating the problem? I wouldn't worry about this. It just means another package depends on a different version of the library. Both libmaven2-core-java and libmaven3-core-java are able to coexist on the same system. In your case, it's brought in by libmaven-docck-plugin-java, a direct dependency in the maven-scala-plugin. Your problem is that poms get rewritten in the build phase by maven- debian-helper. They change the version of dependencies to `debian` because bananas (there really is a reason, but its not important here). This happens regardless whether libmaven2-core-java gets pulled in by dpkg. We just need to tell maven-debian-helper to use a specific version, 3.x, instead of `debian` which redirects to 2.2.1 likely to maintain compatibility. This is what the maven.publishedRules file is for. Andrew [1] https://github.com/googlei18n/libphonenumber/blob/master/debian/mav en.publishedRules
Attachment:
signature.asc
Description: This is a digitally signed message part