🚀 go-pugleaf

James A. Schulz <jaschulz@wiseware.com> wrote:
> Joi,

> Yes, it looks like this:

>     package com.davidflanagan.examples.i18n;

> I don't understand the function of this statement.  It looks like a path to
> me.  Can I change it to point to my src folder?

That's is the package namespace setting.  Java expects the
file's own path to reflect the package statement.  So, typically,
one would place the source file so:

jbproject/ThisExample/src/com/davidflanagan/examples/i18n/ThisExample.java

The JBuilder sourcepath setting must not change, it should still point 
at "jbproject/ThisExample/src", since that is the top of the source tree
and the package name space.

In this particular case you may be able to simply delete the package
statement and leave the file where it sits.  However, this is NOT a good
general strategy for importing 3rd party applications.  Whacking 
package statements can cause all sorts of namespace access issues.

By deleting the package statement, you're telling Java that all variables
in the java file belong to the "default" or "null" package.  The default
package is the very top of the source and class paths, ie "src" and "classes".
See http://java.sun.com/docs/books/tutorial/java/interpack/packages.html
for Sun's tutorial on packages.

-- 
Joi Ellis                    Software Engineer
Aravox Technologies          joi@aravox.com, gyles19@visi.com

No matter what we think of Linux versus FreeBSD, etc., the one thing I
really like about Linux is that it has Microsoft worried.  Anything
that kicks a monopoly in the pants has got to be good for something.
           - Chris Johnson