Robert and Stuart; thank you for fixing the bug introduced by my change,
with such a clear explanation and without a major reversion.
>From your description of this as an edge case, it doesn't seem like this
quite deserves a new test in maven-integration-testing, but it may be worth
testing with t
As an interested contributor, I've opened a couple of pull requests, and
it's not always clear what the next step is for a non-project-member to get
things merged.
To see how other PRs (https://github.com/apache/maven/pulls -- currently,
'32 open') are being handled, I thought it might make sense
I've taken a look at two cleanup tasks for maven-eclipse-plugin.
One is a clearout of long-deprecated classes:
https://issues.apache.org/jira/browse/MECLIPSE-697
and the other is updating the mojos to use annotations:
https://issues.apache.org/jira/browse/MECLIPSE-758
Both have patches
I've filed MDEP-361 and MDEP-362 against the new dependency:tree
implementation. It'd be nice to see them resolved before a final release.
On 31/07/12 07:34, Christian Schulte wrote:
-1 (unbinding)
The dependency plugin still contains 'System.out.println' statements.
Am 07/30/12 22:50, schri
