Eclipse Community Forums: Eclipse Platform » Team work with Eclipse v2 and v3

Home » Eclipse Projects » Eclipse Platform » Team work with Eclipse v2 and v3

Team work with Eclipse v2 and v3 [message #223173]

Tue, 06 April 2004 17:15

Eclipse User

Originally posted by: news-reply-200404.iclipse.org

Hi,

I use Eclipse 3.0M8, my collegues use version 2. We use the CVS
support of Eclipse to access our Java project repository. When I try
to checkout the project from the repository, Eclipse does not treat it
as a Java project, and I cannot work on it. Is there an
incompatibility between v2 and v3 at that point?

Igor

--
Igor

the [i]clipse project
www.iclipse.org

Re: Team work with Eclipse v2 and v3 [message #223189 is a reply to message #223173]

Tue, 06 April 2004 17:33

Eclipse User

Originally posted by: smesh.openrules.com

Some requirements for Java project:
- '.classpath' file in project's root
- javanature and builder in '.project' file

Are they satisfied?

--
Sam Mesh - http://openrules.com

Re: Team work with Eclipse v2 and v3 [message #223237 is a reply to message #223173]

Tue, 06 April 2004 18:14

Eclipse User

Originally posted by: user.domain.invalid

Yeah, I had some difficulty here too. Try this way:
Goto the CVS repos perspective.
Pick your project.
From the pop-up, checkout-as
checkout w/ "New Project Wizard"
java->java project (the crucial step)

It is not a 2 vs 3 issue. We use 2 & 3 and Codeguide and who knows
whatelse here, without probs.

Igor Akkerman wrote:
> Hi,
>
> I use Eclipse 3.0M8, my collegues use version 2. We use the CVS
> support of Eclipse to access our Java project repository. When I try
> to checkout the project from the repository, Eclipse does not treat it
> as a Java project, and I cannot work on it. Is there an
> incompatibility between v2 and v3 at that point?
>
> Igor
>
> --
> Igor
>
> the [i]clipse project
> www.iclipse.org

Re: Team work with Eclipse v2 and v3 [message #223242 is a reply to message #223237]

Tue, 06 April 2004 18:36

Eclipse User

Originally posted by: smesh.openrules.com

Usually, we organize our CVS not in the CVS-module <-> Eclipse-project
way. It's not convenient to have either modules or projects as a
first-level entities. (what make first-level children so special?:) So,
we did not have mentioned here 2.X & 3.X problems yet.

--
Sam Mesh - http://openrules.com

Re: Team work with Eclipse v2 and v3 [message #223506 is a reply to message #223237]

Wed, 07 April 2004 08:11

Eclipse User

Originally posted by: news-reply-200403.iclipse.org

Thanks! That worked. I didn't try it that way.

Igor

exquisitus <user@domain.invalid> wrote:

>Yeah, I had some difficulty here too. Try this way:
>Goto the CVS repos perspective.
>Pick your project.
> From the pop-up, checkout-as
>checkout w/ "New Project Wizard"
>java->java project (the crucial step)
>
>It is not a 2 vs 3 issue. We use 2 & 3 and Codeguide and who knows
>whatelse here, without probs.
>
>Igor Akkerman wrote:
>> Hi,
>>
>> I use Eclipse 3.0M8, my collegues use version 2. We use the CVS
>> support of Eclipse to access our Java project repository. When I try
>> to checkout the project from the repository, Eclipse does not treat it
>> as a Java project, and I cannot work on it. Is there an
>> incompatibility between v2 and v3 at that point?
>>
>> Igor
>>
>> --
>> Igor
>>
>> the [i]clipse project
>> www.iclipse.org

Re: Team work with Eclipse v2 and v3 [message #223514 is a reply to message #223189]

Wed, 07 April 2004 08:12

Eclipse User

Originally posted by: news-reply-200403.iclipse.org

It seems that my checkout operation was wrong. It works now. Thank
you!

Igor

Sam Mesh <smesh@openrules.com> wrote:

>Some requirements for Java project:
>- '.classpath' file in project's root
>- javanature and builder in '.project' file
>
>Are they satisfied?

Previous Topic:	Disable finish button in multi-page wizard
Next Topic:	binary .jar files as plugin

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jun 07 17:08:04 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter