https://issues.apache.org/bugzilla/show_bug.cgi?id=42189
Curt Arnold <[EMAIL PROTECTED]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |ASSIGNED
--- Comment #18 from Curt Arnold <[EMAIL PROTECTED]> 2008-08-05 21:40:18 PST
---
Clearing NEEDINFO since it isn't appropriate for this bug. It should only be
used when it is impossible to understand the bug due to missing info. It
should not be used to try to grab the attention of developers since it would
have exactly the opposite effect. NEEDINFO bugs go to the bottom of the list
until the reporter (or someone else who has or understands the problem) provide
the missing INFO.
Release preparations require JDK 1.4 since Maven requires JDK 1.4, however the
bytecode generated in JRE 1.1 compatible. However, log4j.jar can alternatively
be built using Ant on JDK 1.3 (again targeting JRE 1.1 bytecode). Last I
checked, unit tests could be run on JRE 1.2, it just couldn't be built there
due to known compiler problems with JDK 1.2 (and would require an older version
of Ant).
If I remember correctly, JDK 1.5's javac had problems producing JDK 1.1
compatible bytecode.
Anyway, anything "cutting edge", "experimental" or controversial, should not be
in log4j.jar. The release cycles are too slow for anything rapidly evolving.
If we can't get people to test this as its own log4j companion, we definitely
shouldn't push it into log4j and force people to consume it and also freeze our
ability to change it.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
