Thanks for your reply. I want the properties to be available both at build time (e.g., to be used in packaging) and runtime (e.g., to be used to locate other resources that are relative to directory property values).
Tim -----Original Message----- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 19, 2007 9:36 AM To: Maven Users List Subject: Re: Determining top-level parent pom directory On 9/18/07, Tim Foster <[EMAIL PROTECTED]> wrote: > Okay. I'm trying to dynamically create a properties file, e.g., > my.properties, into which I can define properties that can be referenced > at all levels of the hierarchy. This file would live in a location > relative to the top-level pom file. The default definitions of the > properties are determined by reading a default.properties file, but the > values can be overridden by environment variables. So, I'm using the > maven-antrun-plugin to create this properties file, but I don't know how > to reference it from the lower-level poms. Is this properties file a build-time thing, or something that you need to package up to deliver with your project? IOW, what problem are you trying to solve? You're still describing an implementation. -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
