I may not have answered your question exactly. I've described how its
supposed to work.
Is the client-distribution failing to build, or are you just unable to use
it out-of-the-box because of a lack of slf4j provider?
On 06/07/07, Rupert Smith <[EMAIL PROTECTED]> wrote:
The client only depends on the API part of slf4j. To use it, you have to
provide the slf4j implementation part that you want to use.
For example, the client tests depend on slf4j-log4j:
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-log4j12</artifactId>
<version>1.4.0</version>
<scope>test</scope>
</dependency>
However, we don't want to make the client itself depend on log4j, or else
that forces everyone who uses it to use log4j, which is the entire point of
using slf4j.
So if you have a project (MyProject), that wants to use the java client,
use the following dependencies:
MyProject depends on:
-> Qpid Java Client
-> slf4j implementation (e.g. slf4j-log4j12)
Rupert
On 06/07/07, Jonathan Robie <[EMAIL PROTECTED]> wrote:
>
> Is there supposed to be a client-only distribution of the Java AMQP
> implementation?
>
> Maven is set up to build one. When I do, it doesn't work because it has
> only the API files for slf4j. Here are the slf4j files in the full
> distribution:
>
> [EMAIL PROTECTED] lib]$ pwd
> /home/jrobie/project/qpid/java/distribution/target/qpid-
> 1.0-incubating-M2-SNAPSHOT-java-bin/qpid-1.0-incubating-M2-SNAPSHOT/lib
> [EMAIL PROTECTED] lib]$ ls slf4j*
> slf4j-api-1.4.0.jar slf4j-jdk14-1.4.0.jar slf4j-nop-1.4.0.jar
> slf4j-jcl-1.4.0.jar slf4j-log4j12-1.4.0.jar slf4j-simple-1.4.0.jar
> [EMAIL PROTECTED] lib]$
>
>
> Here are the slf4j files in the client distribution:
>
> [EMAIL PROTECTED] lib]$ pwd
> /home/jrobie/project/qpid/java/client/distribution/target/qpid-
> 1.0-incubating-M2-SNAPSHOT-java-client-bin/qpid-
> 1.0-incubating-M2-SNAPSHOT/lib
> [EMAIL PROTECTED] lib]$ ls slf4j*
> slf4j-api-1.4.0.jar
>
> Both distributions are newly built.
>
> Jonathan
>
>
>
