These are chat archives for sbt/sbt
A relaxed chat room about sbt (That interactive build tool). For getting help on sbt, we encourage people to document it on Stackoverflow or subscribing to Lightbend subscription.
(testOnly in Test) := (testOnly in Test).dependsOn((flywayMigrate in Test).dependsOn(flywayClean in Test)).inputTaskValue, #### [error] No valid parser available. [error] testOnly **.UserDaoSpec
No valid parser availableseems like one of those truly opaque SBT errors that tells me exactly what my problem is, and doesn't help me at all to know what that problem is
executeTasks in Test := ...
testOnlytask to have those dependencies
.evaluatedresult of the
Hi, I'm attempting to add the typesafe repository SSL certificate to the java truststore, but for some reason having trouble with SBT identifying them properly. My assumption was if I download the certificate using
openssl, and import the certificate chain it should be fine, but I'm still getting a verification error.
Anything I might be missing?
Im seeing, as an example:
[error] Server access Error: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target url=https://repo.typesafe.com/typesafe/ivy-releases/com.github.gseitz/sbt-release/scala_2.10/sbt_0.13/1.0.0/ivys/ivy.xml
Although when I look for the lightbend certificate, I see it there:
Owner: CN=repo.lightbend.com, OU=PositiveSSL Multi-Domain, OU=Domain Control Validated Issuer: CN=COMODO RSA Domain Validation Secure Server CA, O=COMODO CA Limited, L=Salford, ST=Greater Manchester, C=GB Serial number: 971da6e69f9f3fda0575059dd333b38f Valid from: Fri Apr 08 03:00:00 IDT 2016 until: Tue Nov 13 01:59:59 IST 2018 Certificate fingerprints: MD5: 74:40:4E:5E:87:F6:B4:13:E5:42:99:79:66:A8:64:28 SHA1: F5:33:21:AF:17:0A:79:5D:1A:35:34:7A:FF:30:E2:8F:A1:4B:54:9B SHA256: 47:3A:33:02:99:F9:D0:24:F1:B3:BA:3A:82:28:C0:62:B5:26:DF:7C:DB:81:6C:DA:AA:6E:29:8E:8B:18:8B:EB Signature algorithm name: SHA256withRSA Version: 3
sbt.override.build.reposan SBT opt? it seems to work as a JVM_OPT as well
Resolver.url("global-ivy", url("<local-repo-group>"))(Resolver.ivyStylePatterns)(note the
ivyStylePatternsusage) still calls that repository with a maven style path. Am I missing something obvious? Tested with 0.13.13 and 0.13.15...
~/.sbt/resolversfile, launcher script changes or command line args when I am seeing this
resolvers ++= Seq( Resolver.url("global-ivy", url("<local-repo-group>"))(Resolver.ivyStylePatterns), DefaultMavenRepository )
[warn] module not found: uk.gov.hmrc#sbt-git-stamp;5.3.0 [warn] ==== typesafe-ivy-releases: tried [warn] https://repo.typesafe.com/typesafe/ivy-releases/uk.gov.hmrc/sbt-git-stamp/5.3.0/ivys/ivy.xml [warn] ==== sbt-plugin-releases: tried [warn] https://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/uk.gov.hmrc/sbt-git-stamp/5.3.0/ivys/ivy.xml [warn] ==== local: tried [warn] /Users/brian/.ivy2/local/uk.gov.hmrc/sbt-git-stamp/5.3.0/ivys/ivy.xml [warn] ==== public: tried [warn] https://repo1.maven.org/maven2/uk/gov/hmrc/sbt-git-stamp/5.3.0/sbt-git-stamp-5.3.0.pom [warn] ==== global-ivy: tried [warn] https://<nexus3 server>/uk.gov.hmrc/sbt-git-stamp/5.3.0/ivys/ivy.xml [warn] ==== public: tried [warn] https://repo1.maven.org/maven2/uk/gov/hmrc/sbt-git-stamp/5.3.0/sbt-git-stamp-5.3.0.pom