i think of it like so... if no value in plugin configuration in pom, then evaluate expression, if expression evaluates to null, then use default value, if still here, don't inject into the field (so the fields initializer from the jvm/class applies)
- Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 13 Dec 2011 17:44, "Laird Nelson" <ljnel...@gmail.com> wrote: > On Tue, Dec 13, 2011 at 12:39 PM, Laird Nelson <ljnel...@gmail.com> wrote: > > > On Tue, Dec 13, 2011 at 12:36 PM, Guillaume Polet < > > guillaume.po...@gmail.com> wrote: > > > >> use mvn help:effective-pom to find out. My guess would be 1.5. > >> > > > > OK; I was more curious to know how one would determine whether there was > a > > bug in Maven's property precedence rules. If the answer is: "use Maven > and > > see what it says, that's the answer" :-) then there cannot be a bug in > this > > area. :-) :-) > > > > Actually, mvn help:effective-pom won't do it, BTW; it will simply show what > the <properties> property is, not the actual configuration values. I > guess mvn > -X will tell me what Maven *happens* to be doing. I'll start there. > > best, > Laird > > -- > http://about.me/lairdnelson >
