What is everyone's opinion on changing maverick to use the Apache
Commons logging API instead of hardcoding a dependency on log4j. My
reason for wanting this would be to cut down on the large number of jar
files my project is accumulating.. I'd like to use java.util.logging as
much as possible. Thi
There have been a few global changes that have been pending for a
while. For instance there was the discussion of repackaging everything
to net.sf.mav.*. If I'm not mistaken there were a few other changes as
well. Maybe now would be an appropriate time to readdress some of the
changes including
That's what I proposed about a year ago, and I still am for replacing Log4J
by Commons Logging.
Eelco
- Original Message -
From: "Jon Newton" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, June 01, 2004 3:56 PM
Subject: [Mav-user] Use Apache Commons Logging instead of log4j
Sure. +1 to changing package names and moving to commons logging, or java
1.4 logging (I think we may have some problems running on 1.3 anyway, or was
it just some of our dependencies...).
It would probably be good to roll any good questions that have come up on
the list into the faq, and document
+1 on moving to commons-logging
-1 on moving to JDK1.4 logging
What problems are there running Maverick on JDK1.3? The only tricky
thing is making sure you have an XML parser since it isn't builtin.
The only thing preventing a move from log4j to commons-logging was the
absence of anyone who actu
I don't have an opinion either way, and no objections to those who are in
favor of the switch... but I guess I'm not really clear on how switching to
commons-logging helps the jar file explosion. As I see it:
Current: log4j.jar
Proposal: commons-logging.jar + log4j.jar -- or -- commons-logging.ja
If you'd give me commit rights I would be happy to do the dirty work ;)
Eelco (sf id eelco12)
- Original Message -
From: "Schnitzer, Jeff" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, June 01, 2004 8:33 PM
Subject: RE: [Mav-user] Use Apache Commons Logging instead of log4j
I'm kind of working on an Eclipse plugin for Maverick. After making some
contributions for the Jetty Plugin (http://spindle.sourceforge.net) I
decided that now is the time to really learn how to write them properly.
Right now, the plugin does some pretty printing of the Maverick config file,
and di
A lot of OSS projects nowadays support Commons Logging instead of Log4J
directly (e.g. Hibernate). So, there's a fat chance you allready have that
dependency. For Maverick users who want to use JDK logging or some other
mechanism they allready have a dependency on, it could mean one dependency
less
[snip]
>
> Do we have a volunteer to do the conversion?
I've looked at the code enough in the last week to feel comfortable
making the changes.. It seems pretty straight forward. But someone else
may be in a better position w/ cvs, etc. I would just submit patches.
>
> Jeff
>
>
---
Part of my wanting to use commons logging is to use java.util.logging
package. Because we're a tiny company we try to stick w/ built-in
libraries when possible. Even though the jar file count would stay the
same, I'm assuming the commons-logging library will change far less than
log4j? Therefor one
+1 on the patch.
I, as well as others, could commit the changes and then we can put together
a new release.
- Original Message -
From: "Jon Newton" <[EMAIL PROTECTED]>
[snip]
>
> Do we have a volunteer to do the conversion?
I've looked at the code enough in the last week to feel comfor
Actually, the only reason that Baritus has a dependency on Log4J, is because
Maverick has (and Baritus is an extension of Maverick). Velocity does not
have a direct dependency on Log4J (see
http://jakarta.apache.org/velocity/developer-guide.html#Configuring%20the%20Log%20System),
but it's probably
I propose making Eelco a committer.
I'm +1.
Jeff
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:mav-user-
> [EMAIL PROTECTED] On Behalf Of Eelco Hillenius
> Sent: Tuesday, June 01, 2004 11:58 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [Mav-user] Use Apache Commons Logging instead
+1, then he can put the link up :)
- Original Message -
From: "Schnitzer, Jeff" <[EMAIL PROTECTED]>
I propose making Eelco a committer.
I'm +1.
---
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux
What about using the config file to help navigate to the controller classes.
It would be nice to be able to see your project space in terms of the
commands and controllers, and then to navigate to the source files
associated with them. Just an idea...
Also, if you are using xsl stuff (with domify)
+1
On Jun 1, 2004, at 2:24 PM, Scott Hernandez wrote:
+1, then he can put the link up :)
- Original Message -
From: "Schnitzer, Jeff" <[EMAIL PROTECTED]>
I propose making Eelco a committer.
I'm +1.
---
This SF.Net email is sponsored b
17 matches
Mail list logo
