eclipse CVS and intellisense

[asd]

hi all,

I am accessing code using Eclipse CVS client from a CVS host.

When I checkout the project from CVS repository to my local machine, I
am not able to use some of the features of the eclipse IDE like code
complition, intellisense, etc.

Where as if I create a new project on my local machine I am able to use
these salient features of the IDE.

What do I need to do so that I can use these features with CVS?

Please guide me.

Thanks in advance for any help.

regards,

Asd

 

[Roland]

hi all,

I am accessing code using Eclipse CVS client from a CVS host.

When I checkout the project from CVS repository to my local machine, I
am not able to use some of the features of the eclipse IDE like code
complition, intellisense, etc.

Where as if I create a new project on my local machine I am able to use
these salient features of the IDE.

What do I need to do so that I can use these features with CVS?

Please guide me.

Thanks in advance for any help.

regards,

Asd

Verify if you haven't checked out the files as read-only. If you can
edit these files (if you can type something in the editor), then they
are writable (i.e. not read-only) and I don't know what's causing
Eclipse's features not to work. :-(
--
Regards,

Roland de Ruiter
___ ___
/__/ w_/ /__/
/ \ /_/ / \

 

[asd]

Thank you for your reply.

The files are not read-only. I can very well edit them and commit them
back to CVS.

But I dont get the code complition support like I type "Str" and press
Ctrl+space to complete it as java.lang.String, it doesnt work.

I cant add method header or class headers by doing alt+shift+j.

For both the cases above I get the following message displayed in a
dialog box:

"This compilation unit is not on the build path of a java project."

With a standalone project (I mean without using CVS), the code is
compiled every time the file is saved. But this doesnt happen when the
code is from CVS.

If these features dont work then it is as good as using any normal text
editor :-(

Any help will be highly appreciated.

regards,

Asd

 

[Christian Gudrian]

Am 10 May 2005 03:45:42 -0700 schrieb asd:

"This compilation unit is not on the build path of a java project."

Well, you could've told us about that in your first post. Check your
project settings to make sure, that the compilation unit (your source file)
is on the build path of the java project.

Christian

 

[Owen Jacobson]

Am 10 May 2005 03:45:42 -0700 schrieb asd:


Well, you could've told us about that in your first post. Check your
project settings to make sure, that the compilation unit (your source
file) is on the build path of the java project.

Also ensure that the project *is* a Java project and not just a Project --
Eclipse treats them slightly differently. I'm unsure of the incantations
required to turn a normal project into a Java project; however, when
checking out the code, there's a relevant menu option labelled 'Check
Out...' (rather than Check Out As Project).

Owen