Eclipse Community Forums: Java Development Tools (JDT) » sharing java projects among 3.3 and 3.4 workspaces

Home

Home » Language IDEs » Java Development Tools (JDT) » sharing java projects among 3.3 and 3.4 workspaces

sharing java projects among 3.3 and 3.4 workspaces [message #256361]

Sat, 13 September 2008 08:39

Eclipse User

Hi,

will sharing a java project (via svn) between 3.3 and 3.4 workspaces
cause problems?

Thanks,
Felix

Re: sharing java projects among 3.3 and 3.4 workspaces [message #256367 is a reply to message #256361]

Sun, 14 September 2008 10:20

Eclipse User

Felix Dorner wrote:
> Hi,
>
> will sharing a java project (via svn) between 3.3 and 3.4 workspaces
> cause problems?
>
Yes. Moving forward is supported i.e. you can start a 3.3 workspace with
3.4 but if you start a 3.4 workspace with 3.3 unexpected things can
happen and hence that scenario is not supported.

Dani
> Thanks,
> Felix
>

Re: sharing java projects among 3.3 and 3.4 workspaces [message #256374 is a reply to message #256367]

Mon, 15 September 2008 01:02

Eclipse User

"Daniel Megert" <daniel_megert@ch.ibm.com> wrote in message
news:gaj6ih$tq0$1@build.eclipse.org...
> Felix Dorner wrote:
>> Hi,
>>
>> will sharing a java project (via svn) between 3.3 and 3.4 workspaces
>> cause problems?
> Yes. Moving forward is supported i.e. you can start a 3.3 workspace with
> 3.4 but if you start a 3.4 workspace with 3.3 unexpected things can happen
> and hence that scenario is not supported.

You can probably get away with it, depending on what features you use - it's
not _supported_, as Dani said, but that doesn't mean it won't work. You
might want to back up your workspace and then give it a try and see what
happens.

Re: sharing java projects among 3.3 and 3.4 workspaces [message #256377 is a reply to message #256374]

Mon, 15 September 2008 03:40

Eclipse User

Walter Harley wrote:
> "Daniel Megert" <daniel_megert@ch.ibm.com> wrote in message
> news:gaj6ih$tq0$1@build.eclipse.org...
>
>> Felix Dorner wrote:
>>
>>> Hi,
>>>
>>> will sharing a java project (via svn) between 3.3 and 3.4 workspaces
>>> cause problems?
>>>
>> Yes. Moving forward is supported i.e. you can start a 3.3 workspace with
>> 3.4 but if you start a 3.4 workspace with 3.3 unexpected things can happen
>> and hence that scenario is not supported.
>>
>
>
> You can probably get away with it, depending on what features you use - it's
> not _supported_, as Dani said, but that doesn't mean it won't work.
Well, it's not just "not supported": there are many things that change
or are new with a new release. You will get exceptions e.g. if you have
a new view open and then start with an older version and you might loose
all the settings made in that view. Now, sure, if you only use the
simplest features it might work.

If you really have to start with an older version (e.g. because a
plug-in doesn't run anymore on 3.4 - which shouldn't happen) from time
to time, why not use a different workspace and share the code via
repository?

Dani
> You
> might want to back up your workspace and then give it a try and see what
> happens.
>
>
>

Re: sharing java projects among 3.3 and 3.4 workspaces [message #256386 is a reply to message #256361]

Mon, 15 September 2008 08:32

Eclipse User

Originally posted by: eclipse-news.rizzoweb.com

Felix Dorner wrote:
> Hi,
>
> will sharing a java project (via svn) between 3.3 and 3.4 workspaces
> cause problems?

I've been doing it on a daily basis since at least 3.4M5 (maybe even
earlier). It works pretty flawlessly other than a few small specific
things that I am careful NOT to check in. In my situation, I'm the only
team member using 3.4 and our we are building plugins/features and an
RCP product. For example, the launch shared configuration files get
touched by 3.4 in a way that caused them not to work in 3.3, so I just
make sure not to check them in. I don't remember the details, but there
were a couple of other small differences (in stuff like the .product or
..target file contents, I don't remember exactly) that I have to also
ignore (not check in).

Hope this helps,
Eric

Re: sharing java projects among 3.3 and 3.4 workspaces [message #256412 is a reply to message #256377]

Mon, 15 September 2008 16:02

Eclipse User

Hi Daniel,

maybe I was misunderstood. What I am sharing in my repositories are java
projects, not entire workspaces. Each client has its own (version
specific) workspace. Still there is some metadata inside a project:

- the custom builders
- the .classpath and .project files

The question is whether these files are properly interpreted by 3.3 and
3.4 clients

Felix

> If you really have to start with an older version (e.g. because a
> plug-in doesn't run anymore on 3.4 - which shouldn't happen) from time
> to time, why not use a different workspace and share the code via
> repository?

Re: sharing java projects among 3.3 and 3.4 workspaces [message #256425 is a reply to message #256412]

Tue, 16 September 2008 03:26

Eclipse User

Felix Dorner wrote:
> Hi Daniel,
>
> maybe I was misunderstood. What I am sharing in my repositories are
> java projects, not entire workspaces. Each client has its own (version
> specific) workspace. Still there is some metadata inside a project:
>
> - the custom builders
> - the .classpath and .project files
>
> The question is whether these files are properly interpreted by 3.3
> and 3.4 clients
If you only store 3.3 based project meta data then this will work. Only
when you start storing project settings that appeared in 3.4 you might
get into trouble (e.g. loose them again when committed to CVS via 3.3
workspace).

Dani
>
> Felix
>
>
>> If you really have to start with an older version (e.g. because a
>> plug-in doesn't run anymore on 3.4 - which shouldn't happen) from
>> time to time, why not use a different workspace and share the code
>> via repository?

Previous Topic:	SearchEngine not finding expected results
Next Topic:	Interaction of folding and offsets used by JDOM and AST

Goto Forum:

-=] Back to Top [=-

Current Time: Tue Jul 22 08:34:59 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter