Which of your dependencies do you need help with? I did the POM for
Commons Logging 1.1.1, so I have a pretty good idea of what's needed.
I had marked all the other dependencies for log4j as optional, because
prior to Maven, that is technically what people had been doing
naturally
dependencies that you need to
compile, but that a user of your jar might only need one of (think
oracle vs mssql bindings).
-Original Message-
From: Paul Smith [mailto:[EMAIL PROTECTED]
Sent: Friday, May 09, 2008 4:42 PM
To: Maven Users List
Subject: Re: Dependency scope - provided
Paul Smith wrote:
Could some explain the difference between the dependency scope
provided versus optional if there actually is any..
We have converted log4j over to Maven recently and accidently forgot to
mark a few dependencies with flags indicating that, while needing for
compile time
Could some explain the difference between the dependency scope
provided versus optional if there actually is any..
We have converted log4j over to Maven recently and accidently forgot
to mark a few dependencies with flags indicating that, while needing
for compile time, should
scope
provided versus optional if there actually is any..
We have converted log4j over to Maven recently and accidently forgot
to mark a few dependencies with flags indicating that, while needing
for compile time, should not necessarily be enforced on the end user.
I refer people
On 10/05/2008, at 9:38 AM, Brianefox wrote:
Provided means to include in the compile do but not in the package
(war)
Optional means that it wont be pulled in transitively by users of
your jar
From this, I gather Optional is actually what we want. Would it be
fair to say that Optional
: Re: Dependency scope - provided or optional.. ?
On 10/05/2008, at 9:38 AM, Brianefox wrote:
Provided means to include in the compile do but not in the package
(war)
Optional means that it wont be pulled in transitively by users of
your jar
From this, I gather Optional is actually what
