| Using eclipse with an existing (complex) project [message #60157] |
Wed, 18 June 2003 06:27  |
Eclipse User |
|
|
|
Originally posted by: james.dontspamme.mosaicsoftware.com
Hi,
I\'ve browsed this group and there have been a number of posts that focus
on similar problems to those I\'ve run into. Some of them have helped a
little in my understanding of how Eclipse manages project directory
structures, and I\'m starting to despair that what I want to do is not
possible (or is going to be just plain painful).
But before I give up I thought I\'d pose this to the group:
We have an existing project consisting of about 1,800 Java files. The
existing directory structure is pretty awful but we inherited it. I\'d
prefer not to change it since we throw away a lot of history for much of
the source code (again, an inherited source control system) and it means
moving a large group of developers over to a new directory structure.
What it boils down to is, a. is it possible, and b. if so what\'s the best
way to point eclipse at the following directory structure (given the
constraints below) and create a new project?
all classes live in sub-packages of foo (so foo.*, foo.bar.*,
foo.bar.blue.*)
base
+--- src
| +--- foo
| +--- other1
|
+--- build
| +--- classes
| +--- other3
|
+--- other4
I want the eclipse project to either live in the src directory, or live in
the base directory but ignore pretty much everything under it except the
contents of base\\src\\foo.
I want to build class files into base\\build\\classes\\foo\\... (as per
the packaging).
This is complicated by the fact that I need eclipse to pick up classes in
a separate directory in a completely unrelated location on the file system
and use a completely different compiler and JVM (initially). In this case
c:\\winnt\\java\\classes, we\'re still on Microsoft\'s compiler/JVM.
We\'re in the process of migrating but we inherited a large amount of
legacy code tied to Microsoft\'s J/Direct technology. Part of that process
involves moving off Visual J++ onto a new IDE. Eclipse gets my vote, _if_
we can get this step right.
I\'ve fought with eclipse a number of times to try to get this right. In
most cases I\'ve lost on the following fronts:
1. It won\'t let me reference class directories below the project folder
(C:\\winnt\\java\\classes)
2. It seems to include everything in the directories under the project
folder (we have a lot of extraneous files that aren\'t related directly to
the Java portion of the project).
3. When I create the projects initially eclipse takes a hell of a long
time to startup before it comes back to me. On one occasion I forcibly
terminated the process when I noticed it was replicating the entire
base\\build directory\'s contents under base\\build\\classes\\build\\...
(I\'d set the build directory to build\\classes and the project files were
in base).
Any help suggestions (pointers to articles, I\'ve read the various FAQS
which were moderately helpful) would be most welcome.
Thanks in advance.
James Greenfield
|
|
|
|
|
|
|
|
|
|
| Re: Using eclipse with an existing (complex) project [message #66564 is a reply to message #61314] |
Wed, 25 June 2003 00:54  |
| Eclipse User |
|
|
|
Originally posted by: radzloco.yahoo.com
Dave,
The solution that you provided almost works for me. I have to add a
module to an existing project. I do not want to include anything else in
my build path but the new module will use existing modules so I want them
in my classpath.
The structure I have :
java
allModules
existingModule1
existingModule2
myNewModule
Whenever I add myNewModule folder all files inside it are assumed to fall
into "default" package, whereas they are in allModules.myNewModule. I
tried unchecking the default directory while creating the project and
browsing to the "java" folder and then adding allModules/myNewModule as
Source folder, but did not work. I also tried creating with default folder
and then adding the folder by Add Folder->Advanced and Link Folder.
Anywhere I am going wrong ?
Thanks.
Radz
Dave Wegener wrote:
> James Greenfield wrote:
> > Dave Wegener wrote:
> > > Randy Faust wrote:
> > > > Create a project named base. Create a Java source folder named
> \\\"src\\\"
> > inside
> > > > base. Move foo and all subdirectories into base.
> > > I believe that he means copy foo and all subdirectories into src.
> > > > Copy the remaining non
> > > > source directories into base. In the project properties, go to Java
Build
> > > > Path, Source tab and set the exclusion filter for your \\\"src\\\"
source
> > folder
> > > > to contain everything that isn\\\'t foo.
> > These both seem to imply that I\\\'m _required_ to match my directory
> > structure to that expected by Eclipse, which is exactly what I\\\'m trying
> > to avoid. We can\\\'t really afford to remodel our directory structure
> > (much as I\\\'d like to).
> > > As an alternative to coping the entire directory hierarchy, you can
> > > uncheck the Use default location item when creating the project and then
> > > point at base. You want to define src as a source folder when creating
> > > the project. Click on the Add Folder button when on the New Java Project
> > > Source tab. You can use the build/classes directory for output by using
> > > the Browse button for the Default Output Folder field on the same tab.
> > This I\\\'ve managed, but once I go this route I can\\\'t seem to include
> > the classes in c:\\\\winnt\\\\java\\\\classes (the idea of an external jar
> > file has occurred to me but I\\\'d like to avoid it if possible since
> > patches to the MS JVM include patches to these classes which means
> > managing updates across our entire group of dev teams, in four countries
> > :-P).
> In that case, You should be able to use a linked folder to accomplish
> this. Set the project up with src defined as a source folder. Go to the
> Project Properties and select Java Build Path. Select Libraries tab and
> Add Class Folder. Select Create Folder and then click on the Advanced
> button. Give the folder a name and select Link to folder in filesystem
> and browse to winnt\java\. Select classes. This will create a link to
> the folder in base. The classes in the directory will now be in your
> classpath.
> > But thanks for the info, I\\\'ll go play (nice :-)) some more and see what
> > I can get done.
> > James
|
|
|
Powered by
FUDForum. Page generated in 0.02769 seconds
Home