I excluded the dependencies from quartz in the fulcrum-quarz pom like this:
<dependency>
<groupId>org.quartz-scheduler</groupId>
<artifactId>quartz</artifactId>
<version>1.8.3</version>
<exclusions>
<exclusion>
<groupId>javax.transaction</groupId>
<artifactId>jta</artifactId>
</exclusion>
<exclusion>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
</exclusion>
<exclusion>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-log4j12</artifactId>
</exclusion>
</exclusions>
</dependency>
ran mvn clean test, all tests failed.
Does not seem like an option?
/Ludwig
-----Ursprungligt meddelande-----
From: Thomas Vandahl
Sent: Thursday, September 22, 2011 7:06 PM
To: Turbine Developers List
Subject: Re: [fulcrum] [VOTE] Release fulcrum-quartz-1.1.0 based on RC1
Hi Siegfried,
On 20.09.11 22:14, Siegfried Göschl wrote:
one question - the quartz library pulls in javax.transaction, c3p0 and
slf4j since this is defined in its pom. Do we really want those dependency
propagated or shall we exclude them directly for this project?
Well, I'm not able to tell whether they are needed or not. If the
dependencies are not required, the should have been made optional in the
first place. Can we define them as optional for fulcrum-quartz and
override the quartz-POM?
I have a bad feeling about excluding dependencies that might shoot users
in the foot.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
