| eclipse and handling packages [message #287143] |
Fri, 24 June 2005 13:10 |
Eclipse User |
|
|
|
Originally posted by: tate.austin.usi.net
I have a bit of an odd question, I am trying to pull a poorly architected
old project into the eclipse environment. The principal hang up here is
that the file structure of this project does not correlate with the package
declarations. I have been told that I cannot changed the package
declaration (or the files at all really) so I can't simply change their
package declarations. In it's old environment and indeed in older java
setups, you could declare a java file to be in a package and have it sitting
in a directory with the understanding that when it was built into a .class
file it would be made be put in the appropriate package directory within the
Classes directory. An example: class X is declared as a member of package
com.filesinterface but resides in a director <projectdir>/Otherfiles/X.java
but when X.java is compiled it creates the file:
<projectdir>/Classes/com/filesinterface/X.class. This works in Versata(the
ide it was originally created in) but in eclipse it of course delivers the
error:
The declared package does not match the expected package X
Is there a way to insruct Eclipse to not try to correlate the physical file
structure with the package declaration?
|
|
|
Powered by
FUDForum. Page generated in 0.02905 seconds
Home