On Jul 3, 2008, at 6:06 PM, Scott Deboy wrote:
log4j-receivers-3rdpartydeps? pretty hokey but a bit more accurate
The first thing that makes me think of is the third party licensing policy (http://www.apache.org/legal/3party.html) and suggests use of code that is not under the ASL. I'm not sure if we want to suggest a connection.
I'm guessing on this, so correct me if I'm wrong. Are we talking about receivers that are compiled against an abstract API (along the lines of JAXP or JDBC) but depends the availability of a concrete implementation to work and where the abstract API is compatible with the ASL but the concrete implementation may be an incompatible license? Or is it something different? Want to lay out specifics (API's and their license, implementations and their licenses)?
What about making apache-log4j-receivers a multi-artifact project, so you'd have apache-log4j-receivers.jar, apache-log4j-receivers-db.jar and apache-log4j-receivers-jms.jar?
This scenario seems to be what OSGi (see http://felix.apache.org) was designed to support where components could use their manifest to declare what services they require and the framework figures out what should be loaded. Unfortunately, I've never had time to ramp up on it.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
