[JBoss JIRA] (JBIDE-22303) Server Adapter: Manually set pod deployment path is ignored
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22303?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-22303:
-----------------------------------------------
Besides, the selection checkbox 'Use inferred Pod Deployment Path' is not respected when model saves podPath to server/project. Value of the checkbox goes nowhere, and podPath value (if it was manually filled before checking 'use inferred' on) is saved anyway. So, if manually set pot path would not be ignored, we would have another bug - 'Use inferred Pod Deployment Path is ignored'.
> Server Adapter: Manually set pod deployment path is ignored
> -----------------------------------------------------------
>
> Key: JBIDE-22303
> URL: https://issues.jboss.org/browse/JBIDE-22303
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.0.Alpha2
>
>
> When creating a new OpenShift 3 server adapter, manually filled Pod deployment path is ignored by the server adapter and still inferred one is used for publishing changes between eclipse workspace project and remote OpenShift application.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22296) Provide on-hover tooltip for repo URL in openshift import wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22296?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-22296 at 5/4/16 4:52 PM:
------------------------------------------------------------------
tested it, works fine for me.
rebased and merged into master
was (Author: adietish):
renbased and merged into master
> Provide on-hover tooltip for repo URL in openshift import wizard
> ----------------------------------------------------------------
>
> Key: JBIDE-22296
> URL: https://issues.jboss.org/browse/JBIDE-22296
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Radim Hopp
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.4.0.Alpha2
>
> Attachments: snapshot1.png
>
>
> This is a followup of JBIDE-21841. In JBIDE-21841, there was added the build config pane, but even with this pane, there is no easy way how to _see_ whole URL of repository (only way is to enlarge whole wizard dialog).
> !snapshot1.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22303) Server Adapter: Manually set pod deployment path is ignored
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22303?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-22303:
-------------------------------------
this is more visible when creating an app from the wildfly builder
> Server Adapter: Manually set pod deployment path is ignored
> -----------------------------------------------------------
>
> Key: JBIDE-22303
> URL: https://issues.jboss.org/browse/JBIDE-22303
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Marián Labuda
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.0.Alpha2
>
>
> When creating a new OpenShift 3 server adapter, manually filled Pod deployment path is ignored by the server adapter and still inferred one is used for publishing changes between eclipse workspace project and remote OpenShift application.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22303) Server Adapter: Manually set pod deployment path is ignored
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22303?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-22303:
-----------------------------------
Assignee: Viacheslav Kabanovich
> Server Adapter: Manually set pod deployment path is ignored
> -----------------------------------------------------------
>
> Key: JBIDE-22303
> URL: https://issues.jboss.org/browse/JBIDE-22303
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.0.Alpha2
>
>
> When creating a new OpenShift 3 server adapter, manually filled Pod deployment path is ignored by the server adapter and still inferred one is used for publishing changes between eclipse workspace project and remote OpenShift application.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22303) Server Adapter: Manually set pod deployment path is ignored
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22303?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22303:
--------------------------------
Story Points: 4
Sprint: devex #114 May 2017
> Server Adapter: Manually set pod deployment path is ignored
> -----------------------------------------------------------
>
> Key: JBIDE-22303
> URL: https://issues.jboss.org/browse/JBIDE-22303
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.0.Alpha2
>
>
> When creating a new OpenShift 3 server adapter, manually filled Pod deployment path is ignored by the server adapter and still inferred one is used for publishing changes between eclipse workspace project and remote OpenShift application.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-20474) Cleanup last CI builds more aggressively
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20474?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-20474:
-------------------------------
Story Points: 3
Sprint: devex #114 May 2017
> Cleanup last CI builds more aggressively
> ----------------------------------------
>
> Key: JBIDE-20474
> URL: https://issues.jboss.org/browse/JBIDE-20474
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Affects Versions: 4.3.0.CR1
> Reporter: Fred Bricon
> Assignee: Nick Boldt
> Priority: Optional
> Fix For: 4.4.0.Alpha2
>
>
> [18/08/2015 15:29:34] Fred Bricon: when building central, I see
> [18/08/2015 15:29:36] Fred Bricon: [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,58kB at 0B/s)
> [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,18kB at 0B/s)
> [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,93kB at 0B/s)
> [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,88kB at 0B/s)
> [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,25kB at 0B/s)
> [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,77kB at 0B/s)
> [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,43kB at 0B/s)
> [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,94kB at 0B/s)
> [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,74kB at 0B/s)
> [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,7kB at 0B/s)
> [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,58kB at 0B/s)
> [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,95kB at 0B/s)
> [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,11kB at 0B/s)
> [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,86kB at 0B/s)
> Nick sez:
> {quote}
> somethign something "store fewer instances of /snapshots/builds /JOB_NAME/TIMESTAMP; more aggressive cleanup required; suggest only keeping 5 builds max"
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22301) NPE in new OS application from eclipse project with no remote git reference.
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22301?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-22301:
-----------------------------------------------
Probably the wizard still should be able to finish with no remote git reference, that is why it is a warning rather than an error.
The cause of the null pointer is a missed check at selecting a model (template or image) to complete the job.
[~jcantrill], please check if the minimal fix in the pull request is good enough.
> NPE in new OS application from eclipse project with no remote git reference.
> ----------------------------------------------------------------------------
>
> Key: JBIDE-22301
> URL: https://issues.jboss.org/browse/JBIDE-22301
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Environment: JBDS 10.0.0.Alpha1
> Reporter: Radim Hopp
>
> Trying to finish new openshift application wizard using existing aplication from workspace without remote git repository fails with NPE:
> {noformat:title=Unhandled event loop exception}
> java.lang.NullPointerException
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizard.performFinish(NewApplicationWizard.java:194)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:790)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:423)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4494)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1339)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3832)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3443)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:287)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:270)
> at org.jboss.tools.openshift.internal.ui.handler.NewApplicationHandler.execute(NewApplicationHandler.java:34)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> 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:497)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264)
> 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:491)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:425)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:449)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem$3.handleEvent(AbstractContributionItem.java:477)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4494)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1339)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3832)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3443)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1118)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1019)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:691)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> 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:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:670)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:609)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1516)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1489)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22128) Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22128?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-22128:
-------------------------------------
Create an openshift project following the steps in https://htmlpreview.github.io/?https://github.com/redhat-helloworld-msa/h...
In Eclipse,
- import the application from the created deployment
- create a Server Adapter, pointing at the workspace project. It should show up as a module of the server in the Servers view
- do some local changes to the project
- start the server adapter, the project should be published to openshift as ROOT.war (see rsync console)
> Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile
> ---------------------------------------------------------------------------
>
> Key: JBIDE-22128
> URL: https://issues.jboss.org/browse/JBIDE-22128
> 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: Fred Bricon
> Labels: respin-b
> Fix For: 4.3.1.CR1
>
>
> I have a Java project with an "openshift" maven profile that creates a ROOT.war
> When I create a "Server Adapter", the openshift plugins deploys the name of the project.war
> The plugin should be integrated with M2E in a way that if I select/enable the "openshift" profile on M2E, the Openshift plugin should deploy ROOT.war through "Server Adapter".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22128) Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22128?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-22128:
-----------------------------------
Assignee: Marián Labuda (was: Fred Bricon)
> Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile
> ---------------------------------------------------------------------------
>
> Key: JBIDE-22128
> URL: https://issues.jboss.org/browse/JBIDE-22128
> 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: Marián Labuda
> Labels: respin-b
> Fix For: 4.3.1.CR1
>
>
> I have a Java project with an "openshift" maven profile that creates a ROOT.war
> When I create a "Server Adapter", the openshift plugins deploys the name of the project.war
> The plugin should be integrated with M2E in a way that if I select/enable the "openshift" profile on M2E, the Openshift plugin should deploy ROOT.war through "Server Adapter".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months