logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lilianne E. Blaze" <lilianne_bl...@tlen.pl>
Subject Re: Small patch for NTEventLogAppender
Date Fri, 12 Oct 2007 17:36:01 GMT
Hello,
Then, could you please consider adding the following (or similar) file:

Index: BUILD-ON-WINDOWS
--- BUILD-ON-WINDOWS Locally New
+++ BUILD-ON-WINDOWS Locally New
@@ -0,0 +1,11 @@
+Default build configuration tries to build and test NTLogEventAppender,
which
+is partially based on Windows32 native code.
+
+To build Log4j on Windows32 you need to either
+
+1a) Install MinGW [someone please provide more details]
+
+Or
+
+1b) Copy NTEventLogAppender.dll from binary Log4j distribution to your
system
+directory (usually C:\Windows\System32)
\ No newline at end of file


Greetings, Lilianne E. Blaze

Curt Arnold wrote:
>
> On Oct 11, 2007, at 11:20 PM, Lilianne E. Blaze wrote:
>
>> Looks like it's not enough. Is there any simple way to just tell maven
>> to skip the tests? There is an option in NB that says just that, but it
>> doesn't work. Probably having something to do with three different build
>> scripts.
>> For now I just put that dll in %system% and it works, I'll look into it
>> later. To be honest, so far re-compiling log4j wasn't exactly
>> straightforward.
>>
>
> Sorry, I don't use Netbeans and it didn't know that it was invoking
> Maven which in turn invokes Ant.  Maven does not pass system
> properties on to Ant, but you could backdoor it by creating
> tests/build.properties containing:
>
> skip-nteventlogtest=whatever
>
> Since the tests/build.xml file will load build.properties if it exists.
>
> The simple way to tell Maven not to run the tests, is to not select a
> goal that requires the tests to be run, for example, "compile". 
> "package" which creates a Jar, does run the unit tests.  If you really
> don't want Netbeans to run any of the tests, you could use the same
> unless="..." trick on the "runAll" target.
>
> Also, if you had MinGW installed, then the build script should build
> NTEventLogAppender.dll and place it on the path for the unit tests and
> you should not need to have to place it in %system%.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message