javabrett wrote:
>
> Further, a build in m2eclipse 0.9.8.200905041414 using the Embedded mvn
> (which version is that?), _does_ throw the WARNING (which is what I want).
>
> Does anyone know how these warnings are supposed to work and whether their
> behaviour has changed recently? It's a sha
Further, a build in m2eclipse 0.9.8.200905041414 using the Embedded mvn
(which version is that?), _does_ throw the WARNING (which is what I want).
Does anyone know how these warnings are supposed to work and whether their
behaviour has changed recently? It's a shame if you can't force a
relocati
Hi,
I'm trying to understand if there is a regression or deliberate change
in WARNING reporting of relocated artifacts between Maven 2.0.9 and
Maven 2.1.0.
I tested with a well-known relocated artifact servletapi:servletapi:2.3
which is relocated to javax.servlet:servlet-api:2.3. Test POM a
