That's pretty much the same as what I found. What did you do in
settings.xml? 

-----Original Message-----
From: Labanca, Rick [mailto:[EMAIL PROTECTED] 
Sent: 15 January 2008 15:32
To: Maven Users List
Subject: RE: Setting Java System property

> From: Simon Kitching [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 15, 2008 7:39 AM
> To: Maven Users List; Matthew Tordoff
> Subject: RE: Setting Java System property Setting properties in a pom 
> which are global to all stuff in the pom (and child poms) is trivial, 
> and definitely works when *not* nested within a <configuration> 
> element (as documented in the page I referred you to):
> 
> <project>
>  ...
>  <properties>
>    <foo>fooval</foo>
>  </properties>
> </project>
> 
> It also works in settings.xml, but you do need to be sure that the 
> profile it is defined within is active..

I wish this would work, from what I've tried the properties will not get
passed to child modules. The only way I can get a property to be seen by
all poms is to -Dparm=val or use settings.xml. 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




The content of this e-mail is confidential and may be privileged. It may be 
read, copied and used only by the intended recipient and may not be disclosed, 
copied or distributed. If you received this email in error, please contact the 
sender immediately by return e-mail or by telephoning +44 20 7260 2000, delete 
it and do not disclose its contents to any person. You should take full 
responsibility for checking this email for viruses. Markit reserves the right 
to monitor all e-mail communications through its network.
Markit and its affiliated companies make no warranty as to the accuracy or 
completeness of any information contained in this message and hereby exclude 
any liability of any kind for the information contained herein. Any opinions 
expressed in this message are those of the author and do not necessarily 
reflect the opinions of Markit.
For full details about Markit, its offerings and legal terms and conditions, 
please see Markit's website at http://www.markit.com <http://www.markit.com/> .

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to