You are viewing a plain text version of this content. The canonical link for it is here.
Posted to m2-dev@maven.apache.org by Emmanuel Venisse <em...@venisse.net> on 2004/07/01 17:49:32 UTC

Re: cvscommit:maven-components/maven-core/src/test/resources/projects/base-directory-alignmentproject-which-needs-directory-alignment.xml

----- Original Message ----- 
From: "Jason van Zyl" <jv...@maven.org>
To: "Maven 2 Developers List" <m2...@maven.apache.org>
Sent: Thursday, July 01, 2004 5:24 PM
Subject: Re:
cvscommit:maven-components/maven-core/src/test/resources/projects/base-direc
tory-alignmentproject-which-needs-directory-alignment.xml


> On Thu, 2004-07-01 at 10:16, Jason van Zyl wrote:
>
> > Right, the maven.properties as I am saying it should be used is only for
> > users. Plugins, projects, groups and sites will strictly use the POM for
> > configuration and the inheritance mechanism will take care of the
> > cascading of values, namely properties defined in the POMs.
>
> What I mean by the notion of maven.properties replacing build.properties
> is that a maven.properties file could be found in the user's home
> directory somewhere or within the project. Same thing as we have in m1
> using build.properties.

Excellent, because a user can have a different property setting for
different project.

>
> -- 
> jvz.
>
> Jason van Zyl
> jason@maven.org
> http://maven.apache.org
>
> happiness is like a butterfly: the more you chase it, the more it will
> elude you, but if you turn your attention to other things, it will come
> and sit softly on your shoulder ...
>
>  -- Thoreau
>
>