On 8/11/07, Adam Constabaris <[EMAIL PROTECTED]> wrote: > Maven2's "optional" dependencies are provided precisely for this use > case: some of the functionality in your project depends on X, but you > recognize that some users won't need that functionality. So what it > means that, for those who are pulling in Abdera from the maven > repositories and their project uses Spring, they'll have to explicitly > declare Spring as a dependency. Everybody else will be able to ignore it.
gotcha. it's likely that everybody who'd want to use abdera with spring would already have spring declared as a dependency in their project anyway, so this doesn't seem like a hardship at all.
