>>>>> "Tomasz Pik" <[EMAIL PROTECTED]>: > Configure plugins in profiles in parent pom and activate profiles in > child poms? This won't be automatic (I do not know if there's a way > to activate profile using packaging, maybe there's?) - you'll need > to add avtivation to child poms but should solve problem with > storing configuration in one place.
Yes, I was wondering about if profiles could be triggered by packaging, and if that was a way to go...? But I dread going this way, because my last incursion into profiles in 2.0.4 broke when 2.0.5 was released, and also breaks on the current 2.0.7... and has (along with another bug introduced with 2.0.5) stuck us on 2.0.4 (which is increasingly more of a problem). --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
