[JBoss JIRA] (JBDS-4706) Use "Red Hat Developer Studio" instead of "Red Hat JBoss Developer Studio" in graphics & text
by Melissa Flinn (JIRA)
[ https://issues.jboss.org/browse/JBDS-4706?page=com.atlassian.jira.plugin.... ]
Melissa Flinn commented on JBDS-4706:
-------------------------------------
I do not see an answer to my question about the JBoss perspective in this JIRA. Did I miss it? I just installed the latest build and JBoss remains the default perspective. Will that be the case for the GA release?
> 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: installer
> Affects Versions: 12.0.0.AM1
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 12.0.0.AM3
>
> Attachments: DevStudio_iconproduction.zip, JBossPerspective.jpg, about_devstudio.png, devstudio_banner.png, heading.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, 9 months
[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22138:
------------------------------------------
according to [~rob.stryker] the best place to make this happen is a m2e project configurator. The configurator would then set the module name according to the pom. The question then is how to make sure we'd only configure those project that we want to deploy to OpenShift. I guess that the OpenShift server wizard would set some marker to the project that the configurator would catch and set the module name accordingly? [~fbricon] [~rawb] thoughts?
> Server adapter: doesn't respect openshift maven profile
> -------------------------------------------------------
>
> Key: JBIDE-22138
> URL: https://issues.jboss.org/browse/JBIDE-22138
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477
> Openshift plugin 3.1.0.Final-v20160401-2357-B263
> Reporter: Rafael Benevides
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.6.0.AM3
>
>
> This is a follow up on JBIDE-22128.
> The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-22138 at 6/12/18 2:03 PM:
-------------------------------------------------------------------
according to [~rob.stryker] the best place to make this happen is a m2e project configurator. The configurator would then set the module name according to the pom. The question then is how to make sure we'd only configure those project that we want to deploy to OpenShift. I guess that the OpenShift server wizard would set some marker to the project that the configurator would catch and set the module name accordingly? [~fbricon], [~rawb] thoughts?
was (Author: adietish):
according to [~rob.stryker] the best place to make this happen is a m2e project configurator. The configurator would then set the module name according to the pom. The question then is how to make sure we'd only configure those project that we want to deploy to OpenShift. I guess that the OpenShift server wizard would set some marker to the project that the configurator would catch and set the module name accordingly? [~fbricon] [~rawb] thoughts?
> Server adapter: doesn't respect openshift maven profile
> -------------------------------------------------------
>
> Key: JBIDE-22138
> URL: https://issues.jboss.org/browse/JBIDE-22138
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477
> Openshift plugin 3.1.0.Final-v20160401-2357-B263
> Reporter: Rafael Benevides
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.6.0.AM3
>
>
> This is a follow up on JBIDE-22128.
> The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-24979) Scale up/down/to: NPE if you have only a rc, no dc for your app
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24979?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-24979.
---------------------------------
Scaling is now working correctly.
Verified in:
Red Hat Developer Studio
Version: 12.0.0.AM3
Build id: AM3-v20180611-0421-B2705
Build date: 20180611-0421
> Scale up/down/to: NPE if you have only a rc, no dc for your app
> ---------------------------------------------------------------
>
> Key: JBIDE-24979
> URL: https://issues.jboss.org/browse/JBIDE-24979
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.x
> Reporter: Andre Dietisheim
> Assignee: Dmitrii Bocharov
> Labels: openshift_v3, scale
> Fix For: 4.6.0.AM3
>
> Attachments: eap-without-service-nor-deploymentconfig.json, image-2017-09-04-21-24-57-027.png
>
>
> # ASSERT: make sure that you have an app that has *NO* deployment config, just a replication controller
> (EXEC: if you dont, create it via the attached custom template [^eap-without-service-nor-deploymentconfig.json])
> # EXEC: in OpenShift explorer: select the pod for your rc, pick "Scale > Up" or "Scale > Down" or "Scale > To"
> !image-2017-09-04-21-24-57-027.png!
> The very same is true if you do the same via the properties view "Deployments". There's a "Scale" item for the deployment context menu, but it does nothing.
> Result:
> Nothing happens and in the log you discover the following:
> {code}
> org.eclipse.e4.core.di.InjectionException: java.lang.NullPointerException
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:65)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:305)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:239)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:487)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:431)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:446)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.lambda$2(AbstractContributionItem.java:472)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4257)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1502)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1525)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1510)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1314)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4081)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1155)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1044)
> 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 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> 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)
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler.getDeploymentConfig(ScaleDeploymentHandler.java:143)
> at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler.getDeploymentConfig(ScaleDeploymentHandler.java:136)
> at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler.getDeploymentConfig(ScaleDeploymentHandler.java:106)
> at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler.execute(ScaleDeploymentHandler.java:78)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:291)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:92)
> at sun.reflect.GeneratedMethodAccessor104.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26079) Manage Project Wizard: is not available when project is selected in explorer (is only if connection is selected)
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26079?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-26079.
---------------------------------
New item is added in context menu and its working. Closing.
Verified in:
Red Hat Developer Studio
Version: 12.0.0.AM3
Build id: AM3-v20180611-0421-B2705
Build date: 20180611-0421
> Manage Project Wizard: is not available when project is selected in explorer (is only if connection is selected)
> ----------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26079
> URL: https://issues.jboss.org/browse/JBIDE-26079
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.6.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: explorer, manage_projects_wizard
> Fix For: 4.6.0.AM3
>
> Attachments: edit-projects-entry-when-project-is-selected.png, missing-edit-projects.png
>
>
> steps:
> # ASSERT: have at least 1 project in your OpenShift server
> # EXEC: in Explorer: select the project and open up the context menu
> Result:
> I have no entry to add/remove projects, I have to select the connection in order to be able to do that.
> !missing-edit-projects.png!
>
> Expected result:
> Offer Edit > Projects... when selecting a project in OpenShift Explorer.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26073) Manage Projects Wizard: Dialog-text to confirm removal says "<missing argument">
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26073?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-26073.
---------------------------------
Message is updated. Closing.
Verified in:
Red Hat Developer Studio
Version: 12.0.0.AM3
Build id: AM3-v20180611-0421-B2705
Build date: 20180611-0421
> Manage Projects Wizard: Dialog-text to confirm removal says "<missing argument">
> --------------------------------------------------------------------------------
>
> Key: JBIDE-26073
> URL: https://issues.jboss.org/browse/JBIDE-26073
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: manage_projects_wizard
> Fix For: 4.6.0.AM3
>
> Attachments: confirm-project-removal.png, dialog-missing-argument.png
>
>
> # ASSERT: have at least 1 connection to a remote server (https://openshift.com, https://api.engint.openshift.com, https://open.paas.redhat.com, etc.)
> # ASSERT: have at least 1 project in your OpenShift
> # EXEC: in OpenShift Explorer: select connection & pick Edit > Projects...
> # ASSERT: "Manage Projects" wizard shows up, listing all projects
> # EXEC: select 1 project and hit "Remove..."
> Result:
> A dialog shows up asking you to confirm the removal. The message shows "<missing argument>"
> !dialog-missing-argument.png!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-21869) Encoding issue in when streaming Build Logs to the console
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21869?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-21869.
---------------------------------
Closing - retested on win10, mac and fedora and encoding was fine.
Verified in:
Red Hat Developer Studio
Version: 12.0.0.AM3
Build id: AM3-v20180611-0421-B2705
Build date: 20180611-0421
> Encoding issue in when streaming Build Logs to the console
> ----------------------------------------------------------
>
> Key: JBIDE-21869
> URL: https://issues.jboss.org/browse/JBIDE-21869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: console
> Fix For: 4.6.0.AM3
>
> Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png
>
>
> Create a new nodejs app, when a build is running, in the OpenShift Explorer, right click on the build and select the Build Log... menu.
> It'll start to spew weird characters eventually :
> {noformat}
> I0315 10:38:28.749220 1 docker.go:286] Image "registry.access.redhat.com/openshift3/nodejs-010-rhel7:latest" not available locally, pulling ...
> I0315 10:39:16.195418 1 source.go:197] Downloading "https://github.com/openshift/nodejs-ex.git" ...
> I0315 10:39:19.670243 1 install.go:236] Using "assemble" installed from "image:///usr/libexec/s2i/assemble"
> I0315 10:39:19.670318 1 install.go:236] Using "run" installed from "image:///usr/libexec/s2i/run"
> I0315 10:39:19.670356 1 install.go:236] Using "save-artifacts" installed from "image:///usr/libexec/s2i/save-artifacts"
> ---> Installing application source
> ---> Building your Node application from source
> E0315 10:39:21.193046 1 util.go:91] npm info it worked if it ends with ok
> E0315 10:39:21.193216 1 util.go:91] npm info using npm(a)2.14.13
> E0315 10:39:21.193229 1 util.go:91] npm info using node(a)v0.10.40
> ...
> E0315 10:39:27.511826 1 util.go:91] npm info prepublish nodejs-ex(a)0.0.1
> ejs(a)2.4.1 node_modules/ejs
> express(a)4.13.4 node_modules/express
> ��������� escape-html(a)1.0.3
> ��������� array-flatten(a)1.1.1
> ��������� utils-merge(a)1.0.0
> ��������� cookie-signature(a)1.0.6
> ��������� merge-descriptors(a)1.0.1
> ��������� fresh(a)0.3.0
> ��������� methods(a)1.1.2
> ��������� range-parser(a)1.0.3
> ��������� vary(a)1.0.1
> ��������� path-to-regexp(a)0.1.7
> ��������� cookie(a)0.1.5
> ��������� parseurl(a)1.3.1
> ��������� content-type(a)1.0.1
> ��������� etag(a)1.7.0
> ��������� content-disposition(a)0.5.1
> ��������� serve-static(a)1.10.2
> ��������� depd(a)1.1.0
> ��������� qs(a)4.0.0
> ��������� finalhandler(a)0.4.1 (unpipe(a)1.0.0)
> ��������� on-finished(a)2.3.0 (ee-first(a)1.1.1)
> ��������� debug(a)2.2.0 (ms(a)0.7.1)
> ��������� proxy-addr(a)1.0.10 (forwarded(a)0.1.0, ipaddr.js(a)1.0.5)
> ��������� send(a)0.13.1 (destroy(a)1.0.4, statuses(a)1.2.1, ms(a)0.7.1, mime(a)1.3.4, http-errors(a)1.3.1)
> ��������� type-is(a)1.6.12 (media-typer(a)0.3.0, mime-types(a)2.1.10)
> ��������� accepts(a)1.2.13 (negotiator(a)0.5.3, mime-types(a)2.1.10)
> mongodb(a)2.1.8 node_modules/mongodb
> ��������� es6-promise(a)3.0.2
> ��������� mongodb-core(a)1.3.5 (bson(a)0.4.22, require_optional(a)1.0.0)
> ��������� readable-stream(a)1.0.31 (inherits(a)2.0.1, isarray(a)0.0.1, string_decoder(a)0.10.31, core-util-is(a)1.0.2)
> E0315 10:39:27.684535 1 util.go:91] npm info ok
> I0315 10:39:42.202321 1 sti.go:245] Using provided push secret for pushing 172.30.183.94:5000/node/nodejs-mongodb-example:latest image
> I0315 10:39:42.202361 1 sti.go:249] Pushing 172.30.183.94:5000/node/nodejs-mongodb-example:latest image ...
> {noformat}
> I'm running on OSX
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months