Hi Mark, I agree with you it would be better not to add the dependencies to compile or test scope, but Eclipse does not understand and complains about compile errors in build classes. I think it will be the same with any IDE. So for now I think adding the dependencies to test scope is our best option.
On 9 May 2016, at 1:40, Hervé BOUTEMY wrote: Some little questions: 1. on https://javabuild.java.net/builder-maven-plugin/usage.html can the dependency on builder-api be test scope? (to avoid polluting the component dependencies with build requirements) I was thinking including the dependency INSIDE the <plugin> declaration might also be useful, if you wanted/needed to depend on extra libraries that should be build specific, they could also go there - and not pollute compile OR test scopes. Plugin looks kinda neat. Mark -- Mark Derricutt http://www.theoryinpractice.net http://www.chaliceofblood.net http://plus.google.com/+MarkDerricutt http://twitter.com/talios http://facebook.com/mderricutt
