My Eclipse

分类： MyEclipse

  • MyEclipse fails to start after upgrade to 2022 version
    I upgraded MyEclipse (bing) to the latest from within the MyElcipse IDE (2019 version). Upon restarting, I get a popup error to check the log file. The contents of the log file are as follows. Please let me know how I can fix this issue.

    I upgraded MyEclipse (bing) to the latest from within the MyElcipse IDE (2019 version). Upon restarting, I get a popup error to check the log file. The contents of the log file are as follows. Please let me know how I can fix this issue.

    !SESSION 2022-12-21 12:48:49.199 ———————————————–
    eclipse.buildId=16.0.0.CI-009
    java.version=16.0.2
    java.vendor=Azul Systems, Inc.
    BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
    Command-line arguments: -os win32 -ws win32 -arch x86_64 -clean

    !ENTRY org.eclipse.equinox.simpleconfigurator 4 0 2022-12-21 12:48:49.986
    !MESSAGE FrameworkEvent ERROR
    !STACK 0
    org.osgi.framework.BundleException: Exception in org.eclipse.equinox.internal.simpleconfigurator.Activator.start() of bundle org.eclipse.equinox.simpleconfigurator.
    at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:863)
    at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:791)
    at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:1015)
    at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:365)
    at org.eclipse.osgi.container.Module.doStart(Module.java:603)
    at org.eclipse.osgi.container.Module.start(Module.java:467)
    at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1844)
    at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$2$1.execute(EquinoxContainerAdaptor.java:150)
    at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1837)
    at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1780)
    at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1742)
    at org.eclipse.osgi.container.SystemModule.startWorker(SystemModule.java:269)
    at org.eclipse.osgi.container.Module.doStart(Module.java:603)
    at org.eclipse.osgi.container.Module.start(Module.java:467)
    at org.eclipse.osgi.container.SystemModule.start(SystemModule.java:193)
    at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:439)
    at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:458)
    at org.eclipse.osgi.launch.Equinox.start(Equinox.java:120)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:338)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:251)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78)
    at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.base/java.lang.reflect.Method.invoke(Method.java:567)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:596)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1467)
    at org.eclipse.equinox.launcher.Main.main(Main.java:1440)
    Caused by: java.lang.IllegalStateException: The System Bundle was updated. The framework must be restarted to finalize the configuration change
    at org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.install(ConfigApplier.java:84)
    at org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:189)
    at org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:204)
    at org.eclipse.equinox.internal.simpleconfigurator.Activator.start(Activator.java:64)
    at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:842)
    at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
    at java.base/java.security.AccessController.doPrivileged(AccessController.java:554)
    at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:834)
    … 27 more
    Root exception:
    java.lang.IllegalStateException: The System Bundle was updated. The framework must be restarted to finalize the configuration change
    at org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.install(ConfigApplier.java:84)
    at org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:189)
    at org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:204)
    at org.eclipse.equinox.internal.simpleconfigurator.Activator.start(Activator.java:64)
    at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:842)
    at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
    at java.base/java.security.AccessController.doPrivileged(AccessController.java:554)
    at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:834)
    at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:791)
    at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:1015)
    at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:365)
    at org.eclipse.osgi.container.Module.doStart(Module.java:603)
    at org.eclipse.osgi.container.Module.start(Module.java:467)
    at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1844)
    at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$2$1.execute(EquinoxContainerAdaptor.java:150)
    at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1837)
    at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1780)
    at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1742)
    at org.eclipse.osgi.container.SystemModule.startWorker(SystemModule.java:269)
    at org.eclipse.osgi.container.Module.doStart(Module.java:603)
    at org.eclipse.osgi.container.Module.start(Module.java:467)
    at org.eclipse.osgi.container.SystemModule.start(SystemModule.java:193)
    at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:439)
    at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:458)
    at org.eclipse.osgi.launch.Equinox.start(Equinox.java:120)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:338)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:251)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78)
    at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.base/java.lang.reflect.Method.invoke(Method.java:567)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:596)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1467)
    at org.eclipse.equinox.launcher.Main.main(Main.java:1440)

    !ENTRY org.eclipse.osgi 4 0 2022-12-21 12:48:49.986
    !MESSAGE Bundle org.eclipse.equinox.simpleconfigurator_1.3.300.v20190716-0825 [1] is not active.

    !ENTRY org.eclipse.osgi 4 0 2022-12-21 12:48:50.001
    !MESSAGE Application error
    !STACK 1
    java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini).
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:81)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78)
    at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.base/java.lang.reflect.Method.invoke(Method.java:567)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:596)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1467)
    at org.eclipse.equinox.launcher.Main.main(Main.java:1440)

    -clean command args was already there; may be added during update process. It is gone after successful start.

    Looks like the problem is fixed by changing the following two jars to newer versions. I did this based on an FAQ link found on another post on this forums. That FAQ suggested updating the following and adding -clean switch. In my case I found the latest jar versions from bundles.info file in configuration\org.eclipse.equinox.simpleconfigurator folder.

    #osgi.bundles=reference\:file\:org.eclipse.equinox.simpleconfigurator_1.3.300.v20190716-0825.jar@1\:start

    osgi.bundles=reference\:file\:org.eclipse.equinox.simpleconfigurator_1.4.0.v20210315-2228.jar@1\:start

    #osgi.framework=file\:plugins/org.eclipse.osgi_3.15.0.v20190830-1434.jar

    osgi.framework=file\:plugins/org.eclipse.osgi_3.17.100.v20211104-1730.jar

  • MyEclipse 2022.1 – Unable to add new server
    I am trying to add new server however I have observed following issues in it.
    1.There is no way to add server by right clicking at server section.
    2.Window-Preferences-MyEclipse giving an error at the screen.
    MyEclipse Configuration –
    Version: 2022.1.0
    Build id: 16.0.0-20220324
    I have attached both the exceptions as attachment. At this point there is now way for me to add new server.
    I had been using MyEclipse 2019 before migrating to 2022. The version 2022 has lot of issues in it. After migration I had to create new workspace to resolve an issue.
    The clean command is not working for me.
    If I create new workspace then current observation will be resolved. Please don’t suggest that option as this would be forth time for me to create new workspace to resolve IDE issue. I don’t want to invest my time again to resolve IDE issue rather than productive work.
    I haven’t changed the java version at myeclipse.ini file. Installation summary has been attached.
    I kept the installation same and pointed it to new workspace. Now I don’t see the issue.

  • Web deployment with a Maven project
    I’ve been trying to deploy a Maven web project to the internal Tomcat 9.0 but it doesn’t seem to be working as I expected.

    I’ve been trying to deploy a Maven web project to the internal Tomcat 9.0 but it doesn’t seem to be working as I expected.

    If prior to deployment I go to Deployment Assembly, then Add -> Java Build Path Entries -> Maven Dependencies -> Finish then the project won’t appear in the Add/Remove Deployments dialog. If I deploy it first without dependencies, then go to Deployment Assembly to add Maven dependencies and then for the server choose Publish I get an error with the following in the log:

    java.lang.NullPointerException: Cannot invoke “org.eclipse.wst.common.componentcore.resources.IVirtualComponent.getDeployedName()” because “component” is null
    at org.eclipse.wst.common.componentcore.internal.util.VirtualReferenceUtilities.getDefaultProjectArchiveName(VirtualReferenceUtilities.java:81)
    at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getJavaClasspathReferences(J2EEModuleVirtualComponent.java:358)
    at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getNonManifestRefs(J2EEModuleVirtualComponent.java:262)
    at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getReferences(J2EEModuleVirtualComponent.java:181)
    at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.addConsumedReferences(FlatVirtualComponent.java:259)
    at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.treeWalk(FlatVirtualComponent.java:234)
    at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.cacheResources(FlatVirtualComponent.java:188)
    at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.fetchResources(FlatVirtualComponent.java:118)

    For now I’ve worked around it by manually getting Maven to copy dependencies and then deploying the target/dependency folder but it would save hassle not having to go through this stage each time a change is made to a related project.

    This is with MyEclipse 2022.1.0 running on Windows 10.

    I presume this is a project with the maven-war-plugin? If so, you should import the project into Eclipse using the Maven import wizard – this will run a few additional steps which will analyze the pom.xml and create the corresponding Eclipse metadata for the tooling within MyEclipse. For instance, since your project has the Maven war plugin, the web facet will be added and deployment assembly will be correctly set up, automatically.

    You could try to undo the Eclipse level changes you’ve manually made and re-import the project from its raw Maven from using File > Import > Maven > Existing Maven Projects.

  • Problem: same views in different perspectives MyEclipse 2022 Ubuntu Ubuntu 22.4
    the problem occurs between perspectives: “Java Enterprise”, “Java” and “Debug”.
    When I add or change the position of a view (eg “Problem”, “Console”, etc.), the change occurs on all perspectives.
    with a new workspace the problem is solved.

    Thank you for confirming that the issue does not exist in a new workspace.
    You could try Window > New Window on your previous workspace and check how it works. This should clear the cache and reset all the perspectives.

  • Infinite popup – Image Loading Error
    In the html editor, I mistakenly hit the image src url and then it show the error message like this.
    Image Loading Error
    Unable to launch Image Editor because input file is either an unrecognized image type, or corrupt.
    which is cool. But then when I hit ‘OK’ to close this, the same popup comes again and again until I kill MyEclipse process by task manager.
    Would you be able to check this?
    Version: 2022.1.0
    Build id: 16.0.0-20220324

    Hi,

    Sorry that you are seeing this issue. Thank you for the details and the screenshots.
    I could replicate it at my end. I have filed a bug report for the dev team to work on it.
    We will keep you posted when the fix is out.

  • Debugging Generic Web Applications in MyEclipse
    Many developers spend half of their time fixing bugs. A powerful debugger is critical to produce a quality web application in a timely manner. That is why our debugger is so valuable, making it easy to debug your JavaScript, (X)HTML and JSP files.

    Starting the Debugger
    To debug a generic web application, you must have Google Chrome installed. When you start the debugger, Google Chrome opens automatically.

    Use any of the following methods to start the debugger:
    Project Explorer—Right-click on the web project or enterprise application project (EAR) and select Debug As>JavaScript in JavaEE Web Application; or, select the project and click the Debug button dddebugbutton (select JavaScript in JavaEE Web Application and click OK if the project is not deployed).
    Server View—After the project has been deployed to the server, right-click on the project in the Servers view and select Launch JavaScript Debug Session; or, select the project and click the Debug button dddebugbutton.
    Debug Configurations—Select Debug Configurations from the Run menu. Select your project from the JavaScript in Web Application folder and click Debug.

    Using the Debug Perspective
    The first time the debugger encounters a breakpoint, you are asked to switch to the Debug perspective. Select Remember my decision to avoid this message in the future, and then click Yes. The Debug perspective includes the views you need to effectively debug your code.

    Editing Debug Configurations
    The first time you debug your application, the debug configuration is automatically created with the default settings. To view the configuration, select Run>Debug Configurations from the menu; or, right-click the generic project in the Project Explorer and select Debug As>Debug Configurations. Your project displays in the JavaScript in Web Application folder. You can edit an existing configuration or right-click on the folder and select New to create a new configuration.

    Tip: If you do not select a Server, you can debug a web application that is deployed on a remote server.

    Source Map Support
    If you are using a tool for transpilation (such as TypeScript or Coffeescript), minification (such as minifyJS or UglifyJS) or bundling (such as Browserify), Source Map Support allows you to easily debug your JavaScript files by allowing the debugger to represent current code execution position in the context of the original file. If you are using source maps, select Enable source maps support on Debug Configurations. You will also need to properly configure your processing tool. Learn more

    Hot-Swap JavaScript Code
    Select the Hot-swap JavaScript code to browser option to automatically view JavaScript changes directly in the Browser without reloading the page. Use this feature in conjunction with Live Preview to speed up your web development.

  • What’s New in MyEclipse2022?
    Jakarta EE 9 & 9.1Get updated support for Jakarta EE 9, along with preliminary support for Jakarta EE 9.1. Add an enterprise project with one of these versions of the specification and your project is created with the correct versions of the schemata and the right libraries.
    Java 17Enjoy built-in support for Java 17 when you configure a Java 17 JDK/JRE in the JRE preference page. Optional access to preview features like “Pattern Matching for Switch” is also available.
    CodeTogetherMyEclipse now includes integrated code collaboration with CodeTogether. Fully end-to-end encrypted, CodeTogether makes teamwork a breeze. Live share your coding session in MyEclipse; guests join from a browser or their IDE, even if it’s different from yours.