Eclipse Community Forums: TMF (Xtext) » Updating Xtext 2.2.1 to 2.3.0

Home » Modeling » TMF (Xtext) » Updating Xtext 2.2.1 to 2.3.0

Updating Xtext 2.2.1 to 2.3.0 [message #897930]

Wed, 25 July 2012 09:06

Eclipse User

I couldn't find any documents about upgrading from 2.2.1 to 2.3.0. The release notes only mention new features.

1. Are there any code changes necessary to update to 2.3.0?

2. Should it be possible to update Eclipse using the archived update site from http://www.eclipse.org/modeling/tmf/downloads/?

Regards,

A. Digulla

Re: Updating Xtext 2.2.1 to 2.3.0 [message #897940 is a reply to message #897930]

Wed, 25 July 2012 09:27

Eclipse User

On 2012-25-07 15:06, Aaron Digulla wrote:
> I couldn't find any documents about upgrading from 2.2.1 to 2.3.0. The
> http://www.eclipse.org/Xtext/releasenotes/2.3.0/new_and_noteworthy.php
> only mention new features.
>
> 1. Are there any code changes necessary to update to 2.3.0?
>
Depends on your customizations. I have quite a few complicated
customizations, and managed to move my code from 2.2.1 to 2.3.0 in 1-2
hours.

Regards
- henrik

Re: Updating Xtext 2.2.1 to 2.3.0 [message #898369 is a reply to message #897940]

Thu, 26 July 2012 05:34

Eclipse User

How about updating the Eclipse plug-ins? Did anyone manage that? Is/should it be possible?

I get lots of errors from p2 because many Xtext bundles are singletons and Eclipse refuses to update them :-/ Two examples are the docs and examples:

Xtext documentation

Cannot complete the install because of a conflicting dependency.
  Software being installed: Xtext Documentation 2.3.0.v201206120633 (org.eclipse.xtext.docs.feature.group 2.3.0.v201206120633)
  Software currently installed: Xtext SDK 2.2.1.v201112130541 (org.eclipse.xtext.sdk.feature.group 2.2.1.v201112130541)
  Only one of the following can be installed at once:
    Xtext Documentation 2.3.0.v201206120633 (org.eclipse.xtext.doc 2.3.0.v201206120633)
    Xtext Documentation 2.2.1.v201112130541 (org.eclipse.xtext.doc 2.2.1.v201112130541)
  Cannot satisfy dependency:
    From: Xtext Documentation 2.3.0.v201206120633 (org.eclipse.xtext.docs.feature.group 2.3.0.v201206120633)
    To: org.eclipse.xtext.doc [2.3.0.v201206120633]
  Cannot satisfy dependency:
    From: Xtext SDK 2.2.1.v201112130541 (org.eclipse.xtext.sdk.feature.group 2.2.1.v201112130541)
    To: org.eclipse.xtext.xtext.ui.feature.group [2.2.1.v201112130541]
  Cannot satisfy dependency:
    From: Xtext Xtext UI 2.2.1.v201112130541 (org.eclipse.xtext.xtext.ui.feature.group 2.2.1.v201112130541)
    To: org.eclipse.xtext.doc [2.2.1.v201112130541]

Xtext examples:

Cannot complete the install because of a conflicting dependency.
  Software being installed: Xtext Examples 2.3.0.v201206120633 (org.eclipse.xtext.examples.feature.group 2.3.0.v201206120633)
  Software currently installed: Xtext Xtext UI 2.2.1.v201112130541 (org.eclipse.xtext.xtext.ui.feature.group 2.2.1.v201112130541)
  Only one of the following can be installed at once:
    Xtext Ecore Ui Support 2.3.0.v201206120633 (org.eclipse.xtext.ui.codetemplates 2.3.0.v201206120633)
    Xtext Ecore Ui Support 2.2.1.v201112130541 (org.eclipse.xtext.ui.codetemplates 2.2.1.v201112130541)
  Cannot satisfy dependency:
    From: Xtext Examples 2.3.0.v201206120633 (org.eclipse.xtext.examples.feature.group 2.3.0.v201206120633)
    To: org.eclipse.xtext.ui.feature.group [2.3.0,2.4.0)
  Cannot satisfy dependency:
    From: Xtext UI 2.2.1.v201112130541 (org.eclipse.xtext.ui.feature.group 2.2.1.v201112130541)
    To: org.eclipse.xtext.ui.codetemplates [2.2.1.v201112130541]
  Cannot satisfy dependency:
    From: Xtext UI 2.3.0.v201206120633 (org.eclipse.xtext.ui.feature.group 2.3.0.v201206120633)
    To: org.eclipse.xtext.ui.codetemplates [2.3.0.v201206120633]
  Cannot satisfy dependency:
    From: Xtext Xtext UI 2.2.1.v201112130541 (org.eclipse.xtext.xtext.ui.feature.group 2.2.1.v201112130541)
    To: org.eclipse.xtext.ui.feature.group [2.2.1,2.3.0)

Xtext base:

Cannot complete the install because of a conflicting dependency.
  Software being installed: Xbase 2.3.0.v201206120633 (org.eclipse.xtext.xbase.feature.group 2.3.0.v201206120633)
  Software currently installed: Xtext UI 2.2.1.v201112130541 (org.eclipse.xtext.ui.feature.group 2.2.1.v201112130541)
  Only one of the following can be installed at once:
    Xtext UI Core 2.3.0.v201206120633 (org.eclipse.xtext.ui 2.3.0.v201206120633)
    Xtext UI Core 2.2.1.v201112130541 (org.eclipse.xtext.ui 2.2.1.v201112130541)
  Cannot satisfy dependency:
    From: Xtext UI 2.2.1.v201112130541 (org.eclipse.xtext.ui.feature.group 2.2.1.v201112130541)
    To: org.eclipse.xtext.ui [2.2.1.v201112130541]
  Cannot satisfy dependency:
    From: Xbase 2.3.0.v201206120633 (org.eclipse.xtext.xbase.feature.group 2.3.0.v201206120633)
    To: org.eclipse.xtext.xbase.ui [2.3.0.v201206120633]
  Cannot satisfy dependency:
    From: Xbase UI 2.3.0.v201206120633 (org.eclipse.xtext.xbase.ui 2.3.0.v201206120633)
    To: bundle org.eclipse.xtext.ui [2.3.0,3.0.0)

Why can't I install two versions of the docs?

Regards,

A. Digulla

[Updated on: Thu, 26 July 2012 05:39] by Moderator

Re: Updating Xtext 2.2.1 to 2.3.0 [message #898443 is a reply to message #898369]

Thu, 26 July 2012 07:46

Eclipse User

Am 26.07.12 11:34, schrieb Aaron Digulla:
> How about updating the Eclipse plug-ins? Did anyone manage that?
> Is/should it be possible?

Sure. "Check for updates" should do the trick.

>
> I get lots of errors from p2 because many Xtext bundles are singletons
> and Eclipse refuses to update them :-/

That indicates an inconsistent manual selection of to-be-installed features.

Regards,
Sebastian
--
Looking for professional support for Xtext, Xtend or Eclipse Modeling?
Go visit: http://xtext.itemis.com

Re: Updating Xtext 2.2.1 to 2.3.0 [message #898468 is a reply to message #898443]

Thu, 26 July 2012 08:36

Eclipse User

Hi

In my experience, p2 is not perfect and I have had trouble when using
N-builds. It appears that
p2 does not always recognize that there is something consistently better
enabling it to kick out the
old. I have sometimes had to manually uninstall the unwanted version to
enable installation of the
new. This then works; I don't now why because often the uninstall breaks
the prerequisites of
other still installed software.

Anyway; just Uninstall problematic old stuff and you could be ok.

Regards

Ed Willink
>> I get lots of errors from p2 because many Xtext bundles are singletons
>> and Eclipse refuses to update them :-/
>
> That indicates an inconsistent manual selection of to-be-installed
> features.

Re: Updating Xtext 2.2.1 to 2.3.0 [message #898487 is a reply to message #898443]

Thu, 26 July 2012 09:20

Eclipse User

Sebastian Zarnekow wrote on Thu, 26 July 2012 13:46

> How about updating the Eclipse plug-ins? Did anyone manage that?
> Is/should it be possible?

Sure. "Check for updates" should do the trick.

Damn.

Sebastian Zarnekow wrote on Thu, 26 July 2012 13:46

> I get lots of errors from p2 because many Xtext bundles are singletons
> and Eclipse refuses to update them :-/

That indicates an inconsistent manual selection of to-be-installed features.

In my case, it means that I must not merge your p2 update site with other update sites into one big update site Sad

I probably could use a composite p2 repo but that causes a lot of unnecessary traffic. *sigh*

What I don't understand: How can p2 update the bundles from your site (even though they are singletons) but not from mine?? Is there some trick to tell p2 that it can update a singleton?

Regards,

A. Digulla

Re: Updating Xtext 2.2.1 to 2.3.0 [message #898498 is a reply to message #898487]

Thu, 26 July 2012 09:38

Eclipse User

On 2012-26-07 15:20, Aaron Digulla wrote:
> What I don't understand: How can p2 update the bundles from your site
> (even though they are singletons) but not from mine?? Is there some
> trick to tell p2 that it can update a singleton?

Have you checked that your non-updateable "singleton" is not bound by
something else that you are not updating ?

Regards
- henrik

Re: Updating Xtext 2.2.1 to 2.3.0 [message #898504 is a reply to message #898498]

Thu, 26 July 2012 09:48

Eclipse User

Well, the error message says:

  Software being installed: Xtext Documentation 2.3.0.v201206120633 (org.eclipse.xtext.docs.feature.group 2.3.0.v201206120633)
  Software currently installed: Xtext SDK 2.2.1.v201112130541 (org.eclipse.xtext.sdk.feature.group 2.2.1.v201112130541)
  Only one of the following can be installed at once:
    Xtext Documentation 2.3.0.v201206120633 (org.eclipse.xtext.doc 2.3.0.v201206120633)
    Xtext Documentation 2.2.1.v201112130541 (org.eclipse.xtext.doc 2.2.1.v201112130541)

so basically, I can't update Xtext Documentation because Xtext SDK wants the old version of the docs.

But I get a similar error when I try to update Xtext SDK :-/ I just tried to come up with a shorter error message. I guess I'll have to try again.

[Updated on: Thu, 26 July 2012 09:53] by Moderator

Re: Updating Xtext 2.2.1 to 2.3.0 [message #899015 is a reply to message #898487]

Mon, 30 July 2012 03:43

Eclipse User

If you repackage Xtext features on an own update site, you have to make
sure that you include all features. Otherwise the update procedure won't
work since not all features that were previously installed can be
updated if you miss one of those.

Regards,
Sebastian
--
Looking for professional support for Xtext, Xtend or Eclipse Modeling?
Go visit: http://xtext.itemis.com

Am 26.07.12 15:20, schrieb Aaron Digulla:
> Sebastian Zarnekow wrote on Thu, 26 July 2012 13:46
>> > How about updating the Eclipse plug-ins? Did anyone manage that?
>> > Is/should it be possible?
>>
>> Sure. "Check for updates" should do the trick.
>
>
> Damn.
>
> Sebastian Zarnekow wrote on Thu, 26 July 2012 13:46
>> > I get lots of errors from p2 because many Xtext bundles are singletons
>> > and Eclipse refuses to update them :-/
>>
>> That indicates an inconsistent manual selection of to-be-installed
>> features.
>
>
> In my case, it means that I must not merge your p2 update site with
> other update sites into one big update site :(
>
> I probably could use a composite p2 repo but that causes a lot of
> unnecessary traffic. *sigh*
>
> What I don't understand: How can p2 update the bundles from your site
> (even though they are singletons) but not from mine?? Is there some
> trick to tell p2 that it can update a singleton?
>
> Regards,
>
> A. Digulla

Previous Topic:	JUnit test not using current validator
Next Topic:	handling both latin-1 and utf-8 files

Goto Forum:

-=] Back to Top [=-

Current Time: Tue Jul 15 22:11:55 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter