> Exactly, such a feature would be very handy. The one thing I suggested was, since properties are "first set wins", you could use: mvn -P profileB,profileA package and then set only the profileB-specific properties in profileB, and leave the common/shared properties in profileA.
This would result in "inheritance" of sorts, since anything not explicitly set in B would be set by A. But Farhan was hoping to just specify 1 profile in his mvn execution, and I don't disagree that it might be nice to see a more formal approach to profile inheritance in 2.1 or 3.0. I'm presently unaware of any specific plans in this direction though, and suggested he ask the list. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
