On Wed, Jun 27, 2018 at 12:33 PM Emmanuel Bourg <ebo...@apache.org> wrote: > > Le 27/06/2018 à 12:30, Mathieu Malaterre a écrit : > > > What should I do with: > > > >> dpkg --search /usr/share/maven-repo/junit/junit/*/* > > Found /usr/share/maven-repo/junit/junit/4.x/junit-4.x.pom in junit4 > > Found /usr/share/maven-repo/junit/junit/3.8.2/junit-3.8.2.pom in junit > > Found /usr/share/maven-repo/junit/junit/3.x/junit-3.x.pom in junit > > Found /usr/share/maven-repo/junit/junit/4.12/junit-4.12.pom in junit4 > >> dpkg --status junit4 > > [error] Package junit4 (4.12) is already installed and contains a > > possible match, > > but I cannot resolve library junit:junit:jar:${junit.version} in it. > > Try with the tests and the javadoc disabled. They can be enabled later.
OK. I can get a little further. 3 errors I'd like to resolve: 1. > dpkg --search > /usr/share/maven-repo/org/apache/maven/plugins/maven-war-plugin/*/* dpkg failed to execute successfully > apt-file search > /usr/share/maven-repo/org/apache/maven/plugins/maven-war-plugin Found /usr/share/maven-repo/org/apache/maven/plugins/maven-war-plugin/2.2/maven-war-plugin-2.2.pom in libmaven-war-plugin-java > dpkg --search /usr/share/java/maven-war-plugin.jar dpkg failed to execute successfully > apt-file search /usr/share/java/maven-war-plugin.jar apt-file failed to execute successfully [error] Cannot resolve Maven dependency org.apache.maven.plugins:maven-war-plugin:maven-plugin:${war.plugin.version}. If you know a package that contains a compatible dependency, try to enter a substitution rule of the form s/groupId/newGroupId/ s/artifactId/newArtifactId/ jar s/version/newVersion/ here: 2. > dpkg --search /usr/share/maven-repo/org/apache/xmlgraphics/batik-all/*/* dpkg failed to execute successfully > apt-file search /usr/share/maven-repo/org/apache/xmlgraphics/batik-all apt-file failed to execute successfully > dpkg --search /usr/share/java/batik-all.jar Found libbatik-java [error] Package libbatik-java does not contain Maven dependency org.apache.xmlgraphics:batik-all:jar:${batik.version} but there seem to be a match If the package contains already Maven artifacts but the names don't match, try to enter a substitution rule of the form s/groupId/newGroupId/ s/artifactId/newArtifactId/ jar s/version/newVersion/ here: > s/xmlgraphics/xmlgraphics/ s/batik-all/batik/ jar s/8.4/8.4/ Please suggest the maintainer of package libbatik-java to add this rule to debian/maven.publishedRules > dpkg --search /usr/share/maven-repo/org/apache/xmlgraphics/batik-all/*/* dpkg failed to execute successfully > apt-file search /usr/share/maven-repo/org/apache/xmlgraphics/batik-all apt-file failed to execute successfully [error] Package libbatik-java does not contain Maven dependency org.apache.xmlgraphics:batik-all:jar:${batik.version} but there seem to be a match If the package contains already Maven artifacts but the names don't match, try to enter a substitution rule of the form s/groupId/newGroupId/ s/artifactId/newArtifactId/ jar s/version/newVersion/ here: 3. > dpkg --search /usr/share/maven-repo/net/sf/saxon/saxon/*/* dpkg failed to execute successfully > apt-file search /usr/share/maven-repo/net/sf/saxon/saxon apt-file failed to execute successfully > dpkg --search /usr/share/java/saxon.jar Found libsaxon-java [error] Package libsaxon-java does not contain Maven dependency net.sf.saxon:saxon:jar:8.7 but there seem to be a match If the package contains already Maven artifacts but the names don't match, try to enter a substitution rule of the form s/groupId/newGroupId/ s/artifactId/newArtifactId/ jar s/version/newVersion/ here: > s/saxon/saxon/ s/saxon/saxon/ jar s/8.7/6.5.5/ Please suggest the maintainer of package libsaxon-java to add this rule to debian/maven.publishedRules > dpkg --search /usr/share/maven-repo/net/sf/saxon/saxon/*/* dpkg failed to execute successfully > apt-file search /usr/share/maven-repo/net/sf/saxon/saxon apt-file failed to execute successfully [error] Package libsaxon-java does not contain Maven dependency net.sf.saxon:saxon:jar:8.7 but there seem to be a match If the package contains already Maven artifacts but the names don't match, try to enter a substitution rule of the form s/groupId/newGroupId/ s/artifactId/newArtifactId/ jar s/version/newVersion/ here: Thanks