alexarchambault on gh-pages
Update website (compare)
tgodzik on main
Fix reflection deprecation Don't forget to create instance… Merge pull request #2684 from e… (compare)
My company has a proxy repository which all artifact access is fronted by.
As such in sbt, we use the configuration details mentioned here: https://www.scala-sbt.org/1.x/docs/Proxy-Repositories.html#sbt+Configuration in order to configure sbt to correctly resolve artifacts.
The docs referenced speak to a block like this:
[repositories]
local
my-ivy-proxy-releases: http://repo.company.com/ivy-releases/, [organization]/[module]/(scala_[scalaVersion]/)(sbt_[sbtVersion]/)[revision]/[type]s/[artifact](-[classifier]).[ext]
my-maven-proxy-releases: http://repo.company.com/maven-releases/
This works great for sbt, but I am trying to accomplish the same in the coursier CLI (as well as in mill, which I know is outside the scope of this repo).
What would be the raw coursier configuration way to accomplish what sbt does? I'm interested both in how to do this with config files, i.e. using coursier.mirrors, using environment variables and finally using command line options.
What's of particular note is how to configure the ivy pattern in coursier as shown in sbt.
Hey folks, I'm trying to download a binary executable from :
https://repo1.maven.org/maven2/io/grpc/protoc-gen-grpc-java/1.47.0/
unfortunately, the binaries are not listed in the pom file, so setting types/classifiers in coursier dependencies is not helping. Does coursier allow for downloading a file without it being referenced in the pom ?
DependencyTree
there is a reconciledVersion
and a retainedVersion
. Anyone know the difference?
Alright so the above just bit me. Looking at the scaladocs I see
/** The final version of this dependency. */
def retainedVersion: String
which made me think I'd want that if ultimately I wanted the actual retained version, but in cases where a version range is used in Java, this still spits out the range whereas reconciled doesn't. For example
version: [2.8.6,2.9)
retrained: [2.8.6,2.9)
reconciled: 2.8.9
DEVELOP.md
This message is replying to a Matrix event but we were unable to find associated bridged Gitter message to put it in the appropriate threaded conversation.
I get past this one.
17:44:11 θ60° lefou:~/work/opensource/coursier master+* 1 ± mill core.jvm[2.13.6].compile
[7/65] core.jvm[2.13.6].publishVersion
[42/65] util.jvm[2.13.6].compile
Compiling project (Scala 2.13.6, JVM)
Warning: 2 feature warnings; re-run with -feature for details
java.nio.file.ClosedFileSystemException
Error compiling project (Scala 2.13.6, JVM)
at jdk.zipfs/jdk.nio.zipfs.ZipFileSystem.ensureOpen(ZipFileSystem.java:1619)
at jdk.zipfs/jdk.nio.zipfs.ZipFileSystem.getFileAttributes(ZipFileSystem.java:531)
at jdk.zipfs/jdk.nio.zipfs.ZipPath.readAttributes(ZipPath.java:767)
at jdk.zipfs/jdk.nio.zipfs.ZipPath.readAttributes(ZipPath.java:777)
at jdk.zipfs/jdk.nio.zipfs.ZipFileSystemProvider.readAttributes(ZipFileSystemProvider.java:276)
at java.base/java.nio.file.Files.readAttributes(Files.java:1851)
at java.base/java.nio.file.Files.size(Files.java:2468)
at sbt.internal.inc.HashUtil$.farmHash(HashUtil.scala:31)
at sbt.internal.inc.FarmHash$.ofPath(Stamp.scala:89)
Can someone explain this?
❯ cs resolve com.zaxxer:HikariCP:4.0.0
https://repo1.maven.org/maven2/com/zaxxer/HikariCP/4.0.0/HikariCP-4.0.0.pom
100.0% [##########] 25.3 KiB (316.4 KiB / s)
com.zaxxer:HikariCP:4.0.0:default
org.slf4j:slf4j-api:2.0.0-alpha1:default
But https://repo1.maven.org/maven2/com/zaxxer/HikariCP/4.0.1/HikariCP-4.0.1.pom doesn't show 2.0.0-alpha1. It uses a property syntax:
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
<version>${slf4j.version}</version>
</dependency>
slf4j.version
in the pom https://repo1.maven.org/maven2/com/zaxxer/HikariCP/4.0.0/HikariCP-4.0.0.pom it is 2.0.0-alpha1
. So resolver here is showing you the fully resolved deps
${slf4j.version}
in different profiles, which get auto-enabled depending on the executing Java version. Probably not the best idea, but within the Maven POM specs.
cs install ammonite
, it installs the latest version but by default it install the scala 2.13 version.
Hi folks, is it possible to complete snapshots dependencies? e.g.
$ cs complete-dep -r sonatype:snapshots org.scalameta:metals_2.13:0.11.8
0.11.8
At the moment it only seems to resolve releases.
Or do you recommend another way of finding out the latest snapshot version of a dependency from the terminal?
nvim-metals
as latest.snapshot
and it will pull it for you
I want to know how to use 'cs launch' with Gradle.
Essentially, you don't
what i really want to do is swap out the scala compiler in gradle's build process with 'cs launch scalac:2.xxx' or 'cs launch scalac:3.xxx' because that's what my company provides
I guess this is the part the confuses me with your use case. cs launch will have nothing to do with gradle. At the point that you're using launch, gradle is no longer in the picture
Dependency
without access to MinimizedExclusions
in coursier 2.1.0-M7?
coursier
package