Well, sure for JPA you need the API and a provider. What I am curious about is
if we can start log4j without Jackson...
Gary
<div>-------- Original message --------</div><div>From: Mikael Ståldal
<mikael.stal...@appearnetworks.com> </div><div>Date:05/14/2014 07:37
(GMT-05:00) </div><div>To: Log4J Developers List <log4j-dev@logging.apache.org>
</div><div>Subject: Re: Dependency to javax.persistence </div><div>
</div>I guess that a standalone app will not work with javax.persistence API
only, it needs an implementation of it as well. And that implementation will
most likely bring in the API as well.
The JMS API dependecy is already declared as provided, from log4j-core/pom.xml:
<!-- Used for JMS appenders (needs an implementation of course) -->
<dependency>
<groupId>org.jboss.spec.javax.jms</groupId>
<artifactId>jboss-jms-api_1.1_spec</artifactId>
<scope>provided</scope>
</dependency>
<!-- Used for JPA appenders (needs an implementation of course) -->
<dependency>
<groupId>org.eclipse.persistence</groupId>
<artifactId>javax.persistence</artifactId>
<scope>compile</scope>
<optional>true</optional>
</dependency>
On Wed, May 14, 2014 at 12:48 PM, Gary Gregory <garydgreg...@gmail.com> wrote:
Why? How would that bring in the right jar in a standalone app? Are you
assuming the app lives in a container like a J2EE server?
Gary
-------- Original message --------
From: Mikael Ståldal
Date:05/14/2014 04:01 (GMT-05:00)
To: log4j-dev@logging.apache.org
Subject: Dependency to javax.persistence
Can't the dependency to javax.persistence be declared as provided?
--
Mikael Ståldal
Chief Software Architect
Appear
Phone: +46 8 545 91 572
Email: mikael.stal...@appearnetworks.com
--
Mikael Ståldal
Chief Software Architect
Appear
Phone: +46 8 545 91 572
Email: mikael.stal...@appearnetworks.com
