Re: Please reopen MNG-4533 Add an always active profile activator

Hi, I don't think that it is documented, but we should once we decide to have a clear separation between the build-pom and the consumer-pom. Now the same pom is used for different purposes. Also in general we advice to avoid profiles (it exposes some design flaws), so maybe better not talk

Re: Please reopen MNG-4533 Add an always active profile activator

Hi, yes, this is only about build time profiles. Including modules is only relevant during build time. And I assume the profile of a dependency cannot change the main project's target directory. So for this use case it's irrelevant whether the profiles would be active or not active during consume

Re: Please reopen MNG-4533 Add an always active profile activator

Hi, One other thing that comes to my mind: is this a build/site time profile or also a "consume"-time profile. With the latter I mean: should the profile have any effect when its artifact is used as a dependency? I think the answer is 'no', which means that the profile shouldn't always be

Re: Please reopen MNG-4533 Add an always active profile activator

Hi, it seems there are no more questions about the use case. So I'd like to return to my original request: Could issue MNG-4533 "Add an always active profile activator" please be reopened? https://issues.apache.org/jira/browse/MNG-4533 Best regards, Arend On Sun, Nov 15, 2015 at 1:44 PM,

Re: Please reopen MNG-4533 Add an always active profile activator

Hi Curtis, yes, using property activation is more or less the workaround described in MNG-4533. If I had to pick a workaround, I would prefer checking for the existence of pom.xml. This is guaranteed to always return true. So the only way to deactivate the profile would be to deactivate it

Re: Please reopen MNG-4533 Add an always active profile activator

On Sat, Nov 14, 2015 at 11:02 PM, Karl Heinz Marbaise wrote: > Hi, > > On 11/14/15 10:06 PM, Arend v. Reinersdorff wrote: > >> Hi Karl Heinz, >> >> good point. I'll try to elaborate more: >> >> The idea is to have a profile which is always active, unless explicitly >>

Re: Please reopen MNG-4533 Add an always active profile activator

Hi, On 11/14/15 2:03 PM, Arend v. Reinersdorff wrote: Hi, could issue MNG-4533 "Add an always active profile activator" please be reopened? https://issues.apache.org/jira/browse/MNG-4533 The issues was automatically closed in 2014. I find the current workarounds to create an always active

Please reopen MNG-4533 Add an always active profile activator

Hi, could issue MNG-4533 "Add an always active profile activator" please be reopened? https://issues.apache.org/jira/browse/MNG-4533 The issues was automatically closed in 2014. I find the current workarounds to create an always active profile (check for non existing property, check for always

Re: Please reopen MNG-4533 Add an always active profile activator

Hi, On 11/14/15 10:06 PM, Arend v. Reinersdorff wrote: Hi Karl Heinz, good point. I'll try to elaborate more: The idea is to have a profile which is always active, unless explicitly deactivated. One can nearly achieve this with true, but not quite because an activeByDefault profile is

Re: Please reopen MNG-4533 Add an always active profile activator

Hi Karl Heinz, good point. I'll try to elaborate more: The idea is to have a profile which is always active, unless explicitly deactivated. One can nearly achieve this with true, but not quite because an activeByDefault profile is deactivated if another profile from the same pom.xml is

Re: Please reopen MNG-4533 Add an always active profile activator

Hi Arend, > The idea is to have a profile which is always active, unless > explicitly deactivated. To achieve that use case, I like to activate based on a property value. Then you can change the property value from the CLI to deactivate it, without affecting any other profiles. This is more