commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simon Kitching <skitch...@apache.org>
Subject Re: svn commit: r476429 - /jakarta/commons/proper/logging/trunk/pom.xml
Date Sat, 18 Nov 2006 04:02:56 GMT
On Fri, 2006-11-17 at 20:53 -0700, Wendy Smoak wrote:
> On 11/17/06, skitching@apache.org <skitching@apache.org> wrote:
> > Author: skitching
> > Date: Fri Nov 17 19:41:32 2006
> > New Revision: 476429
> >
> > URL: http://svn.apache.org/viewvc?view=rev&rev=476429
> > Log:
> > Add comments about unusual dependency-handling approach.
> ...
> >     if we declare them optional then
> > +    - when JCL is *compiled* we get none of them in the classpath.
> 
> Are you saying that if you mark the dependencies optional, you get
> compilation errors?  That doesn't sound right.

Well, that's exactly what happens.

[INFO] Compilation failure

/home/simon/apache/commons-svn/proper/logging/trunk/src/java/org/apache/commons/logging/impl/Log4JLogger.java:[23,24]
package org.apache.log4j does not exist

etc

> 
> If you mark it optional, it will be excluded from transitive
> dependency resolution when a project depends on commons-logging.  But
> it should be on the compile-time classpath.
> 

That's what I'd like to see happen, but it doesn't appear to (using
maven 2.0.4 on Linux).

Regards,

Simon


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message