You could try this: Package your config files into an artifact that gets deployed. Something like a zip. Then use dependency-maven-plugin to retreive the artifact and unpack it where you need it in the generate-sources phase. Viola now your config files are magically available when you need them, but you also have portable builds without cross references.
-----Original Message----- From: Michael Mattox [mailto:[EMAIL PROTECTED] Sent: Friday, February 24, 2006 7:10 AM To: continuum-users@maven.apache.org Subject: Re: Help - The working directory uses numbers instead of the project names "No, you don't have missed something. Actually, you can't choose the working directory. Why do you use some files from an other project? Thses files are included in generated artifact? Emmanuel" -- I'm talking about resource files. They're not included in the jars we produce. So we have this: <testResource> <directory>../config/src/main/config</directory> </testResource> for example to put our common config files in a single project. The other problem we have is the website: http://adclinux:9090/continuum/maven/working-directory/21/target/site/ You can see here 21 which should be "common". Since these change we can't bookmark the site. Isn't there a way to use the real project names instead of numbers? Honestly the numbers don't make any sense to me. We're trying symbolic links, not sure if that will work or not. -Michael
