Bug#853733: Make scala depend on a specific jline version

Frederic Bonnard frediz at linux.vnet.ibm.com
Tue Jan 31 12:42:51 UTC 2017


Source: scala
Source-Version: 2.11.8-1

--

Hi,
scala binary package depends on libjline2-java but .pom files do not reflect this.
So when one installs scala, the pom file shows : 

$ tail /usr/share/maven-repo/org/scala-lang/scala-compiler/2.11.*/scala-compiler-2.11.*.pom 
==> /usr/share/maven-repo/org/scala-lang/scala-compiler/2.11.8/scala-compiler-2.11.8.pom <==
    </dependency>
    <dependency>
      <!-- for scala-compiler-repl; once it moves there, make it required -->
      <groupId>jline</groupId>
      <artifactId>jline</artifactId>
      <version>debian</version>
      <optional>true</optional>
    </dependency>
  </dependencies>
</project>
==> /usr/share/maven-repo/org/scala-lang/scala-compiler/2.11.x/scala-compiler-2.11.x.pom <==
    </dependency>
    <dependency>
      <!-- for scala-compiler-repl; once it moves there, make it required -->
      <groupId>jline</groupId>
      <artifactId>jline</artifactId>
      <version>debian</version>
      <optional>true</optional>
    </dependency>
  </dependencies>

And neither libjline-java nor libjline2-java define a debian version.
So when I try to package some scala related app, it tries to find jline and it breaks :

== resolving dependencies org.scala-lang#scala-compiler;2.11.x->jline#jline;debian [optional->master(*)]
loadData of jline#jline;debian of rootConf=default
        using redefined-public to resolve jline#jline;debian
redefined-public: Checking cache for: dependency: jline#jline;debian {optional=[compile(*), master(*)]}
        no ivy file in cache for jline#jline;debian: tried /home/debian/.ivy2/cache/jline/jline/ivy-debian.xml
debian-local-maven: no namespace defined: using system
        no ivy file in cache for jline#jline;debian: tried /home/debian/.ivy2/cache/jline/jline/ivy-debian.xml
         trying file:/usr/share/maven-repo/jline/jline/debian/jline-debian.pom
                tried file:/usr/share/maven-repo/jline/jline/debian/jline-debian.pom
        debian-local-maven: resource not reachable for jline#jline;debian: res=file:/usr/share/maven-repo/jline/jline/debian/jline-debian.pom
         trying file:/usr/share/maven-repo/jline/jline/debian/jline-debian.jar
                tried file:/usr/share/maven-repo/jline/jline/debian/jline-debian.jar
        debian-local-maven: resource not reachable for jline#jline;debian: res=file:/usr/share/maven-repo/jline/jline/debian/jline-debian.jar
        debian-local-maven: no ivy file nor artifact found for jline#jline;debian
WARN:   module not found: jline#jline;debian
WARN: ==== debian-local-maven: tried
WARN:   file:/usr/share/maven-repo/jline/jline/debian/jline-debian.pom
WARN:   -- artifact jline#jline;debian!jline.jar:
WARN:   file:/usr/share/maven-repo/jline/jline/debian/jline-debian.jar

Manually changing "<version>debian</version>" to "<version>2.x</version>" does the job.
Would it be correct ?

Thanks,

F.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20170131/98f1e59c/attachment.sig>


More information about the pkg-java-maintainers mailing list