Description Alex Blewitt 2005-07-03 05:25:28 EDT

If you're creating a new project from an existing (non-Eclipse) source, such as CVS or a filesystem, why 
can't we scan for Java source packages automatically? We should be able to find them easily enough, 
since *.java files that are not under a source directory are almost useless anyway; and the package 
statement at the top of the Java Source file will tell you where the source directory/ies should be.

e.g. a/b/c/d/e.java with package statement 'package c.d' should have source folder a/b added

Other classpath entries, like .jar files, could also be handled in the same way.

This could be handled during a 'File Import' or 'CVS Import' into a new package. You could also have it 
as an option in existing Java Projects, like 'Update classpath' or similar.

This suggestion comes from interpreting a non-Eclipse viewers handle on how 'stupid' Eclipse is, just 
because he didn't know how to set the classpath:

http://www.javalobby.org/java/forums/m91837490.html