Actually, I originally tried it without the includes. I only had them in this example because I was trying to be thorough. I have tried the includes on each set and every combination and always the same results. The ClassFileSet extends from FileSet and includes only *.class by default. So it probably was redundant, but in either case, I cannot get it to work.
Aaron -----Original Message----- From: Vilya Harvey [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 17, 2002 7:16 AM To: Ant Users List Subject: Re: Problem with ClassFileSet See inline comments below. Hope they help... Vil. ----- Original Message ----- From: "Aaron Kelley" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, December 17, 2002 2:09 AM Subject: Problem with ClassFileSet > I still cannot get the ClassFileSet to work. I am most likely doing > something incorrect. Here is how I am using it: > > <delete file="${cvs.package}.jar"/> > > <classfileset id="reqClasses" dir="/build/mylib/classes" > includes="**/*.class"> > <rootfileset dir="/build/myclient/classes" includes="**/*.class"/> > </classfileset> Don't use the includes attribute on the <classfileset> tag. This attribute, which I'm guessing is inherited from <fileset>, seems to take precedence over any nested specification of the files to include; that means you'll get exactly the files you specify in the attribute, without any dependencies. Is that the incorrect behaviour you're seeing? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
