Re: [ALL] Auto generating README.md and CONTRIBUTING.md for github using the commons build plugin

On 2014-08-20, Benedikt Ritter wrote: > 2014-08-20 13:13 GMT+02:00 Stefan Bodewig : >> On 2014-08-20, Benedikt Ritter wrote: >>> I've committed a new mojo to the commons build plugin, which generates a >>> README.md file for a component [1]. >> Without looking at the code, do you plan to make i

Re: svn commit: r1619091 - /commons/proper/daemon/branches/1.0.x/pom.xml

On 20 August 2014 23:03, Emmanuel Bourg wrote: > Le 20/08/2014 14:45, s...@apache.org a écrit : > >> - http://commons.apache.org/daemon/ >> + http://commons.apache.org/proper/commons-daemon/ > > Hi Sebastian, could we keep the short URLs please? We still have an open > ticket to revert the URLs

Re: svn commit: r1619091 - /commons/proper/daemon/branches/1.0.x/pom.xml

Le 20/08/2014 14:45, s...@apache.org a écrit : > - http://commons.apache.org/daemon/ > + http://commons.apache.org/proper/commons-daemon/ Hi Sebastian, could we keep the short URLs please? We still have an open ticket to revert the URLs to the short form. Emmanuel Bourg --

Re: [ALL] Auto generating README.md and CONTRIBUTING.md for github usingthe commons build plugin

Hello, sounds good. I wonder if all the parent magic could be avoided by specifying the mojo goal fully qualified for a stand alone goal. Since you want to commit the result anyway it is not used so often. Bernd -- http://bernd.eckenfels.net - Ursprüngliche Nachricht - Von: "Benedikt

Re: [JCS] Rework logging

I plan to dig into it before cause if i describe it I fear it will not be clear enough from log4j point of view - no words worth a patch ;). Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/

Re: [JCS] where are we?

>From >https://issues.apache.org/jira/browse/JCS/fixforversion/12312535/?selectedTab=com.atlassian.jira.jira-projects-plugin:version-summary-panel i see nothing blocking for a beta (and thinking to it maybe we can keep beta until we fix the logging issue) wdyt? Romain Manni-Bucau Twitter: @rman

Re: [JCS] Rework logging

On Wed, Aug 20, 2014 at 11:37 AM, Romain Manni-Bucau wrote: > If take tomee stack as reference (to list a few: cxf, bval, owb, > openejb, tomcat). Noone is integrated with log4j2 API. So suppose > we move jcs to log4j2 then to integrate it with tomee we'll need to > shade it to remove log4j2

Re: [JCS] Rework logging

well think nobody doubt we need it to stay enterprise friendly Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-08-20 19:02 GMT+00:00 Gary Gregory : > On Wed, Aug 20, 2014

Re: [JCS] Rework logging

On Wed, Aug 20, 2014 at 2:59 PM, Romain Manni-Bucau wrote: > how do you handle levels and names then? > You dont't: "as simple as it gets". For more, you need a framework. Gary > > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linke

Re: [JCS] Rework logging

how do you handle levels and names then? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-08-20 20:54 GMT+02:00 Gary Gregory : > On Wed, Aug 20, 2014 at 1:31 PM, Thomas Va

Re: [JCS] Rework logging

On Wed, Aug 20, 2014 at 1:31 PM, Thomas Vandahl wrote: > Hi folks, > > On 20.08.14 16:41, Romain Manni-Bucau wrote: > > trying to make it complete: > > > > Solutions are: > > 1) [logging] - think it is deprecated too > > 2) log4j2: not integrated at all with anything so a bit early but we > > *ne

Re: [JCS] Rework logging

On Wed, Aug 20, 2014 at 1:35 PM, Thomas Vandahl wrote: > On 20.08.14 15:37, Gary Gregory wrote: > > On Wed, Aug 20, 2014 at 9:28 AM, sebb wrote: > > > >> On 20 August 2014 14:04, Gary Gregory wrote: > >>> Moving discussion about logging from [JCS-122] to this dev ML. > >>> > >>> Why not use Log

Re: [JCS] Rework logging

On 20.08.14 15:37, Gary Gregory wrote: > On Wed, Aug 20, 2014 at 9:28 AM, sebb wrote: > >> On 20 August 2014 14:04, Gary Gregory wrote: >>> Moving discussion about logging from [JCS-122] to this dev ML. >>> >>> Why not use Log4j 2, uses can redirect logging to other frameworks if >>> needed. >>

Re: [JCS] Rework logging

Hi folks, On 20.08.14 16:41, Romain Manni-Bucau wrote: > trying to make it complete: > > Solutions are: > 1) [logging] - think it is deprecated too > 2) log4j2: not integrated at all with anything so a bit early but we > *need* to be compatible > 3) slf4j: broken in hierarchical classloaders > 4)

Re: svn commit: r1617882 - /commons/proper/compress/trunk/src/main/java/org/apache/commons/compress/archivers/sevenz/CLI.java

On 14 August 2014 06:38, wrote: > Author: bodewig > Date: Thu Aug 14 05:38:59 2014 > New Revision: 1617882 > > URL: http://svn.apache.org/r1617882 > Log: > deal with files without parent > > Modified: > > commons/proper/compress/trunk/src/main/java/org/apache/commons/compress/archivers/seven

Re: [JCS] Rework logging

Yes, that's what I try to say more or less. TomEE doesn't change Tomcat that much (just allows to switch backend more easily hacking LogFactory to be concrete). Main issue is slf4j, log4j2 etc...doesn't have a setup which can work for app "de facto" as JUL has with the famous system properties set

Re: [JCS] Rework logging

On 20/08/2014 15:41, Romain Manni-Bucau wrote: > trying to make it complete: > > Solutions are: > 1) [logging] - think it is deprecated too > 2) log4j2: not integrated at all with anything so a bit early but we > *need* to be compatible > 3) slf4j: broken in hierarchical classloaders > 4) JUL: not

Re: [JCS] Rework logging

If take tomee stack as reference (to list a few: cxf, bval, owb, openejb, tomcat). Noone is integrated with log4j2 API. So suppose we move jcs to log4j2 then to integrate it with tomee we'll need to shade it to remove log4j2 dependency to ensure it works. Other issue is log4j2 is quite broken

Re: [JCS] Rework logging

On Wed, Aug 20, 2014 at 10:41 AM, Romain Manni-Bucau wrote: > trying to make it complete: > > Solutions are: > 1) [logging] - think it is deprecated too > 2) log4j2: not integrated at all with anything What do you mean by "integrated"? Log4j 2 provides a SLF4J bridge for example. Or do you mean

Re: [JCS] Rework logging

On Wed, Aug 20, 2014 at 10:17 AM, Yogesh Rao wrote: > Hi Gary, > > Not that i have anything against the log4j 2 guys :-) its just that log4j > 2 combines both the API and a implementation I am right now not sure of how > the segregation has been done between them i.e. during deployment when > us

Re: [JCS] Rework logging

Sorry but not sure to get how how it helps. That's not because it is used that it works for us. If you check deeper these libs are mostly in the same ecosystem and some of them supports other logging frameworks too. Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/

Re: [JCS] Rework logging

>From SLF4J homepage: Here is a non-exhaustive list of [Apache] projects known to depend on SLF4J: - Apache ActiveMQ - Apache Archiva - Apache Camel - Apache Directory

Re: [JCS] Rework logging

trying to make it complete: Solutions are: 1) [logging] - think it is deprecated too 2) log4j2: not integrated at all with anything so a bit early but we *need* to be compatible 3) slf4j: broken in hierarchical classloaders 4) JUL: not that friendly but prod ready in tomcat/tomee 5) custom logging

Re: [JCS] Rework logging

+1 for log4j2 2014-08-20 17:22 GMT+03:00 David Green : > +1 for slf4j > > > > On 20 August 2014 14:54, Yogesh Rao wrote: > > > Though i am not a member of the dev team :-) I would support a full > fledge > > facade implementation which doesn't provide any logging at all and let > the > > framew

Re: [JCS] Rework logging

+1 for slf4j On 20 August 2014 14:54, Yogesh Rao wrote: > Though i am not a member of the dev team :-) I would support a full fledge > facade implementation which doesn't provide any logging at all and let the > framework user decide which logging would he would like to bind it to. > SLF4J doe

Re: [JCS] Rework logging

Hi Gary, Not that i have anything against the log4j 2 guys :-) its just that log4j 2 combines both the API and a implementation I am right now not sure of how the segregation has been done between them i.e. during deployment when using it in API mode does it have any dependency on other log4j2 ja

Re: [JCS] Rework logging

On Wed, Aug 20, 2014 at 9:54 AM, Yogesh Rao wrote: > Though i am not a member of the dev team :-) I would support a full fledge > facade implementation which doesn't provide any logging at all and let the > framework user decide which logging would he would like to bind it to. > SLF4J does that v

Re: [JCS] Rework logging

On Wed, Aug 20, 2014 at 9:47 AM, sebb wrote: > On 20 August 2014 14:37, Gary Gregory wrote: > > On Wed, Aug 20, 2014 at 9:28 AM, sebb wrote: > > > >> On 20 August 2014 14:04, Gary Gregory wrote: > >> > Moving discussion about logging from [JCS-122] to this dev ML. > >> > > >> > Why not use Log

Re: [JCS] Rework logging

Though i am not a member of the dev team :-) I would support a full fledge facade implementation which doesn't provide any logging at all and let the framework user decide which logging would he would like to bind it to. SLF4J does that very neatly and its also easy, i am also aware it might turn d

Re: [JCS] Rework logging

On 20 August 2014 14:37, Gary Gregory wrote: > On Wed, Aug 20, 2014 at 9:28 AM, sebb wrote: > >> On 20 August 2014 14:04, Gary Gregory wrote: >> > Moving discussion about logging from [JCS-122] to this dev ML. >> > >> > Why not use Log4j 2, uses can redirect logging to other frameworks if >> > n

Re: [ALL] Auto generating README.md and CONTRIBUTING.md for github using the commons build plugin

Sounds like a good idea. Gary On Wed, Aug 20, 2014 at 5:55 AM, Benedikt Ritter wrote: > Hi all, > > I've committed a new mojo to the commons build plugin, which generates a > README.md file for a component [1]. README.md files are used by github to > create some kind of a landing page, when yo

Re: [JCS] Rework logging

On Wed, Aug 20, 2014 at 9:28 AM, sebb wrote: > On 20 August 2014 14:04, Gary Gregory wrote: > > Moving discussion about logging from [JCS-122] to this dev ML. > > > > Why not use Log4j 2, uses can redirect logging to other frameworks if > > needed. > > Why not use Commons Logging, can redirect l

Re: [JCS] Rework logging

On 20 August 2014 14:04, Gary Gregory wrote: > Moving discussion about logging from [JCS-122] to this dev ML. > > Why not use Log4j 2, uses can redirect logging to other frameworks if > needed. Why not use Commons Logging, can redirect logging to other frameworks if needed? > Gary > > -- > E-Mai

[JCS] Rework logging

Moving discussion about logging from [JCS-122] to this dev ML. Why not use Log4j 2, uses can redirect logging to other frameworks if needed. Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition JUnit in Act

Re: [ALL] Auto generating README.md and CONTRIBUTING.md for github using the commons build plugin

2014-08-20 13:13 GMT+02:00 Stefan Bodewig : > On 2014-08-20, Benedikt Ritter wrote: > > > I've committed a new mojo to the commons build plugin, which generates a > > README.md file for a component [1]. > > Without looking at the code, do you plan to make it so that projects can > override the def

Re: [ALL] Auto generating README.md and CONTRIBUTING.md for github using the commons build plugin

On 2014-08-20, Benedikt Ritter wrote: > I've committed a new mojo to the commons build plugin, which generates a > README.md file for a component [1]. Without looking at the code, do you plan to make it so that projects can override the default README.md with a template of their own - much like w

[ALL] Auto generating README.md and CONTRIBUTING.md for github using the commons build plugin

Hi all, I've committed a new mojo to the commons build plugin, which generates a README.md file for a component [1]. README.md files are used by github to create some kind of a landing page, when you browse a repository. It makes a repository more inviting to people using github, so I consider it