Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
From: "KARR, DAVID" <dk068x@att.com>
To: Maven Users List <users@maven.apache.org>
Subject: store file in top parent pom, along with property pointing to it,
 and ref that property in child poms
Thread-Topic: store file in top parent pom, along with property pointing to
 it, and ref that property in child poms
Thread-Index: Ac37KD4pIZ+1EOYNTOuc/wp7Y+DSPw==
Date: Fri, 25 Jan 2013 18:31:08 +0000
Message-ID: 
 <B8D164BED956C5439875951895CB4B2210E57000@WABOTH9MSGUSR8C.ITServices.sbc.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

My project uses a small hierarchy of parent poms.  I believe it would be a =
good idea to set my Sonar connection settings in the top parent pom, instea=
d of telling all the users to add a certain set of settings to their ~/.m2/=
settings.xml.  In addition, we're using the "sonar.secretKeyPath" property,=
 along with a specific secret key file.  Continuing this strategy, it would=
 make sense to store that file in the top parent pom project and set the pr=
operty to refer to that file.

My problem is that I can't figure out how to set a path property that is re=
lative to the top parent, but when referenced from child poms it goes to th=
e correct place.  If I just use the obvious "${basedir}/sonar-secret.txt" t=
hat ends up being relative to the project referencing the property.

I don't want child projects to need to know how deep the pom hierarchy is, =
in case there was some way to do something like "parent.parent....".

I do think it's ok to specify a unique property that specifies where the "r=
oot" pom is, and reference things from that, but I can't figure out how to =
do something useful with that idea.  I tried defining that property ("root.=
parent", for instance) in the top pom and giving it a value like "${basedir=
}", and then having the additional property be "${root.parent}/sonar-secret=
.txt", but that doesn't fool it.  I really need a "statically-defined" prop=
erty that references "${basedir}", so when child poms reference it, it does=
n't evaluate it dynamically.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org