You could turn this single file into its own module and deploy etc it on its own in a jar file. Then use remote-resources plugin or assembly:unpack or a similar approach to bring that file into each submodule as needed.
You generally should not expect that a Maven build of a module necessarily has all of the parents and other modules in the filesystem available. So simply stating ../../../main/resources/file.properties (as an example) as the location of the file is going to be a bad idea in the long run. Instead you should create builds that are generally independent (except for their dependencies). Wayne On 9/19/07, Wendy Smoak <[EMAIL PROTECTED]> wrote: > On 9/19/07, Tim Foster <[EMAIL PROTECTED]> wrote: > > > 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). > > I still don't have the full picture of what you need. In general, > finding the "top" of the project is problematic-- there's no guarantee > the entire project is sitting on disk, ideally the build should work > if you check out a portion of it, by retrieving snapshots of the other > modules from a repository. > > Seems like you need to generate the .properties file and then get it > on the classpath, rather than worry about exactly where to find it. > One way to do that is to put the .properties file in a jar that is > then depended on by other modules. > > -- > 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]
