On 15 Jun 2016, at 23:30, Igor Fedorenko wrote:
extensions.xml was meant for "non-functional" extensions, things like
Takari SmartBuilder, which improves multi-threaded build scheduling
but
does not affect overall build results. If your extensions change build
behaviour in non-trivial ways, your build is not Maven any more and
you
should expect to have to change tooling around the build.
Thing is, it is changing it in a trivial way - it just sets user
properties, we're just wanting to externalise the `<property>`
definition from the pom.xml file.
Ideally I'd much rather put it in:
<build><extensions/></build>
or a
<plugin><extensions>true</extensions></plugin>
block but it seems neither of those options want to run with
`afterProjectsRead`, however - even if it did - by that stage the
project has been read and variables already interpolated, which is why I
was looking at afterSessionStart - only, the only way for that to run is
from `.mvn/extensions.xml`.
Unless there's another way I could intercept POM reading and resolve
properties - in a "maven safe" manner.
Mark
--
Mark Derricutt
http://www.theoryinpractice.net
http://www.chaliceofblood.net
http://plus.google.com/+MarkDerricutt
http://twitter.com/talios
http://facebook.com/mderricutt
