Skip to main content



      Home
Home » Language IDEs » Java Development Tools (JDT) » CVS checkout of non-Eclipse project gives broken tree
CVS checkout of non-Eclipse project gives broken tree [message #51872] Fri, 06 June 2003 12:33 Go to next message
Eclipse UserFriend
Originally posted by: junkmail.stevello.free-online.co.uk

Hi all

I'm trying to checkout a large existing java project as a new Eclipse
project. Since there is no .project file in the module root, Eclipse
doesn't recognise it as a Java project by default, so I've tried checking
out into an existing Java project and also copying a .project file into
the root of the plain project created by Checkout as Project, as well as
importing a commandline cvs checkout from the filesystem into a new
project.

In both cases the result is that every subdirectory of the project appears
as an individual package in Eclipse's java perspective instead of part of
a nice foldable tree, and most of the JDT functions (java-aware searching,
compiling etc) do not work.

Does anyone know what I'm doing wrong here? Eclipse seems like a great
tool for developing from scratch but I am not having any luck contributing
to an existing piece of software held in CVS.

Thanks in advance

Will Stephenson
Re: CVS checkout of non-Eclipse project gives broken tree [message #51897 is a reply to message #51872] Fri, 06 June 2003 12:59 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: wegener.cboenospam.com

Will Stephenson wrote:

> Hi all

> I'm trying to checkout a large existing java project as a new Eclipse
> project. Since there is no .project file in the module root, Eclipse
> doesn't recognise it as a Java project by default, so I've tried checking
> out into an existing Java project and also copying a .project file into
> the root of the plain project created by Checkout as Project, as well as
> importing a commandline cvs checkout from the filesystem into a new
> project.

> In both cases the result is that every subdirectory of the project appears
> as an individual package in Eclipse's java perspective instead of part of
> a nice foldable tree,

Select the little black triangle pointing down on the package explorer
view and selecting Layout->Hierarchial will produce a tree structure.

> and most of the JDT functions (java-aware searching,
> compiling etc) do not work.

What behaviour/errors are you seeing with the JDT functions.

> Does anyone know what I'm doing wrong here? Eclipse seems like a great
> tool for developing from scratch but I am not having any luck contributing
> to an existing piece of software held in CVS.

> Thanks in advance

> Will Stephenson
Re: CVS checkout of non-Eclipse project gives broken tree [message #51923 is a reply to message #51872] Fri, 06 June 2003 14:19 Go to previous message
Eclipse UserFriend
Originally posted by: richkulp.NOSPAM.us.ibm.com

When you check it out, do "Checkout As..." and select java project. It
will now be a valid java project. Checking into an existing java project
or putting the .project file by hand will work, but it is open to
errors. Better to let it create the project properly.

Though if the source is not directly under the root of the project, you
will still get compile errors because it doesn't know exactly where the
source is. In those cases after you check it out, you need to open the
properties on the project, goto java build path, and on the source page,
do "Add Folder..." to add the source folders containing your source to
the build path (a source folder is the directory just below the
directory of first fragment of your package, i.e. if your structure is

xyz/com/ibm/somefile.java

and somefile.java is in package com.ibm, then the source folder is "xyz".)

NOTE: VERY IMPORTANT - When you do the above, make sure, BEFORE you
check things back in, that you click on the bin directory (or whatever
directory(s) you told it to put the output into), bring up the popup
menu and do Team->Add to .cvsignore. If you don't do this, these
directories will be checked back into CVS, and they really shouldn't be
because they are build output directories. Once checked in you can't get
rid of them.

Also, then check back into CVS the .classpath, .project, and .cvsignore
files. This will make anyone else that wants to check out from CVS have
a smooth checkout.

Rich
Previous Topic:Listening to classpath changes
Next Topic:Unusual problem with Eclipse and the Tomcat plugin
Goto Forum:
  


Current Time: Fri May 09 10:49:31 EDT 2025

Powered by FUDForum. Page generated in 0.03523 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top