[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [lyo-dev] Problems with OSLC4J 2.2.1
|
Hi Samit,
Below is the full list of dependencies needed for a minimal client usage including single logging library:
<dependency>
<!--avoid ClassNotFoundException: org.w3c.dom.ElementTraversal-->
<groupId>xml-apis</groupId>
<artifactId>xml-apis</artifactId>
<version>1.4.01</version>
</dependency>
<dependency>
<groupId>org.eclipse.lyo.clients</groupId>
<artifactId>oslc-java-client</artifactId>
<version>2.1.2-SNAPSHOT</version>
<exclusions>
<exclusion>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
</exclusion>
<exclusion>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-log4j12</artifactId>
</exclusion>
<exclusion>
<groupId>org.slf4j</groupId>
<artifactId>jcl-over-slf4j</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
<version>1.7.21</version>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-simple</artifactId>
<version>1.7.21</version>
<scope>runtime</scope>
</dependency>
You can set the logging level to TRACE by creating src/main/resources/simplelogger.properties file with the following contents:
org.slf4j.simpleLogger.defaultLogLevel=trace
If you don’t mind the warnings (reported in https://bugs.eclipse.org/bugs/show_bug.cgi?id=513477), you can simply use:
<dependency>
<!--avoid ClassNotFoundException: org.w3c.dom.ElementTraversal-->
<groupId>xml-apis</groupId>
<artifactId>xml-apis</artifactId>
<version>1.4.01</version>
</dependency>
<dependency>
<groupId>org.eclipse.lyo.clients</groupId>
<artifactId>oslc-java-client</artifactId>
<version>2.1.2-SNAPSHOT</version>
</dependency>
-Andrew.
On 03.02.17, 17:22, lyo-dev-bounces@xxxxxxxxxxx im Auftrag von Samit Mehta <lyo-dev-bounces@xxxxxxxxxxx im Auftrag von samit.mehta@xxxxxxxxxx> wrote:
Jim,
The improvements described should help with the consumption. You may already be planning this, but wanted to confirm:
Will there be an easy way to consume the packages that are needed to develop an OSLC client (I believe we only support a Java client) versus develop an OSLC server (or server/client)?
I am only going off of memory since I haven't built/consumed OSLC4J in a while, but I seem to remember having to download/build all the OSLC4J packages since that was easier than trying to figure individual packages that are needed to support a client versus server.
Sincerely,
___________________________________________________________________________
Samit Mehta
IBM, Watson IoT Alliances and Ecosystem
mailto:samit.mehta@xxxxxxxxxx