Well - you can see your directory structure from your source code - and you should also be able to see the package/directory structure from within your IDE (whatever IDE you are using), so I'm not sure how seeing it in your class files actually helps you.
But what you are doing with adding an extra directory to the /cfclasses/ dir, is trying to tell Java that the class is in another package down, without actually declaring the package in the code (I think that made sense). So if you had /cfclasses/fred/myClass.class the myClass would be in package fred, and would be created by calling fred.myClass. Now in myClass you also have to declare that it is in package fred, otherwise it just won't work. Does that help? Mark On 7/8/05, Taco <[EMAIL PROTECTED]> wrote: > > You know how Packages and directory structures work? > > I *think* I do, but tell me what you were thinking of? > > > You are probably better off writing up your Java, and then putting it in a > JAR archive, and then dropping it into that folder. it's a fairly neat way > of doing things. > > Yeah a JAR archive is a nice way to package it up, but I (personally) prefer > to see the files in a directory structure sort of way, that way I can sort > of keep track of what classes are used where and which I need to refactor. > The .java files could eventually be all over the place, but your classes > directory is sort of the only place where you can make a bit of sense out of > it. What do reckon? > -- E: [EMAIL PROTECTED] W: www.compoundtheory.com ICQ: 3094740 --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
