Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade Overture to build against Eclipse Oxygen #653

Closed
peterwvj opened this issue Nov 8, 2017 · 0 comments
Closed

Upgrade Overture to build against Eclipse Oxygen #653

peterwvj opened this issue Nov 8, 2017 · 0 comments
Assignees
Labels
enhancement Not a bug, but nice to have
Milestone

Comments

@peterwvj
Copy link
Member

peterwvj commented Nov 8, 2017

There's a need to upgrade Overture to build against the newest version of Eclipse, which at the current time of writing is Oxygen. The plan is to perform the upgrade immediately after Overture 2.5.4 is released (the release candidate has already been sent out). I tried to upgrade to Oxygen locally, and it seems to work well for the experiments that I have carried out (there are no Eclipse API changes that affect Overture). The only changes required to perform the upgrade are:

diff --git a/ide/pom.xml b/ide/pom.xml
index 39341c7f1b..55ec687a4b 100644
--- a/ide/pom.xml
+++ b/ide/pom.xml
@@ -164,9 +164,9 @@ the manifests, though.
 
   <repositories>
     <repository>
-      <id>eclipse-neon</id>
+      <id>eclipse-oxygen</id>
       <layout>p2</layout>
-      <url>http://download.eclipse.org/releases/neon</url>
+      <url>http://download.eclipse.org/releases/oxygen</url>
     </repository>
   </repositories>
@peterwvj peterwvj added the enhancement Not a bug, but nice to have label Nov 8, 2017
@peterwvj peterwvj added this to the v2.5.4 milestone Nov 8, 2017
@peterwvj peterwvj self-assigned this Nov 8, 2017
@peterwvj peterwvj modified the milestones: v2.5.4, v2.5.6 Nov 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Not a bug, but nice to have
Projects
None yet
Development

No branches or pull requests

1 participant