Hi Ceki. After careful consideration I'd like to migrate the log4j routines I have written which caters to the AS/400[1] world into logback, hopefully benefitting the small but thriving "java on AS/400"-community[2] by providing better integration with qsysopr messages, spool files, qprint output and much more that I have only seen on this platform. As this introduces a new software dependency, namely on the jt400 sourceforge project, and on actual hardware to run the tests against which is rather impossible for mere mortals, I would suggest that this should go in a new logback subproject incubator instead of being merged in any of the current logback projects. What do you think? [1] IBM marketing has renamed the platform regularily, currently it is named "IBM i". [2] http://archive.midrange.com/java400-l/ -- Thorbjørn Ravn Andersen "...plus... Tubular Bells!"
I am starting to wonder if ext should be a root directory for some subprojects. For example, AOP could be one subproject, utils another, AS400 a third. Then we wouldn't need to make the dependencies optional, but it will lead to more jars. FWIW, I worked with Java on OS/400 about 8 or 9 years ago. It had really, really ugly APIs back then. I don't have access to an AS/400 any more so I can't really help with that. My only concern with bringin them into SLF4J would simply be that you would be the only committer who could actually test them. Ralph On Mon, Nov 17, 2008 at 5:39 AM, Thorbjørn Ravn Andersen < thunderaxiom@gmail.com> wrote:
Hi Ceki.
After careful consideration I'd like to migrate the log4j routines I have written which caters to the AS/400[1] world into logback, hopefully benefitting the small but thriving "java on AS/400"-community[2] by providing better integration with qsysopr messages, spool files, qprint output and much more that I have only seen on this platform.
As this introduces a new software dependency, namely on the jt400 sourceforge project, and on actual hardware to run the tests against which is rather impossible for mere mortals, I would suggest that this should go in a new logback subproject incubator instead of being merged in any of the current logback projects.
What do you think?
[1] IBM marketing has renamed the platform regularily, currently it is named "IBM i". [2] http://archive.midrange.com/java400-l/
-- Thorbjørn Ravn Andersen "...plus... Tubular Bells!"
_______________________________________________ logback-dev mailing list logback-dev@qos.ch http://qos.ch/mailman/listinfo/logback-dev
Oh. Darn. I was thinking I was on the slf4j-dev list. The second paragraph still applies. I'd wonder where you want to put this in logback. Ralph On Mon, Nov 17, 2008 at 11:43 AM, ralph.goers @dslextreme.com < rgoers@apache.org> wrote:
I am starting to wonder if ext should be a root directory for some subprojects. For example, AOP could be one subproject, utils another, AS400 a third. Then we wouldn't need to make the dependencies optional, but it will lead to more jars.
FWIW, I worked with Java on OS/400 about 8 or 9 years ago. It had really, really ugly APIs back then. I don't have access to an AS/400 any more so I can't really help with that. My only concern with bringin them into SLF4J would simply be that you would be the only committer who could actually test them.
Ralph
On Mon, Nov 17, 2008 at 5:39 AM, Thorbjørn Ravn Andersen < thunderaxiom@gmail.com> wrote:
Hi Ceki.
After careful consideration I'd like to migrate the log4j routines I have written which caters to the AS/400[1] world into logback, hopefully benefitting the small but thriving "java on AS/400"-community[2] by providing better integration with qsysopr messages, spool files, qprint output and much more that I have only seen on this platform.
As this introduces a new software dependency, namely on the jt400 sourceforge project, and on actual hardware to run the tests against which is rather impossible for mere mortals, I would suggest that this should go in a new logback subproject incubator instead of being merged in any of the current logback projects.
What do you think?
[1] IBM marketing has renamed the platform regularily, currently it is named "IBM i". [2] http://archive.midrange.com/java400-l/
-- Thorbjørn Ravn Andersen "...plus... Tubular Bells!"
_______________________________________________ logback-dev mailing list logback-dev@qos.ch http://qos.ch/mailman/listinfo/logback-dev
ralph.goers @dslextreme.com wrote:
FWIW, I worked with Java on OS/400 about 8 or 9 years ago. It had really, really ugly APIs back then. I don't have access to an AS/400 any more so I can't really help with that. My only concern with bringin them into [logback] would simply be that you would be the only committer who could actually test them.
I share the same concern. At the same time, if Thorbjoern is committed to this project I'd like to encourage him even if I can't help directly with the code.
Ralph -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch
Ceki Gulcu skrev:
ralph.goers @dslextreme.com wrote:
FWIW, I worked with Java on OS/400 about 8 or 9 years ago. It had really, really ugly APIs back then. I don't have access to an AS/400 any more so I can't really help with that. My only concern with bringin them into [logback] would simply be that you would be the only committer who could actually test them.
I share the same concern. At the same time, if Thorbjoern is committed to this project I'd like to encourage him even if I can't help directly with the code.
I consider that to be a sounding **YES** then :D If so, would you create a suitable location in subversion for me, and ensure I have commit rights to this location? -- Thorbjørn Ravn Andersen "...plus... Tubular Bells!"
Hi Thorbjørn, Thank you for your proposal and for considering logback as a host for your software. How about setting up a sub-module for this? It could be under logback/logback-as400 (please confirm my choice of name). Do you rather it became an entirely different project? Thorbjørn Ravn Andersen wrote:
Hi Ceki.
After careful consideration I'd like to migrate the log4j routines I have written which caters to the AS/400[1] world into logback, hopefully benefitting the small but thriving "java on AS/400"-community[2] by providing better integration with qsysopr messages, spool files, qprint output and much more that I have only seen on this platform.
As this introduces a new software dependency, namely on the jt400 sourceforge project, and on actual hardware to run the tests against which is rather impossible for mere mortals, I would suggest that this should go in a new logback subproject incubator instead of being merged in any of the current logback projects.
What do you think?
[1] IBM marketing has renamed the platform regularily, currently it is named "IBM i". [2] http://archive.midrange.com/java400-l/
-- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch
Ceki Gulcu skrev:
Hi Thorbjørn,
Thank you for your proposal and for considering logback as a host for your software. How about setting up a sub-module for this? It could be under logback/logback-as400 (please confirm my choice of name). Do you rather it became an entirely different project? I believe you are the one who best can judge the location, and I can just give the facts as objectively as I can.
This will introduce a dependency on the jt400 project (which should be in maven) so compilation should be possible on any Java platform. Testing will require an AS/400 box. If this catches on, then I believe it should be possible to arrange something either with IBM or others. Time will tell. This also goes for the number of interested users :) I expect this code to be very stable and unchanging when mature, simply because the AS/400 is extremely focused on backward compatability. It will most likely be changes in either slf4j or logback that will trigger changes. There is precedent of JMS classes being in logback-classic (most likely to be log4j compatible), but I have no idea how hard this has been to maintain, so I'll leave it up to you. -- Thorbjørn Ravn Andersen "...plus... Tubular Bells!"
Thorbjørn, If you agree, I intend to create a module under https://svn.qos.ch/repos/incubator with you having read/write access. You will then be able to create any directory underneath. When your project matures we will see how it can be incorporated into logback-classic or logback-access or alternatively live its own separate life. Does that sound good to you? Thorbjørn Ravn Andersen wrote:
Ceki Gulcu skrev:
Hi Thorbjørn,
Thank you for your proposal and for considering logback as a host for your software. How about setting up a sub-module for this? It could be under logback/logback-as400 (please confirm my choice of name). Do you rather it became an entirely different project? I believe you are the one who best can judge the location, and I can just give the facts as objectively as I can.
This will introduce a dependency on the jt400 project (which should be in maven) so compilation should be possible on any Java platform. Testing will require an AS/400 box. If this catches on, then I believe it should be possible to arrange something either with IBM or others. Time will tell. This also goes for the number of interested users :)
I expect this code to be very stable and unchanging when mature, simply because the AS/400 is extremely focused on backward compatability. It will most likely be changes in either slf4j or logback that will trigger changes.
There is precedent of JMS classes being in logback-classic (most likely to be log4j compatible), but I have no idea how hard this has been to maintain, so I'll leave it up to you.
-- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch
Ceki Gulcu skrev:
Thorbjørn,
If you agree, I intend to create a module under https://svn.qos.ch/repos/incubator with you having read/write access. You will then be able to create any directory underneath. When your project matures we will see how it can be incorporated into logback-classic or logback-access or alternatively live its own separate life.
Does that sound good to you?
That would be fine. Thanks :) -- Thorbjørn Ravn Andersen "...plus... Tubular Bells!"
Done. Your current svn id works for logback as well. Give it a try. The repository URL is https://svn.qos.ch/repos/logback-incubator Do holler if you run into trouble. Thorbjørn Ravn Andersen wrote:
Ceki Gulcu skrev:
Thorbjørn,
If you agree, I intend to create a module under https://svn.qos.ch/repos/incubator with you having read/write access. You will then be able to create any directory underneath. When your project matures we will see how it can be incorporated into logback-classic or logback-access or alternatively live its own separate life.
Does that sound good to you?
That would be fine. Thanks :)
-- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch
Ceki Gulcu skrev:
Done. Your current svn id works for logback as well. Give it a try. The repository URL is https://svn.qos.ch/repos/logback-incubator
Great. Shows up here.
Do holler if you run into trouble.
Initial testing showed I was not allowed to write to logback-incubator/trunk. Could you give it a look? -- Thorbjørn Ravn Andersen "...plus... Tubular Bells!"
Thorbjørn Ravn Andersen wrote:
Ceki Gulcu skrev:
Done. Your current svn id works for logback as well. Give it a try. The repository URL is https://svn.qos.ch/repos/logback-incubator
Great. Shows up here.
Do holler if you run into trouble.
Initial testing showed I was not allowed to write to logback-incubator/trunk. Could you give it a look?
Things look OK on my end. What happens when you do: svn co https://svn.qos.ch/repos/logback-incubator/trunk logback-incubator cd logback-incubator touch test2 svn add test2 svn ci -m "testing" -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch
Ceki Gulcu skrev:
Thorbjørn Ravn Andersen wrote:
Ceki Gulcu skrev:
Done. Your current svn id works for logback as well. Give it a try. The repository URL is https://svn.qos.ch/repos/logback-incubator
Great. Shows up here.
Do holler if you run into trouble.
Initial testing showed I was not allowed to write to logback-incubator/trunk. Could you give it a look?
Things look OK on my end. What happens when you do:
svn co https://svn.qos.ch/repos/logback-incubator/trunk logback-incubator cd logback-incubator touch test2 svn add test2 svn ci -m "testing"
That apparently works... Hmm... Probably some more strangeness in Eclipse Subclipse. Oh well. I'll just do it that way then. Thanks. :) -- Thorbjørn Ravn Andersen "...plus... Tubular Bells!"
participants (4)
-
Ceki Gulcu -
ralph.goers ＠dslextreme.com -
Thorbjørn Ravn Andersen -
Thorbjørn Ravn Andersen