Eclipse Community Forums: Eclipse Platform

Home » Eclipse Projects » Eclipse Platform » cvs check out as project

cvs check out as project [message #160263]

Fri, 21 November 2003 14:29

Eclipse User

Originally posted by: bob.donovan.eds.com

Some of my users are using eclipse to checkin my custom project
directories to a cvs repository. When the use the cvs "Check out as
Project" to bring the project to another machine, the project is missing
properties that were set using the properties extension.

How is this supposed to be properly handled? I think properties are stored
down in the .metadata directory which is not pushed into cvs. Are we
supposed to store the properties somewhere else?

Or are we supposed to override and popup a dialog on "Check out" and ask
for the properties to be filled out?

Anyone have this problem?

Bob

Re: cvs check out as project [message #160357 is a reply to message #160263]

Fri, 21 November 2003 17:19

Eclipse User

Originally posted by: richkulp.NO.SPAM.us.ibm.com

It depends on which properties. Properties such as the classpath are
stored in the .classpath file, which should also be checked in. Other
properties are workspace specific and are not exported through CVS.

(Note: The .project file should also be checked into CVS).

--
Thanks, Rich Kulp

Re: cvs check out as project [message #160398 is a reply to message #160357]

Fri, 21 November 2003 18:26

Eclipse User

Originally posted by: bob.donovan.eds.com

Rich,

I am using the org.eclipse.ui.propertyPages extension point.

I am storing things that are important to making the project work
correctly. I retrieve the properties via the
IResource.getPersistenProperty() api (see below).

String sCustomDir = ((IResource) getElement()).getPersistentProperty(
new QualifiedName("",
ServerUIPluginConstants.PROJECT_CUSTOMDIR_PROPERTY));

Does this mean that I need to find some other way of storing properties
that go with my project?

Bob

Rich Kulp wrote:

> It depends on which properties. Properties such as the classpath are
> stored in the .classpath file, which should also be checked in. Other
> properties are workspace specific and are not exported through CVS.

> (Note: The .project file should also be checked into CVS).

Re: cvs check out as project [message #160951 is a reply to message #160398]

Mon, 24 November 2003 09:35

Eclipse User

Originally posted by: Michael_Valenta.oti.com

Bob,

One of the planned items for 3.0 is improved user settings support. The
plan item is still being fleshed out but one of the aspects being
investigated is support of persistable project/resource properties.
However, in the mean time (or if this doesn't make it into the user
settings support), you will need to use your own mechanism to persist
your project meta-data in the project (in a similar manner to the
..classpath file).

Michael

Bob Donovan wrote:

> Rich,
>
> I am using the org.eclipse.ui.propertyPages extension point.
>
> I am storing things that are important to making the project work
> correctly. I retrieve the properties via the
> IResource.getPersistenProperty() api (see below).
>
> String sCustomDir = ((IResource) getElement()).getPersistentProperty(
> new QualifiedName("",
> ServerUIPluginConstants.PROJECT_CUSTOMDIR_PROPERTY));
>
> Does this mean that I need to find some other way of storing properties
> that go with my project?
>
> Bob
>
> Rich Kulp wrote:
>
>
>>It depends on which properties. Properties such as the classpath are
>>stored in the .classpath file, which should also be checked in. Other
>>properties are workspace specific and are not exported through CVS.
>>
>
>>(Note: The .project file should also be checked into CVS).
>>
>
>
>

Previous Topic:	CVS problems
Next Topic:	CVS commit an IFile

Goto Forum:

-=] Back to Top [=-

Current Time: Thu Sep 18 18:18:22 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter