Steve said: > ----- Original Message ----- > From: "Nick Bauman" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, January 22, 2002 09:06 > Subject: Re: properties files aren't getting included > > >> Thanks for your help: >> >> > ----- Original Message ----- >> > From: "Nick Bauman" <[EMAIL PROTECTED]> >> > To: <[EMAIL PROTECTED]> >> > Sent: Tuesday, January 22, 2002 8:29 AM >> > Subject: properties files aren't getting included >> > >> > >> >> Am I just being stupid? I have some properties files in my project >> >> that ant seems to ignore when making a jar. I looked at the >> >> documentation and I searched the archives and couldn't find >> >> anything relevant on this subject. >> > >> > I assume you have the properties files next to the java source >> > right? >> >> Yes, it's in my src/ in a subpackage, right alongside my code. >> >> > And then you jar up the compiled classes in the build directory, >> > right? >> >> Yup. >> >> > If these two guesses are correct, how are you getting the properties >> > from the source dir to the build dir? >> >> I'm not. That's the problem, then. I need some kind of parameter to >> the "dist" task to keep the properties with the compiled classes. >> > -steve > > > I would add a copy task in the compile target which copies > **/*properties from src to build
Yes, I did that and that has solved the problem. Thanks. I added the entity to the "compile" target in my build.xml and it's now working fine. In particular, I added: <copy todir="${build}/org/foo/messages"> <fileset dir="${src}/org/foo/messages"> <patternset id="props" > <include name="**/*.properties"/> </patternset> </fileset> </copy> I guess I was making a stupid assumption that compiling would automatically do this for me. -- Nick Bauman Java Programmer. Available Cheap. Minneapolis area. Will Commute. Resume: http://www.cortexity.com/resume.html -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>