[logback-dev] AS/400 specific logback project.
rgoers at apache.org
Mon Nov 17 20:43:50 CET 2008
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
On Mon, Nov 17, 2008 at 5:39 AM, Thorbjørn Ravn Andersen <
thunderaxiom at 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 world into logback, hopefully
> benefitting the small but thriving "java on AS/400"-community 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?
>  IBM marketing has renamed the platform regularily, currently it is
> named "IBM i".
>  http://archive.midrange.com/java400-l/
> Thorbjørn Ravn Andersen "...plus... Tubular Bells!"
> logback-dev mailing list
> logback-dev at qos.ch
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the logback-dev