[JBoss JIRA] (JBDS-4719) Eclipse will not change to alternate JDK with Spring Boot project.
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4719?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4719:
-----------------------------
Component/s: openshift
> Eclipse will not change to alternate JDK with Spring Boot project.
> ------------------------------------------------------------------
>
> Key: JBDS-4719
> URL: https://issues.jboss.org/browse/JBDS-4719
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 11.3.0.GA
> Reporter: Hiram Chirino
> Assignee: Jeff MAURY
> Fix For: 12.9.0.AM2
>
>
> Feed back from [~egetchel] in a recent Fuse enablement session:
> This seems specific to JBDS 11.x as it is not a problem in 10. Typical scenario - I start a new project in Eclipse and it defaults to a JRE enviornment. This gets picked up at runtime. I add the JDK to Eclipse. Normally, I can go into the project configuration and change the compile and runtime to use the new JDK. In Eclipse 11, we could not find any option to do this, and no matter what we did, running the Spring Boot project still defaulted back to the JRE. The only way to force Eclipse to use the JDK was to go into Eclipse and delete the reference to the JRE, so that only a single JDK existed.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBDS-4719) Eclipse will not change to alternate JDK with Spring Boot project.
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4719?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4719:
-----------------------------
Fix Version/s: 12.9.0.AM2
> Eclipse will not change to alternate JDK with Spring Boot project.
> ------------------------------------------------------------------
>
> Key: JBDS-4719
> URL: https://issues.jboss.org/browse/JBDS-4719
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Affects Versions: 11.3.0.GA
> Reporter: Hiram Chirino
> Assignee: Jeff MAURY
> Fix For: 12.9.0.AM2
>
>
> Feed back from [~egetchel] in a recent Fuse enablement session:
> This seems specific to JBDS 11.x as it is not a problem in 10. Typical scenario - I start a new project in Eclipse and it defaults to a JRE enviornment. This gets picked up at runtime. I add the JDK to Eclipse. Normally, I can go into the project configuration and change the compile and runtime to use the new JDK. In Eclipse 11, we could not find any option to do this, and no matter what we did, running the Spring Boot project still defaulted back to the JRE. The only way to force Eclipse to use the JDK was to go into Eclipse and delete the reference to the JRE, so that only a single JDK existed.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBDS-4706) Use "Red Hat Developer Studio" instead of "Red Hat JBoss Developer Studio" in graphics & text
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4706?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4706:
----------------------------------
[~rpdavis] Did we ever get instructions on how to handle the EULA referencing JBoss Middleware? I believe it's unchanged at this point, or at least the EULA in the devstudio installer has not changed.
> Use "Red Hat Developer Studio" instead of "Red Hat JBoss Developer Studio" in graphics & text
> ---------------------------------------------------------------------------------------------
>
> Key: JBDS-4706
> URL: https://issues.jboss.org/browse/JBDS-4706
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: build, installer
> Affects Versions: 12.0.0.AM1
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 12.9.0.AM1
>
> Attachments: DevStudio_iconproduction.zip, JBossPerspective.jpg, about_devstudio.png, devstudio12-central.png, devstudio_banner.png, heading.png, installer01.png, installer02.png, splash.bmp, uninstall.ico
>
>
> Branding has requested that we rename devstudio from "Red Hat JBoss Developer Studio" to "Red Hat Developer Studio".
> We'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-25557) OpenJDK9 + org.jboss.forge: org.jboss.forge.furnace.exception.ContainerException
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25557?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25557:
-------------------------------
Fix Version/s: 4.9.0.AM1
(was: 4.9.x)
> OpenJDK9 + org.jboss.forge: org.jboss.forge.furnace.exception.ContainerException
> --------------------------------------------------------------------------------
>
> Key: JBIDE-25557
> URL: https://issues.jboss.org/browse/JBIDE-25557
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.5.2.AM3
> Environment: FC27 + OpenJDK9
> Red Hat JBoss Developer Studio Version: 11.2.0.AM3
> Reporter: Josef Kopriva
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.9.0.AM1
>
>
> Forge does not start:
> {code:java}
> null
> org.eclipse.core.jobs
> Error
> Thu Jan 11 12:59:40 CET 2018
> An internal error occurred during: "Starting JBoss Forge 3.7.2.Final".
> org.jboss.forge.furnace.exception.ContainerException: No services of type [org.jboss.forge.addon.projects.ProjectFactory] could be found in any started addons.
> at org.jboss.forge.furnace.impl.addons.ImportedImpl.get(ImportedImpl.java:79)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:124)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:97)
> at org.jboss.forge.furnace.services.Imported_$$_javassist_4e1fc78d-0b5f-4839-8d1e-22b7d372d229.get(Imported_$$_javassist_4e1fc78d-0b5f-4839-8d1e-22b7d372d229.java)
> at org.jboss.tools.forge.core.furnace.FurnaceService.lookup(FurnaceService.java:95)
> at org.jboss.tools.forge.ui.util.ForgeHelper.initializeFurnaceRuntime(ForgeHelper.java:99)
> at org.jboss.tools.forge.ui.util.ForgeHelper.access$0(ForgeHelper.java:89)
> at org.jboss.tools.forge.ui.util.ForgeHelper$1.runInWorkspace(ForgeHelper.java:57)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
> {code:java}
> null
> org.eclipse.ui
> Error
> Thu Jan 11 12:59:40 CET 2018
> Unhandled event loop exception
> org.jboss.forge.furnace.exception.ContainerException: No services of type [org.jboss.forge.addon.shell.spi.ShellHandle] could be found in any started addons.
> at org.jboss.forge.furnace.impl.addons.ImportedImpl.get(ImportedImpl.java:79)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:124)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:97)
> at org.jboss.forge.furnace.services.Imported_$$_javassist_4e1fc78d-0b5f-4839-8d1e-22b7d372d229.get(Imported_$$_javassist_4e1fc78d-0b5f-4839-8d1e-22b7d372d229.java)
> at org.jboss.tools.forge.core.furnace.FurnaceService.lookup(FurnaceService.java:95)
> at org.jboss.tools.forge.ui.internal.cli.AeshConsole.start(AeshConsole.java:46)
> at org.jboss.tools.aesh.ui.view.AbstractTextViewer$1.run(AbstractTextViewer.java:46)
> at org.eclipse.ui.internal.PendingSyncExec.run(PendingSyncExec.java:58)
> at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:168)
> at org.eclipse.ui.internal.UISynchronizer.lambda$0(UISynchronizer.java:150)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:37)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4577)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4186)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-25557) OpenJDK9 + org.jboss.forge: org.jboss.forge.furnace.exception.ContainerException
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25557?page=com.atlassian.jira.plugi... ]
Jeff MAURY closed JBIDE-25557.
------------------------------
Resolution: Done
> OpenJDK9 + org.jboss.forge: org.jboss.forge.furnace.exception.ContainerException
> --------------------------------------------------------------------------------
>
> Key: JBIDE-25557
> URL: https://issues.jboss.org/browse/JBIDE-25557
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.5.2.AM3
> Environment: FC27 + OpenJDK9
> Red Hat JBoss Developer Studio Version: 11.2.0.AM3
> Reporter: Josef Kopriva
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.9.0.AM1
>
>
> Forge does not start:
> {code:java}
> null
> org.eclipse.core.jobs
> Error
> Thu Jan 11 12:59:40 CET 2018
> An internal error occurred during: "Starting JBoss Forge 3.7.2.Final".
> org.jboss.forge.furnace.exception.ContainerException: No services of type [org.jboss.forge.addon.projects.ProjectFactory] could be found in any started addons.
> at org.jboss.forge.furnace.impl.addons.ImportedImpl.get(ImportedImpl.java:79)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:124)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:97)
> at org.jboss.forge.furnace.services.Imported_$$_javassist_4e1fc78d-0b5f-4839-8d1e-22b7d372d229.get(Imported_$$_javassist_4e1fc78d-0b5f-4839-8d1e-22b7d372d229.java)
> at org.jboss.tools.forge.core.furnace.FurnaceService.lookup(FurnaceService.java:95)
> at org.jboss.tools.forge.ui.util.ForgeHelper.initializeFurnaceRuntime(ForgeHelper.java:99)
> at org.jboss.tools.forge.ui.util.ForgeHelper.access$0(ForgeHelper.java:89)
> at org.jboss.tools.forge.ui.util.ForgeHelper$1.runInWorkspace(ForgeHelper.java:57)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
> {code:java}
> null
> org.eclipse.ui
> Error
> Thu Jan 11 12:59:40 CET 2018
> Unhandled event loop exception
> org.jboss.forge.furnace.exception.ContainerException: No services of type [org.jboss.forge.addon.shell.spi.ShellHandle] could be found in any started addons.
> at org.jboss.forge.furnace.impl.addons.ImportedImpl.get(ImportedImpl.java:79)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:124)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:97)
> at org.jboss.forge.furnace.services.Imported_$$_javassist_4e1fc78d-0b5f-4839-8d1e-22b7d372d229.get(Imported_$$_javassist_4e1fc78d-0b5f-4839-8d1e-22b7d372d229.java)
> at org.jboss.tools.forge.core.furnace.FurnaceService.lookup(FurnaceService.java:95)
> at org.jboss.tools.forge.ui.internal.cli.AeshConsole.start(AeshConsole.java:46)
> at org.jboss.tools.aesh.ui.view.AbstractTextViewer$1.run(AbstractTextViewer.java:46)
> at org.eclipse.ui.internal.PendingSyncExec.run(PendingSyncExec.java:58)
> at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:168)
> at org.eclipse.ui.internal.UISynchronizer.lambda$0(UISynchronizer.java:150)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:37)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4577)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4186)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBDS-4719) Eclipse will not change to alternate JDK with Spring Boot project.
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-4719?page=com.atlassian.jira.plugin.... ]
Jeff MAURY updated JBDS-4719:
-----------------------------
Affects Version/s: 11.3.0.GA
> Eclipse will not change to alternate JDK with Spring Boot project.
> ------------------------------------------------------------------
>
> Key: JBDS-4719
> URL: https://issues.jboss.org/browse/JBDS-4719
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Affects Versions: 11.3.0.GA
> Reporter: Hiram Chirino
> Assignee: Jeff MAURY
>
> Feed back from [~egetchel] in a recent Fuse enablement session:
> This seems specific to JBDS 11.x as it is not a problem in 10. Typical scenario - I start a new project in Eclipse and it defaults to a JRE enviornment. This gets picked up at runtime. I add the JDK to Eclipse. Normally, I can go into the project configuration and change the compile and runtime to use the new JDK. In Eclipse 11, we could not find any option to do this, and no matter what we did, running the Spring Boot project still defaulted back to the JRE. The only way to force Eclipse to use the JDK was to go into Eclipse and delete the reference to the JRE, so that only a single JDK existed.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBDS-4719) Eclipse will not change to alternate JDK with Spring Boot project.
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-4719?page=com.atlassian.jira.plugin.... ]
Jeff MAURY reassigned JBDS-4719:
--------------------------------
Assignee: Jeff MAURY
> Eclipse will not change to alternate JDK with Spring Boot project.
> ------------------------------------------------------------------
>
> Key: JBDS-4719
> URL: https://issues.jboss.org/browse/JBDS-4719
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Reporter: Hiram Chirino
> Assignee: Jeff MAURY
>
> Feed back from [~egetchel] in a recent Fuse enablement session:
> This seems specific to JBDS 11.x as it is not a problem in 10. Typical scenario - I start a new project in Eclipse and it defaults to a JRE enviornment. This gets picked up at runtime. I add the JDK to Eclipse. Normally, I can go into the project configuration and change the compile and runtime to use the new JDK. In Eclipse 11, we could not find any option to do this, and no matter what we did, running the Spring Boot project still defaulted back to the JRE. The only way to force Eclipse to use the JDK was to go into Eclipse and delete the reference to the JRE, so that only a single JDK existed.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months