[news.eclipse.technology] Re: Eclipse just seems wrong

["Bob Hays, Computer Geek" <purplehayz@xxxxxxxxxxxxx>]

On 9/10/03 12:07 AM, in article bjmbgt$m7p$2@xxxxxxxxxxx, "Gregg Wonderly"
<gergg@xxxxxxx> wrote:

> I tried to take one of my 800 source file projects, and build it in eclipse.
> I used my KAWA configuration to specify all of the needed jars to build
> against.  But,
> it appears that since my .java files do not mirror the package structure,
> that the compiler (I guess eclipse uses its own compiler [which will
> guarantee compile time portability issues to other IDEs, sigh]) can not find
> the classes with the expected package names (is it ignoring my package
> statements...), and thus I get 5000 error messages about classes not
> found...sigh...

The Java spec says that the directory structure and package structures are
mirrors of each other - if you're using package statements that don't match
the file structure then you're asking for problems when porting to other
Java compilers, not just IDEs.

> What is the deal with simplicity?  I've always used "javac -d ???" to
> compile my class files into an appropriate directory where I like to keep
> all my build output so that I can copy it to other machines when I need to
> bring up a new build environment.  Apparently everyone has gone around
> compiling without -d and thus thinks you must put your source files into
> package directory structures.

When you create a project in Eclipse, you can select an output directory -
its on the last wizard screen and also available under the build section of
the Properties pages for the project (once its created).  The item is the
last item on the Source tab of that page.  I use it both to separate
binaries from source and to make it easier to make jar files when I need to.

Hope that helps.  Have fun! - Bob

-- 
Bob Hays, Computer Geek
http://www.alephnaught.com

"The difference between a craftsman and an artist is, after all, in the
mind, not the hands."
-- Bob Lewis