Snowplow-scala-tracker library URL


#1

The below call doesn’t work, because presumably the URL is incorrect. Can someone please share me the correct URL?

wget http://maven.snplow.com/releases/com/snowplowanalytics/snowplow-scala-tracker/0.2.0/snowplow-scala-tracker-0.2.0.jar

If someone knows of a method to just list all valid (w.r.t. the local environment) gradle library strings that would also be great.

I tried
compile 'com.snowplowanalytics:snowplow-scala-tracker:0.2.0'

, which I believe to be correct, but it wouldn’t resolve.


#2

Hello @0xABAB.

Scala tracker is compiled against Scala 2.10, so you can use following URL:

http://maven.snplow.com/releases/com/snowplowanalytics/snowplow-scala-tracker_2.10/0.2.0/snowplow-scala-tracker_2.10-0.2.0.jar

SBT implicitly adds Scala version with %% resolution operator, but using Gradle and Maven you should give full artifactId explicitly.

And you can use 2.11 as well.

Cheers,
Anton


#3

I got the snowplow tracker library via git, ran sbt publishLocal with exit status 0, but

then adding

compile 'com.snowplowanalytics:snowplow-scala-tracker_2.11:0.3.0-M1'

to my configuration doesn’t work. (I.e. it does not resolve my local repository in Gradle. )

# output of : find .ivy2 -wholename '*snowplow-scala-tracker_2.1*/0.3.0-M1*' # in home dir
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.10/0.3.0-M1
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.10/0.3.0-M1/docs
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.10/0.3.0-M1/docs/snowplow-scala-tracker_2.10-javadoc.jar
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.10/0.3.0-M1/docs/snowplow-scala-tracker_2.10-javadoc.jar.md5
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.10/0.3.0-M1/docs/snowplow-scala-tracker_2.10-javadoc.jar.sha1
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.10/0.3.0-M1/ivys
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.10/0.3.0-M1/ivys/ivy.xml
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.10/0.3.0-M1/ivys/ivy.xml.md5
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.10/0.3.0-M1/ivys/ivy.xml.sha1
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.10/0.3.0-M1/jars
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.10/0.3.0-M1/jars/snowplow-scala-tracker_2.10.jar
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.10/0.3.0-M1/jars/snowplow-scala-tracker_2.10.jar.md5
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.10/0.3.0-M1/jars/snowplow-scala-tracker_2.10.jar.sha1
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.10/0.3.0-M1/poms
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.10/0.3.0-M1/poms/snowplow-scala-tracker_2.10.pom
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.10/0.3.0-M1/poms/snowplow-scala-tracker_2.10.pom.md5
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.10/0.3.0-M1/poms/snowplow-scala-tracker_2.10.pom.sha1
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.10/0.3.0-M1/srcs
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.10/0.3.0-M1/srcs/snowplow-scala-tracker_2.10-sources.jar
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.10/0.3.0-M1/srcs/snowplow-scala-tracker_2.10-sources.jar.md5
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.10/0.3.0-M1/srcs/snowplow-scala-tracker_2.10-sources.jar.sha1
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.11/0.3.0-M1
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.11/0.3.0-M1/docs
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.11/0.3.0-M1/docs/snowplow-scala-tracker_2.11-javadoc.jar
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.11/0.3.0-M1/docs/snowplow-scala-tracker_2.11-javadoc.jar.md5
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.11/0.3.0-M1/docs/snowplow-scala-tracker_2.11-javadoc.jar.sha1
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.11/0.3.0-M1/ivys
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.11/0.3.0-M1/ivys/ivy.xml
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.11/0.3.0-M1/ivys/ivy.xml.md5
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.11/0.3.0-M1/ivys/ivy.xml.sha1
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.11/0.3.0-M1/jars
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.11/0.3.0-M1/jars/snowplow-scala-tracker_2.11.jar
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.11/0.3.0-M1/jars/snowplow-scala-tracker_2.11.jar.md5
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.11/0.3.0-M1/jars/snowplow-scala-tracker_2.11.jar.sha1
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.11/0.3.0-M1/poms
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.11/0.3.0-M1/poms/snowplow-scala-tracker_2.11.pom
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.11/0.3.0-M1/poms/snowplow-scala-tracker_2.11.pom.md5
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.11/0.3.0-M1/poms/snowplow-scala-tracker_2.11.pom.sha1
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.11/0.3.0-M1/srcs
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.11/0.3.0-M1/srcs/snowplow-scala-tracker_2.11-sources.jar
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.11/0.3.0-M1/srcs/snowplow-scala-tracker_2.11-sources.jar.md5
.ivy2/local/com.snowplowanalytics/snowplow-scala-tracker_2.11/0.3.0-M1/srcs/snowplow-scala-tracker_2.11-sources.jar.sha1

#4

@0xABAB can your Gradle configuration handle any other locally published artifacts? This workflow works fine from SBT, but I have no experience with Gradle.


#5

Hey @0xABAB, I’d do it like this for now;

repositories {
    mavenCentral()
    maven { url "http://dl.bintray.com/snowplow/snowplow-maven" }
    maven { url "http://maven.snplow.com/releases" }
}

dependencies {
    compile 'org.scala-lang:scala-library:2.11.5'
    compile 'com.snowplowanalytics:snowplow-scala-tracker_2.11:0.3.0-M1' 
}

The final release will be in jcenter/mavencentral, but this should let you work with the current pre-release.


#6

Thanks, I got this part to work now.

I don’t know why it works now, though, but that’s not really of much interest. I suspect gradle has some deficiencies/bugs that I don’t want to know about. I will eliminate the gradle dependency once the application of interest fully works (I wanted to do that earlier, but was not able to reproduce the build easily before).