It's already on the roadmap.
I expect it was not being included transitively because the container is
test scope.
- Brett
John Casey wrote:
> it'd almost require an index of classes -> artifacts, but that index
> would be immensely useful IMO. Once we have something like that in a
> maintained s
it'd almost require an index of classes -> artifacts, but that index
would be immensely useful IMO. Once we have something like that in a
maintained state, it'd be easy to write a plugin to verify this sort of
thing.
Mark Hobson wrote:
On 30/11/05, John Casey <[EMAIL PROTECTED]> wrote:
that
On 30/11/05, John Casey <[EMAIL PROTECTED]> wrote:
> that's fair, but if it's directly used, it should be directly specified.
> It wasn't working on this end, so I'm not sure what the difference is...
I've often encountered this situation where direct dependencies are
not declared as they are supp
that's fair, but if it's directly used, it should be directly specified.
It wasn't working on this end, so I'm not sure what the difference is...
Emmanuel Venisse wrote:
build works fine on maven zone. plexus-utils is a transitive dep with
plexus-container-default
Emmanuel
[EMAIL PROTECTED]
build works fine on maven zone. plexus-utils is a transitive dep with
plexus-container-default
Emmanuel
[EMAIL PROTECTED] a écrit :
Author: jdcasey
Date: Wed Nov 30 07:50:02 2005
New Revision: 349968
URL: http://svn.apache.org/viewcvs?rev=349968&view=rev
Log:
Adding dep on p-u to fix the buil
