Paul,
thanks for this hint. I believed that the trunk actually contained the
log4j 2.0 code (where is that?).
I got log4j to compile. However, I had to grab the
NTEventLogAppender.dll from the prebuilt log4j-1.2.15 to my Windows
system directory to pass all unit tests. Can this "hack" be further
improved?
Now, while trying to build zeroconf, I'm already waiting several minutes
to complete the "Running
org.apache.log4j.net.ZeroConfSocketHubAppenderTest" step - it seems to
do plain nothing, but the build process is waiting for it. I'll give it
another hour, but I'm not very hopeful... CPU usage is low, and there is
no network traffic either...
Oliver
Paul Smith schrieb:
On 22/06/2008, at 7:44 PM, Oliver Frietsch wrote:
Hello list,
As there might be differences between 1.2.15 and 1.2.16, I then
checked out the latest 1.2.15 tag from SVN that I could find
(/v1_2_15, there is no 1.2.16!), and tried to build that. This is the
result:
There is ono 1.2.16 tag as you mention, because 1.2.16 is not released,
it is in fact held in trunk as a snapshot.
So, the missing steps are:
* get log4j trunk
* mvn install (this will install log4j 1.2.16-SNAPSHOT locally)
I believe that will resolve the zeroconf build problem and let you
continue.
I'll update the build info for Chainsaw, it's slipped out of sync.
thanks for the pickup.
The main reason for the lack of releases is to conform to a policy of
only releasing voted on releases, and the fact that Chainsaw depends on
-SNAPSHOT versions of some log4j sub modules of which we're (slowly)
getting closer to release quality.
cheers,
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
