Build directory contains:
F:\dev\A(class).java
F:\dev\B(class).java
( a rather long listing - truncated for posting )
With no classpath specified on the command line compiler says:
F:\dev\A.java:35: cannot find symbol
symbol: class B
public class A extends B copiously spewing out just about my entire build directory. All of the files for my entire project have ( in the re-design ) been cleaned of any package declarations and placed in the same folder. I ran the main() using a tool that I had used for a long time. I believe I also opened a cli window and tried it, from memory this is where I got the code snippet posted in the original post in this
thread.
adding
"F:\dev" to classpath using control panel gets rid of a lot of errors but now a critically needed library ( jar file in extensions directory ) is no longer visible resulting in
F:\dev\M.java:114: cannot find symbol : class BoyerMooreHorspoolRaita (This extension is someting I cannot do without).
removing F:\dev from environment variables using control panel and placing it on the command line gets the same compiler error, the extensions are no longer available. My classpath using the control panel to set envirionment variables is now 167 characters long just from a
temporary workaround to so that the current re-design of the entire project does not make my work idempotent. To accomplish this, I moved the re-write to a thumb-drive.
The following code compiles on hard disk:
With the F:\dev left in the command line classpath switch.
BoyerMooreHorspoolRaita is a powerful tool I got from investing a lot of work in my project, I can ( if I absolutely have to ) copy parts of the work to conventional disk and do modular development while I read about 2,300 pages of books I bought and work on this question. My goal is to be able to transport a complete build with source code on thumb-drive, as built, to the Team-Lead's machine or ftp to a Tier-1 server after I generate
md5deep
on the directory structure where a release is working and tested. I would then run a utility ( written as part of the project ) to provide an ECDLP public key on the Team-Lead's machine for work to proceed. The JavaOne 2003 conference provided hope for ECDLP being implemented, I do not have to use Elliptic Curve, RSA PublicKey is totally sufficient, but the need to do this using publicly studied tool suites is something that is hammered again and again in the many books I have read.
The reasons why I need this are well beyond the scope of a beginner area. I have collected dozens of powerful jar files and have begun to use them copiously now that my Java skills have improved. Java has become very popular in the undergraduate computer science lab, their work is saving my project.
[ February 17, 2008: Message edited by: Nicholas Jordan ]