On 27 Jul 2011, at 01:27, Ansgar Konermann <ansgar.konerm...@googlemail.com
> wrote:
Am 26.07.2011 00:56, schrieb Kasun Gajasinghe:
So, doesn't having an intermediary layer that will
point to newer set of plugins is justified?
Sure.
Simplest solution that will work: use your own parent pom with an
updated <pluginManagement> section.
As I explained before, parent pom thing has few caveats.
Btw, lot of problems occured to me because of the maven super pom,
which, apparently has some hard-coded (quite old) plugin versions. (As
I've read [1], the super pom is something like Java's java.lang.Object
that every class inherits properties from.)
So, I could get over some issues if I can patch the plugin versions in
super pom according to our needs. Unfortunately, I can't find it
exists in source.
Can anyone shed a light on where I could find the super pom?
Thanks,
Kasun
[1] http://maven.apache.org/pom.html#The_Super_POM
Ansgar
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
