You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myriad.apache.org by Paul Read <pd...@gmail.com> on 2015/03/30 12:56:18 UTC

log4j and executor?

Is there an underlying reason why log4j.properties or log4j.xml was not
included in the executor runtime configuration? Or was this an oversight?

Re: log4j and executor?

Posted by Adam Bordelon <ad...@mesosphere.io>.
Thanks. Feel free to create a Pull Request for your fix.

On Mon, Apr 6, 2015 at 2:38 PM, Paul Read <pd...@gmail.com> wrote:

> What I did to make it work was added log4j.xml to the build.gradle so it
> was added to the executor jar but not the myriad.x.x.x.jar file. Seems to
> work.
>
>
>
> On Mon, Apr 6, 2015 at 9:46 AM, Ken Sipe <ke...@mesosphere.io> wrote:
>
>> sorry guys… I was on vacation…    let me check on this…
>>
>> Ken
>> > On Mar 30, 2015, at 11:33 AM, Adam Bordelon <ad...@mesosphere.io> wrote:
>> >
>> > I don't think this was intentional. Could be a side effect of the new
>> gradle build? @kensipe?
>> >
>> > On Mon, Mar 30, 2015 at 3:56 AM, Paul Read <pdread101@gmail.com
>> <ma...@gmail.com>> wrote:
>> > Is there an underlying reason why log4j.properties or log4j.xml was not
>> > included in the executor runtime configuration? Or was this an
>> oversight?
>> >
>>
>>
>

Re: log4j and executor?

Posted by Paul Read <pd...@gmail.com>.
What I did to make it work was added log4j.xml to the build.gradle so it
was added to the executor jar but not the myriad.x.x.x.jar file. Seems to
work.



On Mon, Apr 6, 2015 at 9:46 AM, Ken Sipe <ke...@mesosphere.io> wrote:

> sorry guys… I was on vacation…    let me check on this…
>
> Ken
> > On Mar 30, 2015, at 11:33 AM, Adam Bordelon <ad...@mesosphere.io> wrote:
> >
> > I don't think this was intentional. Could be a side effect of the new
> gradle build? @kensipe?
> >
> > On Mon, Mar 30, 2015 at 3:56 AM, Paul Read <pdread101@gmail.com <mailto:
> pdread101@gmail.com>> wrote:
> > Is there an underlying reason why log4j.properties or log4j.xml was not
> > included in the executor runtime configuration? Or was this an oversight?
> >
>
>

Re: log4j and executor?

Posted by Ken Sipe <ke...@mesosphere.io>.
sorry guys… I was on vacation…    let me check on this… 

Ken
> On Mar 30, 2015, at 11:33 AM, Adam Bordelon <ad...@mesosphere.io> wrote:
> 
> I don't think this was intentional. Could be a side effect of the new gradle build? @kensipe?
> 
> On Mon, Mar 30, 2015 at 3:56 AM, Paul Read <pdread101@gmail.com <ma...@gmail.com>> wrote:
> Is there an underlying reason why log4j.properties or log4j.xml was not
> included in the executor runtime configuration? Or was this an oversight?
> 


Re: log4j and executor?

Posted by Adam Bordelon <ad...@mesosphere.io>.
I don't think this was intentional. Could be a side effect of the new
gradle build? @kensipe?

On Mon, Mar 30, 2015 at 3:56 AM, Paul Read <pd...@gmail.com> wrote:

> Is there an underlying reason why log4j.properties or log4j.xml was not
> included in the executor runtime configuration? Or was this an oversight?
>