Ahmed Ounaissa wrote:
You do have to for the ant task as it uses the relative directory structure to figure out which files haveThx to all for your answers.
If summarize:
1. I do not have to respect the package structure for my sources (is this compliant to Java Spec ?).
been compiled, however ant does not have the code to inspect the java source files to see if the
package names are what is expected,
2. If -d is supplied to the compiler (javac) it disregards possible mismatches between package class statement and compilation unit location. (source location is supplied in the ant xml build file).
Side question: Loading same sources in Eclipse raises the error.
Thx /Ahmed
-----Original Message----- From: Stefan Bodewig [mailto:[EMAIL PROTECTED] Sent: mercredi 16 f�vrier 2005 12:51 To: [email protected] Subject: Re: Error not detected in ANT 1.6.1 compile task
On Wed, 16 Feb 2005, Peter Reilly <[EMAIL PROTECTED]> wrote:
To clarify,
this is normal commandline and ant task javac behaviour.
Even more than that.
I once worked on a(n open source) project[1] that kept all source files in the same directory, even though they belonged to different Java packages. They wanted it to be that way ("I won't let the programming language tell me how I structure my workspace").
Stefan
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
