Details
-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
None
-
None
-
1
Description
Scala libraries are often cross-compiled for multiple Scala language versions, so you end up with foo_2.11, foo_2.12 etc. jars.
Maven doesn't have great support for this. The solution we use currently uses "${scala.compat.version}" in the artifactId, together with profiles, which does work - but produces a lot of warnings of the "this will not work in the future" variety.
Also, thanhbv has reported on SCBC-206 that there are other issues with the profile approach, namely that some dependencies get included twice in the final pom.xml with two different version numbers.
This blanket ticket will aim to resolve these two, and generally clean up the Maven build for Scala as much as possible.