XML and JSON layouts and listeners are all Jackson-based and in svn.

Gary

<div>-------- Original message --------</div><div>From: Matt Sicker 
<boa...@gmail.com> </div><div>Date:05/14/2014  21:53  (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>So what about generating or receiving XML log events? Gary said something 
about using Jackson for that, but I'm not sure on the specifics. It sounded 
like something like an optional plugin based on the presence of Jackson. 
Considering we use Jackson for JSON/YAML configuration formats, it would make 
sense to keep anything depending on it in log4j-core.


On 14 May 2014 13:16, Ralph Goers <ralph.go...@dslextreme.com> wrote:
I would hope it would only be required for XMLLayout, JSONLayout and 
JSONConfiguration + any receivers you created.  Log4j with only XML 
configuration shouldn’t require Jackson. If it does it should be addressed.

Ralph

On May 14, 2014, at 9:09 AM, Gary Gregory <garydgreg...@gmail.com> wrote:

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


-------- Original message --------
From: Mikael Ståldal
Date:05/14/2014 07:37 (GMT-05:00)
To: Log4J Developers List
Subject: Re: Dependency to javax.persistence

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




-- 
Matt Sicker <boa...@gmail.com>

Reply via email to