On Sat, 2005-10-22 at 14:05 +0200, Vincent Massol wrote: > Hi Robert, > > > -----Original Message----- > > From: Robert Taylor [mailto:[EMAIL PROTECTED] > > Sent: samedi 22 octobre 2005 14:03 > > To: [email protected] > > Subject: Where should configuration files go? > > > > Greetings, > > > > I'm a recent Ant-to-Maven 2.0 convert and am trying to "mavenize" some > > existing greenfield projects. > > > > In the past I have usually kept my Hibernate *.hbm.xml files in the same > > directory as their corresponding .java files because it facilitates > > referencing. Should I still keep them there, or move them to the > > /resources directory? Personally, I'ld like to keep them close to their > > corresponding .java file. > > You should move them in the resources directory but you can keep the same > package. The notion of "close" is subjective. They can be in a different > directory and still be close in your IDE view for example. > > > For testing, should I place files like log4j.properties, > > *-applicationContext.xml (Spring) files, and other configuration type > > files under the /test/resources directory?
We might want to align our notions: http://maven.apache.org/guides/introduction/introduction-to-the- standard-directory-layout.html Are we going to make a distinction between resources like i18n files and things like log4j.properties files or things like app server configurations? Just throwing this out for comment and clarification before we start recommending things wholesale to users. > Exactly. Note that those files will need to be accessed using the classpath > as described on > http://maven.apache.org/guides/getting-started/index.html#How%20do%20add%20r > esources%20to%20my%20JAR? > > -Vincent > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
