Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Platform » .settings compatability between 3.4 and 3.5
.settings compatability between 3.4 and 3.5 [message #445567] Fri, 31 July 2009 19:52 Go to next message
Michael Giroux is currently offline Michael GirouxFriend
Messages: 81
Registered: July 2009
Location: Phoenix, AZ
Member
Our project team is currently using Eclipse 3.4. Our project contains XML
and XSL files that cause validation errors in the IDE (but are valid at
runtime) so we have to disable validation in the IDE.

I have started to evaluate migration to 3.5, and have encountered
differences in the .settings/org.eclipse.wst.validation.prefs:

USER_PREFERENCE=overrideGlobalPreferencestruedisableAllValid ationfalseversion1.2.102.v200905201610
vals/org.eclipse.wst.xsl.core.xsl/global=FF02

If I commit this my (3.5) version of the .settings, will Eclipse 3.4 be
able to handle the USER_PREFERENCE version number?

Normally, once a workspace is migrated, it is not reliable on previous
version, but in the case of files that are shared via SVN such as the
settings directory, what is the correct way for a team to migrate? If I
commit the .settings file, will team members using 3.4 get errors?

I was not able to find anything regarding migration that covers this
specific issue. If I overlooked something, please provide a link.

Michael
Re: .settings compatability between 3.4 and 3.5 [message #468035 is a reply to message #445567] Mon, 03 August 2009 17:38 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: eclipse-news.rizzoweb.com

Copying to the eclipse.webtools group since this is essentially about
the WTP project.


Michael Giroux wrote:
> Our project team is currently using Eclipse 3.4. Our project contains
> XML and XSL files that cause validation errors in the IDE (but are valid
> at runtime) so we have to disable validation in the IDE.
> I have started to evaluate migration to 3.5, and have encountered
> differences in the .settings/org.eclipse.wst.validation.prefs:
>
> USER_PREFERENCE=overrideGlobalPreferencestruedisableAllValid ationfalseversion1.2.102.v200905201610
>
> vals/org.eclipse.wst.xsl.core.xsl/global=FF02
>
> If I commit this my (3.5) version of the .settings, will Eclipse 3.4 be
> able to handle the USER_PREFERENCE version number?
>
> Normally, once a workspace is migrated, it is not reliable on previous
> version, but in the case of files that are shared via SVN such as the
> settings directory, what is the correct way for a team to migrate? If I
> commit the .settings file, will team members using 3.4 get errors?
>
> I was not able to find anything regarding migration that covers this
> specific issue. If I overlooked something, please provide a link.
>
> Michael
>
>
Re: .settings compatability between 3.4 and 3.5 [message #468058 is a reply to message #468035] Mon, 03 August 2009 19:57 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: dcarver.starstandard.org

If you can upgrade to Eclipse 3.5, you can set on a per project basis
the validation settings for XSL files. This is particularly handy for
templates that can't be found, as you can change these to warnings
instead of errors.

Hopefully we'll get project level validation settings for XML as well.

Dave

Eric Rizzo wrote:
> Copying to the eclipse.webtools group since this is essentially about
> the WTP project.
>
>
> Michael Giroux wrote:
>> Our project team is currently using Eclipse 3.4. Our project contains
>> XML and XSL files that cause validation errors in the IDE (but are
>> valid at runtime) so we have to disable validation in the IDE. I have
>> started to evaluate migration to 3.5, and have encountered differences
>> in the .settings/org.eclipse.wst.validation.prefs:
>>
>> USER_PREFERENCE=overrideGlobalPreferencestruedisableAllValid ationfalseversion1.2.102.v200905201610
>>
>> vals/org.eclipse.wst.xsl.core.xsl/global=FF02
>>
>> If I commit this my (3.5) version of the .settings, will Eclipse 3.4
>> be able to handle the USER_PREFERENCE version number?
>>
>> Normally, once a workspace is migrated, it is not reliable on previous
>> version, but in the case of files that are shared via SVN such as the
>> settings directory, what is the correct way for a team to migrate? If
>> I commit the .settings file, will team members using 3.4 get errors?
>>
>> I was not able to find anything regarding migration that covers this
>> specific issue. If I overlooked something, please provide a link.
>>
>> Michael
>>
>>
Re: .settings compatability between 3.4 and 3.5 [message #493657 is a reply to message #445567] Tue, 27 October 2009 13:54 Go to previous message
Michael Giroux is currently offline Michael GirouxFriend
Messages: 81
Registered: July 2009
Location: Phoenix, AZ
Member
The question has become more general in recent days. Some of the developers on the team would like to upgrade to 3.5 to evaluate new features, while the rest of the team stays with 3.4.

If the 3.5 users commit any of the project files (.settings/*) will there be any problems for the 3.4 users when they update their project from SVN?

Specifically, can a mix of 3.4 and 3.5 users operate on a shared project without stepping on each other?
Previous Topic:Editor toolbar action visibility
Next Topic:dll and MFC and errors
Goto Forum:
  


Current Time: Mon Mar 08 13:49:47 GMT 2021

Powered by FUDForum. Page generated in 0.01986 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top