I have just been told that a couple of our presentations were miss-marked.
Please stand by... :-)
Nick
Sent from my iPhone, so please forgive brief replies and frequent typos
> On Feb 18, 2014, at 7:38, Nicholas Williams
> wrote:
>
> Unfortunately, they have wait-listed ALL
Unfortunately, they have wait-listed ALL FOUR of our presentations. It's rather
maddening how they kept emailing us saying "your project isn't represented" and
"not enough people have submitted CFPs," and now they decided that our project
won't be represented.
Nick
Sent from my iPhone, so ple
Apparently I don't have karma to commit anything on dist, because I can't
commit my keys OR the rc1 release artifacts. I'm told it's forbidden. Can y'all
provide me (even temporary) karma to do that? Or does Infra have to get
involved?
Nick
Sent from my iPhone, so please forgive brief replies
I think it's very clearly a yes. The legal page says code with the MIT license
can be included in ASF projects.
However, I have a suggestion for the next release that will make this whole
discussion moot: let's use the CDN instead of including the JQuery source code
in source control. That way
Agreed.
Nick
Sent from my iPhone, so please forgive brief replies and frequent typos
> On Feb 8, 2014, at 9:05, Remko Popma wrote:
>
> Fine with me also.
> Remko
>
>> On Saturday, February 8, 2014, Gary Gregory wrote:
>> Fine with me.
>>
>> Gary
>>
>>
>> Original message --
void diag(String message);
> // optional other methods
> }
>
> That way, this interface exists at compile time.
>
>> On Monday, January 27, 2014, Nicholas Williams
>> wrote:
>> Scott, invokedynamic and javassist...those are all /runtime/ things.
Scott, invokedynamic and javassist...those are all /runtime/ things. The user
needs Logger#notice to be available at compile time. Those are not compatible.
Nick
Sent from my iPhone, so please forgive brief replies and frequent typos
> On Jan 26, 2014, at 22:37, Scott Deboy wrote:
>
> Yes, I
Ralph, if you're getting compile errors with that code, A) there's a
copy-paste/transposition error, or B) there's something wrong with your
(non-standard?) compiler. Given:
abstract class A { ... }
This is perfectly legal in Java 5+:
A a = new A() { };
That's an anonymous inner class extendi
easy
> to handle as in those cases the custom levels need to be converted to a
> StdLevel and then that enum is used.
>
> Unless anyone objects I plan on committing this later today once I finish it
> and create some tests and documentation.
>
> Ralph
>
>
>
>>
No, of course, everyone seems to agree that custom levels should be permitted.
But I never heard agreement on whether we were going the extensible enum route
or the Level-as-interface route. The camp still seemed to disagree on that.
Nick
Sent from my iPhone, so please forgive brief replies and
I prefer to avoid markers whenever possible. Unlike levels, markers require
some amount of configuration to get them to log/not log when desired. They
don't "just work."
N
Sent from my iPhone from LAX baggage claim, so please forgive brief replies and
frequent typos
> On Jan 18, 2014, at 14:0
y
> to go for servlet 3.0.
>
>
>> On 18 January 2014 15:19, Ralph Goers wrote:
>> I was hoping to start the GA release sooner than that.
>>
>> If the servlet context initializer is disabled then the listener should
>> still be allowed.
>>
>> Ra
I explained in the email why CONFIG > INFO. Not sure I can explain it any
better. :-/
To repeat in case you didn't see it:
>> My reason for putting CONFIG between INFO and WARN is simple: I ALWAYS want
>> to see config-related messages when the application starts, but I don't
>> always want to
Yes. Next weekend I plan on adding a Servlet context parameter that allows the
user to disable starting Log4j automatically. That should allow us to keep
everything in one JAR while supporting both sides of the argument.
Nick
Sent from my iPhone, so please forgive brief replies and frequent ty
To be clear, here's how I see it (assuming we adopted all levels proposed):
FATAL > ERROR > WARN > CONFIG > INFO > VERBOSE > DEBUG > FINE > TRACE.
CONFIG would map to INFO for slf4j. VERBOSE and FINE would both map to DEBUG.
My motivation for FINE was similar to your motivation for VERBOSE: DEBU
Umm, guys? Nobody ever put the logo contest on the homepage. No wonder
we only have one submission so far!
I don't have access to do this that I know of. Someone needs to update it ASAP!
Nick
Sent from my iPhone, so please forgive brief replies and frequent typos
smime.p7s
Description: S/MIME
Emails have been very snappy for me. Perhaps your provider is marking some
as spam, or delaying some? Then again, you're using Yahoo! mail. I can't
encourage you enough to use someone else.
I will note: a lot of these messages used to be delivered to spam for me
(Gmail). So I created a filter "to:
If it helps, check out LOG4J2-291. I may be handling errors
incorrectly in the JDBC/JPA/NoSQL appenders. If an exception is thrown
within the *Manager write methods, should I just let that exception
propagate (wrapping it if it's a checked exception that I can't
throw)? Should I wrap all exceptions
Sounds good to me, for the most part. But perhaps a sooner date? I think it
would be nice if the new logo was in place by then. It seems (to me,
anyway) that we are very close to general availability.
Nick
Sent from my iPhone, so please forgive brief replies and frequent typos
On May 11, 2013, a
:-/ fair enough. But I would definitely like to put the rush on beta7,
like you said. Can someone figure out this bug and go ahead and commit
the change so that if the release is canceled for one reason or
another the bug will already be fixed?
Nick
Sent from my iPhone, so please forgive brief re
*so I should include the connection information in my
_DatabaseManagers' names...
Sent from my iPhone, so please forgive brief replies and frequent typos
On Apr 29, 2013, at 8:34, Nicholas Williams
wrote:
> Oh! That makes sense! So I should include the connection information
Oh! That makes sense! So I should include the connection information
in my FileManager's name so that a new one gets created if the
connection information changes. Right?
Nick
Sent from my iPhone, so please forgive brief replies and frequent typos
On Apr 29, 2013, at 8:30, Ralph Goers wrote:
>
s considerably more complicated.
>
> Ralph
>
>
>
>
> On Apr 25, 2013, at 9:25 AM, Nicholas Williams wrote:
>
>
> On Thu, Apr 25, 2013 at 11:17 AM, Nicholas Williams <
> nicho...@nicholaswilliams.net> wrote:
>
>>
>> On Thu, Apr 25, 2013 at 1
at 1:11 PM, Ralph Goers wrote:
> Rather than a JDBC appender I was hoping for a more generic appender that
> could use JPA or something else.
>
>
> On Apr 25, 2013, at 7:39 AM, Nicholas Williams wrote:
>
> > First, a quick question: do we anticipate the next version
On Thu, Apr 25, 2013 at 11:17 AM, Nicholas Williams <
nicho...@nicholaswilliams.net> wrote:
>
> On Thu, Apr 25, 2013 at 11:15 AM, Nicholas Williams <
> nicho...@nicholaswilliams.net> wrote:
>
>>
>> On Thu, Apr 25, 2013 at 11:06 AM, Gary Gregory wrote:
>>
On Thu, Apr 25, 2013 at 11:15 AM, Nicholas Williams <
nicho...@nicholaswilliams.net> wrote:
>
> On Thu, Apr 25, 2013 at 11:06 AM, Gary Gregory wrote:
>
>> I thought it included a vendor neutral NoSQL API in its stack someplace.
>>
>
> From what I can tell, it
ding a whole lot of useful information on
their website.
>
> Gary
>
> On Apr 25, 2013, at 11:47, Nicholas Williams <
> nicho...@nicholaswilliams.net> wrote:
>
>
> On Thu, Apr 25, 2013 at 10:43 AM, Gary Gregory wrote:
>
>> On Thu, Apr 25, 2013 at 11:37 AM, N
On Thu, Apr 25, 2013 at 10:43 AM, Gary Gregory wrote:
> On Thu, Apr 25, 2013 at 11:37 AM, Nicholas Williams <
> nicho...@nicholaswilliams.net> wrote:
>
>>
>> On Thu, Apr 25, 2013 at 10:01 AM, Remko Popma wrote:
>>
>>> I think this is the link Gary is
Sent from my iPhone
>
> On 2013/04/25, at 23:51, Gary Gregory wrote:
>
> On Thu, Apr 25, 2013 at 10:39 AM, Nicholas Williams <
> nicho...@nicholaswilliams.net> wrote:
>
>> First, a quick question: do we anticipate the next version to be beta6 or
>> rc1?
On Thu, Apr 25, 2013 at 9:51 AM, Gary Gregory wrote:
> On Thu, Apr 25, 2013 at 10:39 AM, Nicholas Williams <
> nicho...@nicholaswilliams.net> wrote:
>
>> First, a quick question: do we anticipate the next version to be beta6 or
>> rc1? Just curious.
>>
>
>
First, a quick question: do we anticipate the next version to be beta6 or
rc1? Just curious.
I'm currently working on cleaning up compiler warnings throughout the
project and should have that completed soon.
I want to go ahead and get the conversation started about database
appenders. I'd like to
31 matches
Mail list logo
