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.
--
Regards,
Igor
On Wed, Jun 15, 2016, at 01:02 AM, Mark Derricutt wrote:
> Hey all,
> At work we're now making use of some custom
> AbstractMavenLifecycleParticipant's declared in .mvn/extensions.xml
> and whilst our command line builds all work flawlessly ( our own minor
> bugs withstanding ) I'm noticing that IntelliJ IDEA won't resolve the
> project dependencies anymore ( in part, we're externalising properties
> and referring to them ala <verison>${foo.version}</version>.
> I've posted this as a query on the IntelliJ forums [1], but also
> thought that maybe this was a general problem with the Maven Embedder
> ( which I assume IntelliJ uses ).
> Does anyone know what part of the problem might be the right place to
> chase up a fix in? Maven or IntelliJ ( or, possibly my code even ).
>
> Cheers
> Mark
>
> [1]
> https://intellij-support.jetbrains.com/hc/en-us/community/posts/207603265-Importing-Maven-Projects-using-Lifecycle-Extensions
>
> --
> Mark Derricutt
> http://www.theoryinpractice.net
> http://www.chaliceofblood.net
> http://plus.google.com/+MarkDerricutt
> http://twitter.com/talios
> http://facebook.com/mderricutt
>
> Email had 1 attachment:
> * signature.asc 1k (application/pgp-signature)
