Home » Newcomers » Newcomers » Eclipse's compatibility policy
Eclipse's compatibility policy [message #171934] |
Thu, 21 September 2006 01:39 |
Shaddy Baddah Messages: 2 Registered: July 2009 |
Junior Member |
|
|
Hi,
If someone could point me to a document detailing Eclipse's
compatibility policy, it would be much appreciated.
My question relates to changes to project settings by more recent
versions of Eclipse. My understanding is that within a minor version of
Eclipse (e.g. 3.1, as opposed to 3.2), every (sub) release (e.g. 3.1.1,
3.1.2) will be fully compatible, across many compatibility areas (e.g.
API), and pertaining to my question, project settings.
Further, my understanding is that a project created in, say 3.1, will be
compatible for use in 3.2. Projects created in 3.2 are not necessarily
compatible for use in 3.1.
Finally, my question(s) is, when using a 3.1 project in 3.2, is it
expected that modification be done to the project settings, for 3.2
compatibility? Are any changes done to the project settings required to
retain the 3.1 compatibility from which the project was sourced?
Thanks in advance,
Shaddy
|
|
|
Re: Eclipse's compatibility policy [message #172034 is a reply to message #171934] |
Thu, 21 September 2006 18:08 |
Eclipse User |
|
|
|
Originally posted by: eclipse4.rizzoweb.com
Shaddy Baddah wrote:
> Hi,
>
> If someone could point me to a document detailing Eclipse's
> compatibility policy, it would be much appreciated.
>
> My question relates to changes to project settings by more recent
> versions of Eclipse. My understanding is that within a minor version of
> Eclipse (e.g. 3.1, as opposed to 3.2), every (sub) release (e.g. 3.1.1,
> 3.1.2) will be fully compatible, across many compatibility areas (e.g.
> API), and pertaining to my question, project settings.
>
> Further, my understanding is that a project created in, say 3.1, will be
> compatible for use in 3.2. Projects created in 3.2 are not necessarily
> compatible for use in 3.1.
>
> Finally, my question(s) is, when using a 3.1 project in 3.2, is it
> expected that modification be done to the project settings, for 3.2
> compatibility? Are any changes done to the project settings required to
> retain the 3.1 compatibility from which the project was sourced?
The wording above gets a little confusing, but I think this information
will help you:
Later Eclipse versions can always read projects created in earlier
versions. However, once the later version touches the project, it is no
longer guaranteed to work in the earlier Eclipse version. This applies
to point releases and major releases alike (2.1 -> 3.0, 3.1 -> 3.2). For
minor update releases (eg, 3.1 -> 3.1.2) everything should be totally
forwards and backwards compatible.
I am not the keeper of the "official" Eclipse policy, but this is how it
has worked for every release in the 4+ years I've used Eclipse.
--
Hope this helps,
Eric
|
|
|
Re: Eclipse's compatibility policy [message #172110 is a reply to message #172034] |
Fri, 22 September 2006 06:51 |
Shaddy Baddah Messages: 2 Registered: July 2009 |
Junior Member |
|
|
Hi,
Eric Rizzo wrote:
> The wording above gets a little confusing, but I think this information
> will help you:
Yeah, sorry about that. Was trying to be articulate, and probably
overdid it.
> Later Eclipse versions can always read projects created in earlier
> versions. However, once the later version touches the project, it is no
> longer guaranteed to work in the earlier Eclipse version. This applies
> to point releases and major releases alike (2.1 -> 3.0, 3.1 -> 3.2). For
> minor update releases (eg, 3.1 -> 3.1.2) everything should be totally
> forwards and backwards compatible.
"touch" is a good word to describe what I meant. This confirms what I
expected.
To me, this is interesting. It makes sense, no doubt, but in explicit
terms, Eclipse maintains project backwards compatibility by migrating
the project settings one time.
Thanks,
Shaddy
|
|
|
Goto Forum:
Current Time: Sat Apr 27 03:57:07 GMT 2024
Powered by FUDForum. Page generated in 0.08260 seconds
|