Hi Mark, This is by design. For simplicity, it is intended that profiles behave identically to inheritence, and inheritence doesn't merge resource sets. This may or may not be the right behaviour though - but we should discuss in that context rather than the profile.
- Brett On 9/14/05, Mark Hobson <[EMAIL PROTECTED]> wrote: > > Didn't want to file a bug if this was a conscious design decision, but > with the following POM: > > <project> > ... > <build> > <resources> > <resource>a</resource> > </resources> > </build> > <profiles> > <profile> > ... > <build> > <resources> > <resource>b</resource> > </resources> > </build> > ... > </profile> > </profiles> > ... > </project> > > Shouldn't the effective resources block consist of both 'a' and 'b' > when the profile is activated? Currently 'b' overrides 'a'. > > Cheers, > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
