You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Very nice plugin! However, I was wondering, given that the plugin is following the GAV format, shouldn't JARs and POMs both have Scala and SBT versions included in the name? What I mean is:
Oh, sorry, maybe I didn't explain it properly. What I meant is that I think that the full artifactId should be included in the filenames - for artifactId 'sbt-pack_2.12_1.0' files should be 'sbt-pack_2.12_1.0-0.11.jar' (same for pom). The example I gave with akka doesn't include the sbt version for some reason but includes the full artifactId in the filename.
Hello,
Very nice plugin! However, I was wondering, given that the plugin is following the GAV format, shouldn't JARs and POMs both have Scala and SBT versions included in the name? What I mean is:
For the below GAV
GroupId: org.xerial.sbt
ArtifactId: sbt-pack_2.12_1.0
Version: 0.11
Shouldn't the path be /org/xerial/sbt/sbt-pack_2.12_1.0/sbt-pack_2.12_1.0-0.11.jar
Instead of /org/xerial/sbt/sbt-pack_2.12_1.0/sbt-pack-0.11.jar
I was looking at some other libraries as examples and they seem to include scala/sbt versions in the jar/pom. E.g the akka-actor library:
http://central.maven.org/maven2/com/typesafe/akka/akka-actor_2.12/2.5.17/
I might be wrong but I think a Nexus mirror with only Maven dependency resolution might not be able to resolve the plugin.
Thanks
The text was updated successfully, but these errors were encountered: