After reading about the pitfalls and spotty implementation of pseudo-inheritance of profiles, I can report that it appears that for a profile defined in a parent pom you can activate it from a child as long as the child doesn't try to activate it using a property value.
So a profile defined in a parent pom that is defined to be active when a file exists and when a property is true will never be activated by a child, because the child--or the command line--can never fulfill the property condition. I find this to be counterintuitive and weird. Is this a bug, or by some kind of design that I'm not smart enough to comprehend? :-) Best, Laird
