-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
My vote is for #1, for the following reasons:
I think it's really more important to consider the use cases of
profiles, rather than the simplicity of describing their use. Profiles
are supposed to be modifications per environment (whether that be sou
Kenney Westerhof wrote:
>Hm.. I meant to say: profiles are inherited AND merged (inheritance has
>to either replace values (override) or merge them), whereas I think the
>build information is project local and should not be merged, but possibly
>only used for specifying defaults.
>
>
Right, so w
On Mon, 19 Sep 2005, Brett Porter wrote:
> Kenney Westerhof wrote:
>
> Maven is about encouraging patterns, but not necessarily our patterns.
> Hopefully people will use the defaults for simplicity, but if a company
> standard is in force that should be easy too.
Ofcourse, I totally agree. But no
Kenney Westerhof wrote:
>Resource inheritance from a normal pom seems useless to me since the
>paths are totally different (other project).
>
Right, that's what I was getting at too.
>Specifying default
>directories for an entire project tree (for users that don't conform to
>the maven2 director
On Mon, 19 Sep 2005, Brett Porter wrote:
> Hi,
>
> Some opinions needed. Currently we have a problem in: MNG-895 (cannot
> add resources to a profile).
>
> Basically, profiles operate identically to inheritence, and so resources
> are not merged through inheritence, but if they do exist in the par
Hi,
Some opinions needed. Currently we have a problem in: MNG-895 (cannot
add resources to a profile).
Basically, profiles operate identically to inheritence, and so resources
are not merged through inheritence, but if they do exist in the parent
they are inherited (eg src/main/resources from the
