On Tue, Nov 20, 2018 at 2:30 AM Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > 1. you have to use lib/ext folder and not extensions.xml cause it is loaded > too late
Unfortunately, that's a deal breaker. Using Maven's lib/ext is the original situation I reported when I started this thread (i.e., it worked from Maven's lib/ext, but not from the project's .mvn/extensions.xml.) There's no way I can get the developers of the software I'm planning to use this in to install the extension in Maven's lib/ext; it has to be able to work from the project's .mvn/extensions.xml. I guess this is the end of the road, then. Bummer. > 2. you have to override the property activator as you mentionned cause > otherwise your profile is added (through plexus) in the list of activator, > set the activation to true and then property one sets it to false > > To do 2 you just have to use sisu @Priority and ensure the hint is property: I tried adding the Priority annotation, and it works from Maven's lib/ext, but it also works *without* it, so I'm hesitant to add it unless I know it's really necessary. The readme file in Maven's lib/ext says Use this directory to contribute 3rd-party extensions to the Maven core. These extensions can either extend or override Maven's default implementation. Do I really need the Priority annotation, or will my extension's AdvancedProfileActivator (annotated with '@Component(role = ProfileActivator.class, hint = "property")') always take precedence over the default by virtue of being in Maven's lib/ext? Thank you! Lewis --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
