It's really that this goal and the go-offline where some experimental ones I wrote eons ago. It doesn't find the plugins that are injected by default lifecycles. I have code now in the enforcer to detect these, but it hasn't been shared with the dependency plugin yet. So bug, possibly..more like unfinished ;-)
On Fri, Jan 8, 2010 at 11:43 AM, Weber, Stephan <[email protected]> wrote: > Hi, > > it would be nice to have a list of REALLY ALL downloaded/used dependencies of > a complete maven lifecycle - including ALL the maven plugins. > > I played around with the dependency tool (dependency:resolve, > dependency:resolve-plugins): > I start with an empty local repo and a minimal pom. After a mvn clean install > I have many more artifacts and especially maven plugins just being downloaded > to the local repo than are reported by the dependency plugin. > > Is this a bug? If not, how else can we make maven generate a complete > 'used-artifacts-and-plugins-list' containing everything(!) that has been > downloaded to or was taken from the local repository during a whole lifecycle? > > Regards, Stephan > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
