ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 5613] New: - Compiler not catching misnamed package name
Date Fri, 28 Dec 2001 22:37:39 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5613>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5613

Compiler not catching misnamed package name

           Summary: Compiler not catching misnamed package name
           Product: Ant
           Version: 1.4.1
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Build Process
        AssignedTo: ant-dev@jakarta.apache.org
        ReportedBy: marksmithurbana@yahoo.com


Hi all,

Forgive me if this has been fixed since 1.4.1 but I couldn't find anything 
about this in bugzilla.

For some reason if I have a class with an inappropriate package name (that does 
not match it's directory structure), ant doesn't seem to catch any error from 
the compiler (i've tested on jikes 1.14 and Sun's javac 1.3.1 on win2k and 
jikes 1.15 and Sun's javac 1.3.1 on debain linux 2.2.19).  When not in ant, the 
compiler normally will spit out an error that the package name does not match 
the directory structure.  Ant does not give me an error, yet instead, compiles 
and places into my classes directory based upon the package name (instead of 
the directory structure).  I'm assuming this bug passed any lots of testing b/c 
in my particular case, it didn't break any of my import statements by luck 
since anything using my misnamed package name imported the full classpath to 
where it got incorrectly compiled, also.  I was not able to get any strange 
output in ant's verbose mode, either.

Regardless somehow ant 1.4.1 seems to not catch these standard compilation 
errors.  Has anyone else experienced this?  If not, please lemme know (i can 
duplicate this if someone wants into a simple project for testing.  i figure i 
owe the jakarta team that much after the sheer number of hours I've saved using 
a tool as cool as Ant!!).

Thanks,
Mark

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message