On 20/03/2009, James Carman <ja...@carmanconsulting.com> wrote: > On Fri, Mar 20, 2009 at 11:40 AM, sebb <seb...@gmail.com> wrote: > > It's only optional at run-time; it's not optional at compile-time. > > > > > Right. That's what optional means.
I thought I understood optional, obviously I didn't. How does one express a dependency that really is optional at compile time? > Putting it as optional in Maven > will change the dependencies report: > > http://commons.apache.org/proxy/dependencies.html I find the text on the report very confusing. Does (optional) mean "optional at compile and runtime" or "optional for transitive dependencies"? Or something else? [BTW, JUnit should be updated to 3.8.2] Niall wrote that the use of optional caused problems for OSGI dependencies, and I thought I saw that myself when I tried building httpcore-osgi earlier - but now when I try that it works fine. My head is spinning! > None of the dependencies in Proxy (other than the JDK itself) are > required. However, maven does put them on the classpath so that Proxy > will compile. When a user declares a dependency on Proxy, they don't > get all of that extra stuff automatically. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
