OK, I'm really hoping someone can provide some more insight on this as I
have reached my limit.
To make things clearer, I have created a project containing
integration-tests showing the failure that is causing us grief (external
wagon dependencies not being resolvable from within
MavenLifeCyclePar
It honestly should all be closed up. There are odd openings in the API to allow
strange forms of reactor resolution which is likely what you're running into.
The most bizarre form of reactor resolution occurs in the maven-eclipse-plugin
which essentially redoes reactor resolution entirely becaus
Unintentional, I had the change here in my workspace.
On May 17, 2014, at 5:39 AM, Hervé BOUTEMY wrote:
> is the System.out.println really intended or just forgotten cleanup once you
> figured out the solution?
>
> Regards,
>
> Hervé
>
> Le jeudi 15 mai 2014 17:14:52 jvan...@apache.org a écr
is the System.out.println really intended or just forgotten cleanup once you
figured out the solution?
Regards,
Hervé
Le jeudi 15 mai 2014 17:14:52 jvan...@apache.org a écrit :
> Repository: maven-plugin-testing
> Updated Branches:
> refs/heads/master c53f5ef30 -> d4c57479d
>
>
> MPLUGINTES
