Project

General

Profile

Support #1868

Support #1863: Kepler: Migrate Autofocus to Eclipse 4.3 Kepler

Evaluate migration problems

Added by Anonymous almost 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Start date:
12/18/2013
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)

Description

By the migration to 4.3, at least under Mac, some existing functionality is lost.

We need to evaluate this loss also under Windows and Linux.

toolbar.png (99.5 KB) toolbar.png Anonymous, 12/18/2013 04:19 PM

Subtasks

Bug #1876: Kepler: errors in model are not found/displayedRejected

Bug #2011: Kepler: Exceptions after closing AF3 without savingClosedGeorgeta Igna


Related issues

Related to Bug #1875: Kepler: adding a component to a library does not workRejected12/18/2013

Related to Bug #1877: Kepler: impossible to create a component architectureRejected12/18/2013

Related to Bug #1878: Kepler: Exception when simulating (win64, linux)Closed12/18/2013

History

#1 Updated by Anonymous almost 7 years ago

  • Parent task set to #1863

#2 Updated by Anonymous almost 7 years ago

- The bug related to text widgets in property sections is non-existent under Linux and non-existant under win64.

#3 Updated by Anonymous almost 7 years ago

- at startup, many warnings of the form "Both P and P register a package for '...'" (note that it is really P and P, i.e., twice the same name, not P and Q)

  • comes from the plugin.xml files in the corresponding packages * these plugin.xml files register the mentionned package once explicitly, and another time via some automatically generated section * works properly in indigo because the latter section was not generated automatically * easily solved by removing the section registering the package manually

-> I don't apply the changes because this would prevent indigo-af3 to work correctly

-> works fine under win64 :D

- > actually works fine under linux, with the nightly build :-/

#4 Updated by Anonymous almost 7 years ago

- when loading a model, many warnings of the form "Unable to find Action Set: org.eclipse.ui...."
-> I guess GUI elements which were removed/renamed between indigo and kepler?

-> same error under win64

#5 Updated by Anonymous almost 7 years ago

- errors in models (e.g., different type between the input and output of a channel) are not registered/displayed any more:
  • the red error icon does not display
  • no error is registered in the "Model Markers" view

-> created issue 1876

-> works fine under win64

- > actually works fine under linux, with the nightly build :-/

#6 Updated by Anonymous almost 7 years ago

- Exception at startup when the workspace is not empty:

java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at org.fortiss.tooling.kernel.internal.PrototypeService.setupPrototypes(PrototypeService.java:75)
at org.fortiss.tooling.kernel.internal.PrototypeService.<init>(PrototypeService.java:64)
at org.fortiss.tooling.kernel.service.IPrototypeService.<clinit>(IPrototypeService.java:47)
at org.fortiss.tooling.kernel.ui.internal.views.NavigatorNewMenu.<init>(NavigatorNewMenu.java:56)
and many more

-> works fine under win :D

- > actually works fine under linux, with the nightly build :-/

#7 Updated by Anonymous almost 7 years ago

- Impossible to create a component architecture: the option simply does not appear in the contextual menu

-> created Issue 1877

-> works fine under win64 :D

- > actually works fine under linux, with the nightly build :-(

#8 Updated by Anonymous almost 7 years ago

The toolbar displays weirdly on linux: there is a "quick search" field and the icons are pushed to the right. See attached image. Works ok on win64 however.

(solved in the latest build)

#9 Updated by Anonymous almost 7 years ago

When a view with some unsaved changes is closed, Kepler asks if one should save or not. In Indigo, this was asked only when the complete project was closed. Maybe it is just a behavior change of Kepler itself w.r.t. Indigo (and therefore intended)?

#10 Updated by Anonymous over 6 years ago

  • Target version changed from Team Programing - Session 7 to 76

#11 Updated by Anonymous over 6 years ago

  • Subject changed from Evaluate migration problems for win and linux to Evaluate migration problems
  • Assignee changed from Anonymous to Anonymous

#12 Updated by Anonymous over 6 years ago

  • Target version changed from 76 to Phoenix 2.6 Release

#13 Updated by Anonymous over 6 years ago

  • Status changed from New to In Progress
  • Target version changed from Phoenix 2.6 Release to AF3 2.6 RC2 Kepler bug fixes

#14 Updated by Anonymous over 6 years ago

  • Status changed from In Progress to Closed

Also available in: Atom PDF