On 06.06.2012 09:53, Christian Grobmeier wrote:
On Tue, Jun 5, 2012 at 5:35 PM, ceki<c...@qos.ch> wrote:
Right. Lf5 and chainsaw merit to be in different projects. You are also
right to point out that I had module and project confused. If the
modules have different release cycles they should be in different
projects.
There is currently no one working on Lf5 or chainsaw1 to my knowledge.
Therefore I'd lets make them modules, as they will most likely not see
a release outside log4j1.x
My point about separately documenting lof4j-uber.jar and the log4j-*
jars remains valid though.
I don't see a big issue here.
There are no big issues involved here. We are talking about making a
fine adjustment.
I think Documentation for maven users which tell them what to include
is much more easier than knowing what to exclude. Inclusion is
standard, for ecxlusion i always need to google. In fact, since I know
about the Shade plugin I am always angry with people who force me make
my pom.xml look even more messy with exclusions.
No one is arguing for non-optional dependencies. I also find projects
requiring exclusions lame. The way dependencies are currently declared
in log4j is sub-optimal (to put it politely) and should only be taken
as an example of what not to do. However, the current approach should
not serve as justification for forcing the pendulum too far in the
other direction. More below.
That being said, currently I see the following modules below log4j-parent:
log4j-parent
+--log4j-core
+--log4j-chainsaw
+--log4j-lf5
+--log4j-smtpappender
+--log4j-ee (* contains the code whic uses Geronimo dependencies)
+--log4j-ntdll (* pending NAR plugin evaluation)
This makes sense. As stated earlier, I'd recommend merging log4j-ee
(more precisely the o.a.log4j.net package) with log4j-core. It's just
a recommendation, feel free to ignore.
Cheers,
--
Ceki
http://twitter.com/#!/ceki
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
