Installation

The library will have to be added to the project's dependencies:

SBT

libraryDependencies += "org.talares" %% "talares" % "0.1.0"
libraryDependencies += "org.talares" %% "talares-java" % "0.1.0" // Only needed to make the Java API available

Maven

<dependency>
  <groupId>org.talares</groupId>
  <artifactId>talares_2.10</artifactId>
  <version>0.1.0</version>
</dependency>
<!-- Only needed to make the Java API available -->
<dependency>
  <groupId>org.talares</groupId>
  <artifactId>talares-java_2.10</artifactId>
  <version>0.1.0</version>
</dependency>

To make use of the latest development, snapshot releases are available (note that these releases should not be considered stable and should therefore mostly serve testing purposes):

SBT

resolvers +=  "Sonatype snapshots" at "https://oss.sonatype.org/content/repositories/snapshots/"

libraryDependencies += "org.talares" %% "talares" % "0.1.1-SNAPSHOT"
libraryDependencies += "org.talares" %% "talares-java" % "0.1.1-SNAPSHOT" // Only needed to make the Java API available

Maven

<dependency>
  <groupId>org.talares</groupId>
  <artifactId>talares_2.10</artifactId>
  <version>0.1.1-SNAPSHOT</version>
</dependency>
<!-- Only needed to make the Java API available -->
<dependency>
  <groupId>org.talares</groupId>
  <artifactId>talares-java_2.10</artifactId>
  <version>0.1.1-SNAPSHOT</version>
</dependency>

An application.conf file will have to be present and added to the class path. This is usually done by placing it in the project's resources folder. The key talares.webservicelocation needs to be added to this file and it's value set to the URL through which the OData webservice can be reached.

Example application.conf

  talares.webservicelocation="http://www.example.com/cd_webservice/odata.svc"