Here are the files that I think you need.
- jnisyslog.tar.gz contain the java file and the C file. Inside this file there is also a test directory, which contains a test program and .lcf file that is called by the test.jnisyslog target in the build.xml changes I have made.
- build.xml.diff if the output of the following command "cvs diff -u build.xml > build.xml.diff"
Let me know if you need anything else. I think that I have explained everything you would need in the javadocs.
Please let me know if this will make it into the baseline.
Thanks again !!!!!
-------Original Message-------
> From: Paul Smith <[EMAIL PROTECTED]>
> Subject: Re: Prototype written : JNI Syslog appender
> Sent: 29 Feb 2004 21:45:33
>
> On Sun, 2004-02-29 at 14:36, log4jdev wrote:
> > I have written a JNI based syslog appender. I would like to submit
> > this code to the group for approval. Is there a formal process for
> > doing so?
>
> Apologise for the brevity of this email, I'm a bit snowed under:
>
> * Please conform to the Log4j coding conventions, if you use Jalopy, you
> can use the log4j-coding-conventions.xml file under the src/jalopy
> directory of the Log4j CVS module.
>
> * Documentation within the main java file is incredibly important, with
> any notes as to configuration etc to get it working.
>
> * Post your files to a new Bugzilla item. (this prevents it from getting
> lost) - ideally its in the "diff -u" format, but since it's probably all
> new files, the new java file, or zip up multiple.
>
> * Also post the above to the log4j-dev list for review.
>
> regards,
>
> Paul Smith
-------Original Message-------
jnisyslog.tar.gz
Description: Binary data
build.xml.diff
Description: Binary data
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
