| Source directory structure... help needed! [message #582504] |
Tue, 17 September 2002 18:46 |
 Macon Pegram
Messages: 1
Registered: July 2009 |
Junior Member |
|
|
I\'m a huge fan of Eclipse, and have been using it for awhile. I\'ve
recently joined a project at work which has been around for quite awhile.
They have expressed an interest in using Eclipse as their IDE, but we\'re
running into one glitch.
Source code is currently arranged in the project as follows:
foo\\source - Base directory for source
foo\\source\\com - The beginning a bunch of packages (com.xxx.xxx.)
foo\\source\\batch - More code which is NOT in a \"batch.xxx\"
package structure
Now I\'ll be the first to admit this, isn\'t the best way to organize
one\'s code, but it\'s what I have to deal with and I don\'t have the
option to change this structure at this time. We\'re doing our
development under WIN NT 4 (so the previous suggestions in the message
board of using the W2K tool Junction to create links will not work for
us).
When I setup the project to use \'foo\\source\\batch\' as the base
directory for source, I can deal with the code in that directory just
fine, but this prevents me from pointing the project to \'foo\\source\' as
an additional source directory since \'batch\' is nested within
\'foo\\source\', so I can\'t work on the code in the \'foo\\source\\com\'
directory.
If I try to do the reverse, where I tell Eclipse that \'foo\\source\' is
my source directory, Eclipse has a fit on compilation because it wants to
compile all the java code in the \'foo\\source\\batch\' directory as if it
was in a \'batch.xxx\' package.
Are there any work arounds anyone can suggest? This is the only real
reason we can\'t use Eclipse on this project. Aside from this one issue
Eclipse would be a MUCH better tool than any of the others currently being
used on the project.
As I see it there\'s two possible solutions (but I don\'t know how to
implement either one):
- 1. Define \'foo\\source\\batch\' and \'foo\\source\' as source
directories (with the corresponding package mapping relative to these
directories). This seems pretty unlikely given the way Eclipse does
things.
- 2. Is there some way to get Eclipse to ignore compilation in the
\'foo\\source\\batch\' directory when I define \'foo\\source\' as my
project\'s source directory? I know you can FILTER seeing
\'foo\\source\\batch\', but I want to be able to actually have Eclipse
FILTER compilation of this directory. That would allow me to set up a
seperate Eclipse project to deal with the contents of the
\'foo\\source\\batch\' tree. (Which would be a perfectly acceptable
solution for my needs).
Any help would be TREMENDOUSLY appreciated.
Thanks!
Macon Pegram
|
|
|
Powered by
FUDForum. Page generated in 0.05069 seconds
] 
Search
Help
Register
Login
Home
