Re: Wrong home for log4j-server stuff

I like log4j-samples better than log4j-server for the same reasons that Mikael and Ralph mentioned. True, it has already been released, but the module breakup gives us a chance to clarify our intentions. (Shameless plug) Every java main() method deserves http://picocli.info > On May 31, 2017,

Re: Wrong home for log4j-server stuff

The point is that the server isn’t really very useful by itself. The intent was for you to copy it and add whatever logic you want to it. That is what makes it a sample. Ralph > On May 30, 2017, at 12:10 PM, Gary Gregory wrote: > > On Tue, May 30, 2017 at 10:37 AM, Ralph Goers

Re: Wrong home for log4j-server stuff

On Tue, May 30, 2017 at 12:37 PM, Mikael Ståldal wrote: > Sounds good. I like to declare it as sample, since it is not really > production ready on the level of quality and security I would like us to > maintain the core of Log4j. If we want to declare it as production ready, I > think we have so

Re: Wrong home for log4j-server stuff

Sounds good. I like to declare it as sample, since it is not really production ready on the level of quality and security I would like us to maintain the core of Log4j. If we want to declare it as production ready, I think we have some work to do to improve it. We recently had to make a securi

Re: Wrong home for log4j-server stuff

On Tue, May 30, 2017 at 10:37 AM, Ralph Goers wrote: > I plan on moving the log4j-samples module to a separate repo anyway. I see > no reason why the server can’t go into that repo. > > > On May 30, 2017, at 10:33 AM, Matt Sicker wrote: > > > > Making a new repo isn't a big deal. Once we figure

Re: Wrong home for log4j-server stuff

I plan on moving the log4j-samples module to a separate repo anyway. I see no reason why the server can’t go into that repo. > On May 30, 2017, at 10:33 AM, Matt Sicker wrote: > > Making a new repo isn't a big deal. Once we figure out a nice way to build > two separate repos, that can easily ex

Re: Wrong home for log4j-server stuff

Making a new repo isn't a big deal. Once we figure out a nice way to build two separate repos, that can easily extend to N separate repos, right? ;) On 30 May 2017 at 11:26, Mikael Ståldal wrote: > I put it in log4j-tools since it Ralph didn't wanted it in the main repo, > and there was not othe

Re: Wrong home for log4j-server stuff

I put it in log4j-tools since it Ralph didn't wanted it in the main repo, and there was not other existing repo which fitted better. I don't mind moving it to the main repo, or to some other new repo (if we find it worth the effort to create and setup yet another repo, I am skeptic). I would o

Re: Wrong home for log4j-server stuff

I agree it doesn’t belong in the tools repo. It really belongs in a log4j-examples or log4j-samples as that is all it was meant to be. Ralph > On May 29, 2017, at 2:06 PM, Gary Gregory wrote: > > I find that the Git repo logging-log4j-tools is the wrong home for > log4-server. This is not a to

Wrong home for log4j-server stuff

I find that the Git repo logging-log4j-tools is the wrong home for log4-server. This is not a tool. It's a runtime component. I do not see why it cannot live in main repo. I use tools at development time. YMMV. Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with H