Hi,
On Mon, May 12, 2014 at 8:19 PM, Tammo van Lessen <tvanles...@gmail.com> wrote:
> very cool, that adds a feature that I was missing for quite a long time. I
> found my own solution [1] via monkey patching. If I understand your
dang - I wish I had seen that before ;)
> approach correctly, then all dependencies must be provided manually.
> Wouldn't it make sense initialize the dependencies entry with all compile
> time deps and give the user the possibility to override this "smart"
> default?
The way it does work is the way you want it to ... I think. All
compile.dependencies are added as pom dependencies in scope "compile".
You only need to specify artifact in the runtime_dependencies,
optional_dependencies and provided_dependencies lists if you want to
change the scope or optionality. The one thing that is not provided is
the ability to remove dependencies from pom. I am not sure if this is
a problem or not.
On another note, someone off list suggested that we add exlusions to
all our dependencies as buildr in theory is the resolved set of
dependencies. Something like the following works in maven3 apparently.
<exclusions>
<exclusion>
<groupId>*</groupId>
<artifactId>*</artifactId>
</exclusion>
</exclusions>
Thoughts?
--
Cheers,
Peter Donald
