You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Craig McClanahan <cr...@apache.org> on 2006/11/18 03:52:36 UTC

[logging] Maven2 POM Question

The pom.xml file for Commons Logging in the trunk has an "interesting"
approach to declaring dependencies, based on the existence or non-existence
of a file named "commons-logging-README.txt".  AFAICT, the purpose for this
is to make the dependencies non-optional when you are building Commons
Logging itself, but optional for downstream users.

Is that a correct understanding of the purpose?  If so, we should really
document this in the pom.xml file, so others don't have to puzzle out the
thinking.

Craig

Re: [logging] Maven2 POM Question

Posted by Wendy Smoak <ws...@gmail.com>.
On 11/17/06, Simon Kitching <sk...@apache.org> wrote:

> Sorry :-). That's exactly the purpose. I'll add a comment now.

I saw the commit before the thread, so commented there.

Marking a dependency 'optional' excludes it from transitive dependency
resolution, nothing more.  It should still be on the compile time
classpath.

(For example, that's how we compile Shale Test against HtmlUnit and
Cargo, but don't impose those dependencies on every Shale Test user.)

-- 
Wendy

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


Re: [logging] Maven2 POM Question

Posted by Simon Kitching <sk...@apache.org>.
On Fri, 2006-11-17 at 18:52 -0800, Craig McClanahan wrote:
> The pom.xml file for Commons Logging in the trunk has an "interesting"
> approach to declaring dependencies, based on the existence or non-existence
> of a file named "commons-logging-README.txt".  AFAICT, the purpose for this
> is to make the dependencies non-optional when you are building Commons
> Logging itself, but optional for downstream users.
> 
> Is that a correct understanding of the purpose?  If so, we should really
> document this in the pom.xml file, so others don't have to puzzle out the
> thinking.

Sorry :-). That's exactly the purpose. I'll add a comment now.



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