> -----Original Message----- > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > Sent: lundi 24 octobre 2005 04:01 > To: Maven Users List > Subject: RE: Where should configuration files go?
[snip] > We might want to align our notions: > > http://maven.apache.org/guides/introduction/introduction-to-the- > standard-directory-layout.html Ok, I hadn't noticed the introduction of src/main/config. > Are we going to make a distinction between resources like i18n files and > things like log4j.properties files or things like app server > configurations? I was planning on putting container configuration files in src/main/resources in order to reuse the resources tag and use the filtering mechanism in place. In the use case I'm working on, it'd be fine because I have a separate project for generate a container distribution. However I can see cases where you want to have both resources go in the artifact you're building and where you have config files that should remain outside of it. Thus I'd be all for having a separate config/ dir but we'd need to support it in the same way as we support resources in the pom (including filtering). > Just throwing this out for comment and clarification before we start > recommending things wholesale to users. Good point. [snip] -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
