[JBoss JIRA] (JBIDE-23815) NPE in BuildConfigPropertySource.getResourcePropertyDescriptors
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23815?page=com.atlassian.jira.plugi... ]
Jan Richter closed JBIDE-23815.
-------------------------------
> NPE in BuildConfigPropertySource.getResourcePropertyDescriptors
> ---------------------------------------------------------------
>
> Key: JBIDE-23815
> URL: https://issues.jboss.org/browse/JBIDE-23815
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.Final
> Reporter: Aurélien Pupier
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.4.3.Final
>
> Attachments: buildconfig-properties.png, npe.webm, spring-boot-camel-template.png, test-ose.zip
>
>
> {noformat}
> !ENTRY org.eclipse.jface 4 2 2017-01-31 10:27:08.951
> !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface".
> !STACK 0
> java.lang.NullPointerException
> at org.jboss.tools.openshift.internal.ui.property.BuildConfigPropertySource.getResourcePropertyDescriptors(BuildConfigPropertySource.java:56)
> at org.jboss.tools.openshift.internal.ui.property.ResourcePropertySource.getPropertyDescriptors(ResourcePropertySource.java:62)
> at org.eclipse.ui.views.properties.PropertySheetEntry.computeMergedPropertyDescriptors(PropertySheetEntry.java:171)
> at org.eclipse.ui.views.properties.PropertySheetEntry.refreshChildEntries(PropertySheetEntry.java:506)
> at org.eclipse.ui.views.properties.PropertySheetEntry.setValues(PropertySheetEntry.java:732)
> at org.eclipse.ui.views.properties.PropertySheetViewer.setInput(PropertySheetViewer.java:980)
> at org.eclipse.ui.views.properties.PropertySheetPage.selectionChanged(PropertySheetPage.java:525)
> at org.jboss.tools.openshift.internal.ui.property.tabbed.OpenShiftResourcePropertySection$2.selectionChanged(OpenShiftResourcePropertySection.java:140)
> at org.eclipse.jface.viewers.Viewer$1.run(Viewer.java:158)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:155)
> at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2191)
> at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1229)
> at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1258)
> at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:242)
> at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:236)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:405)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4410)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4228)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3816)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
> 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:148)
> 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:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
> {noformat}
> here is the json available when I click "Edit" on the application:
> {noformat}
> {
> "metadata" : {
> "name" : "camel-ose-springboot-xml",
> "namespace" : "test1",
> "selfLink" : "/api/v1/namespaces/test1/services/camel-ose-springboot-xml",
> "uid" : "a28f19cd-e298-11e6-9637-525400ee9c8f",
> "resourceVersion" : "69156",
> "creationTimestamp" : "2017-01-25T00:53:07Z",
> "labels" : {
> "expose" : "true",
> "group" : "com.mycompany",
> "project" : "camel-ose-springboot-xml",
> "provider" : "fabric8",
> "version" : "1.0.0-SNAPSHOT"
> },
> "annotations" : {
> "fabric8.io/iconUrl" : "img/icons/camel.svg",
> "prometheus.io/port" : "9779",
> "prometheus.io/scrape" : "true"
> }
> },
> "spec" : {
> "ports" : [{
> "name" : "http",
> "protocol" : "TCP",
> "port" : 80,
> "targetPort" : 8080
> }],
> "selector" : {
> "group" : "com.mycompany",
> "project" : "camel-ose-springboot-xml",
> "provider" : "fabric8"
> },
> "portalIP" : "172.30.65.90",
> "clusterIP" : "172.30.65.90",
> "type" : "ClusterIP",
> "sessionAffinity" : "None"
> },
> "status" : {"loadBalancer" : {}},
> "kind" : "Service",
> "apiVersion" : "v1"
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23811) ZipException in CDICoreBuilder when indexing some Maven artifacts
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23811?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-23811:
-----------------------------------------
I tried again on a fresh install and cannot reproduce either :(
> ZipException in CDICoreBuilder when indexing some Maven artifacts
> -----------------------------------------------------------------
>
> Key: JBIDE-23811
> URL: https://issues.jboss.org/browse/JBIDE-23811
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Fix For: 4.4.4.AM1
>
>
> it would be nice to provide more information in log such as the classes in inspection by CDI Core Builder.
> Also if there are some issues with those jars, please report bugs to them.
> {noformat}
> !ENTRY org.jboss.tools.common.core 4 0 2017-01-17 11:17:20.815
> !MESSAGE invalid LOC header (bad signature)
> !STACK 0
> java.util.zip.ZipException: invalid LOC header (bad signature)
> at java.util.zip.ZipFile.read(Native Method)
> at java.util.zip.ZipFile.access$1400(ZipFile.java:60)
> at java.util.zip.ZipFile$ZipFileInputStream.read(ZipFile.java:717)
> at java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(ZipFile.java:419)
> at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:158)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
> at java.io.DataInputStream.readFully(DataInputStream.java:195)
> at java.io.DataInputStream.readFully(DataInputStream.java:169)
> at org.jboss.jandex.Indexer.verifyMagic(Indexer.java:433)
> at org.jboss.jandex.Indexer.index(Indexer.java:689)
> at org.jboss.tools.common.core.jandex.JandexUtil.createJarIndex(JandexUtil.java:56)
> at org.jboss.tools.common.core.jandex.JandexUtil.hasAnnotation(JandexUtil.java:104)
> at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.hasAnnotatedBeans(BeanArchiveDetector.java:276)
> at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.resolve(BeanArchiveDetector.java:203)
> at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.detectBeanModule(ClassPathMonitor.java:150)
> at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.process(ClassPathMonitor.java:106)
> at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:215)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> {noformat}
> !ENTRY org.jboss.tools.common.model 4 0 2017-01-25 16:11:53.722
> !MESSAGE Exception occurs when reading C:\Users\Aurelien Pupier\.m2\repository\org\apache\aries\blueprint\org.apache.aries.blueprint.core\1.7.1\org.apache.aries.blueprint.core-1.7.1.jar
> !STACK 0
> java.util.zip.ZipException: invalid LOC header (bad signature)
> at java.util.zip.ZipFile.read(Native Method)
> at java.util.zip.ZipFile.access$1400(Unknown Source)
> at java.util.zip.ZipFile$ZipFileInputStream.read(Unknown Source)
> at java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(Unknown Source)
> at java.util.zip.InflaterInputStream.read(Unknown Source)
> at java.io.BufferedInputStream.fill(Unknown Source)
> at java.io.BufferedInputStream.read1(Unknown Source)
> at java.io.BufferedInputStream.read(Unknown Source)
> at org.jboss.tools.common.model.filesystems.impl.JarAccess.getContent(JarAccess.java:235)
> at org.jboss.tools.common.model.filesystems.impl.JarAccess.isTextEntry(JarAccess.java:266)
> at org.jboss.tools.common.model.filesystems.impl.JarFolderImpl.createFileObject(JarFolderImpl.java:95)
> at org.jboss.tools.common.model.filesystems.impl.JarFolderImpl.loadChildren(JarFolderImpl.java:78)
> at org.jboss.tools.common.model.impl.RegularObjectImpl.getChildByPathPart(RegularObjectImpl.java:159)
> at org.jboss.tools.common.model.filesystems.impl.JarFolderImpl.getChildByPathPart(JarFolderImpl.java:152)
> at org.jboss.tools.common.model.impl.XModelObjectImpl.getChildByPath(XModelObjectImpl.java:347)
> at org.jboss.tools.common.model.impl.XModelObjectImpl.getChildByPath(XModelObjectImpl.java:352)
> at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.readRuntimes(ClassPathMonitor.java:286)
> at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.process(ClassPathMonitor.java:103)
> at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:215)
> at org.jboss.tools.cdi.core.CDICoreBuilder.<init>(CDICoreBuilder.java:101)
> at org.jboss.tools.cdi.core.CDICoreNature.load(CDICoreNature.java:420)
> at org.jboss.tools.cdi.core.CDICoreNature.resolveStorage(CDICoreNature.java:393)
> at org.jboss.tools.cdi.core.CDICoreNature.resolve(CDICoreNature.java:406)
> at org.jboss.tools.cdi.core.CDICorePlugin.getCDI(CDICorePlugin.java:165)
> at org.jboss.tools.cdi.core.CDICorePlugin$RCL.resourceChanged(CDICorePlugin.java:104)
> at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:299)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:289)
> at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:152)
> at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:374)
> at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1469)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:46)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23977) Base New and Noteworthy for 4.4.3.Final
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23977?page=com.atlassian.jira.plugi... ]
Jeff MAURY closed JBIDE-23977.
------------------------------
Resolution: Rejected
> Base New and Noteworthy for 4.4.3.Final
> -----------------------------------------------------
>
> Key: JBIDE-23977
> URL: https://issues.jboss.org/browse/JBIDE-23977
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common, foundation, usage
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Priority: Critical
>
> Jeff MAURY,
> Search for your component's New and Noteworthy issues:
> Queries:
> * [Completed Base JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...]
> * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...]
> * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...]
> * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...]
> If no N&N issues are found for Base, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them.
> Document the ones relevant for Base by submitting a pull request against:
> * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio...
> If your PR's commit comment is of the form... {code}JBIDE-23968 #comment Create N&N for Base 4.4.3.Final #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied.
> If there is nothing new or noteworthy for Base for this milestone, please *reject* and *close* this issue.
> ----
> If there is nothing new or noteworthy for 4.4.3.Final since the AM3 release of Base, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents.
> If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.4.3.Final.adoc file here:
> * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio...
> The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc.
> However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.4.3.Final.adoc file, adding: {code}page-include-previous: false{code}.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23990) Server New and Noteworthy for 4.4.3.Final
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23990?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-23990:
----------------------------------
Assignee: Jeff MAURY (was: Rob Stryker)
> Server New and Noteworthy for 4.4.3.Final
> -----------------------------------------------------
>
> Key: JBIDE-23990
> URL: https://issues.jboss.org/browse/JBIDE-23990
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: archives, jmx, server
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Priority: Critical
>
> Rob Stryker,
> Search for your component's New and Noteworthy issues:
> Queries:
> * [Completed Server JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...]
> * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...]
> * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...]
> * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...]
> If no N&N issues are found for Server, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them.
> Document the ones relevant for Server by submitting a pull request against:
> * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio...
> If your PR's commit comment is of the form... {code}JBIDE-23968 #comment Create N&N for Server 4.4.3.Final #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied.
> If there is nothing new or noteworthy for Server for this milestone, please *reject* and *close* this issue.
> ----
> If there is nothing new or noteworthy for 4.4.3.Final since the AM3 release of Server, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents.
> If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.4.3.Final.adoc file here:
> * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio...
> The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc.
> However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.4.3.Final.adoc file, adding: {code}page-include-previous: false{code}.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23490) Server adapter: provide ability to link pods/'deployment config'/'replication controller'(?) when no service is available
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23490?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-23490:
------------------------------------
Think of a daemon that uses the twitter stream API to receive data and then calls internal OpenShift services. It will not be exposed as a service. This is one example but I'm pretty usre we can find others
> Server adapter: provide ability to link pods/'deployment config'/'replication controller'(?) when no service is available
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23490
> URL: https://issues.jboss.org/browse/JBIDE-23490
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: new_and_noteworthy, openshift_v3, server_adapter, server_adapter_wizard
> Fix For: 4.4.3.Final
>
>
> When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to create an OpenShift server adapters to deploy new version of the application.
> The only that we are sure that will be always available are pods so it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds when there is no service provided.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23490) Server adapter: provide ability to link pods/'deployment config'/'replication controller'(?) when no service is available
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23490?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-23490:
-----------------------------------------
{quote}could you be more specific "several camel router are just polling something and expose no services"? Because routes can be linked ONLY to services. IP addresses of pods and services are internal, thus only way to show application from outside is via route which expose public DNS. {quote}
I was talking about Camel Routes, not OpenShift routes.
> Server adapter: provide ability to link pods/'deployment config'/'replication controller'(?) when no service is available
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23490
> URL: https://issues.jboss.org/browse/JBIDE-23490
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: new_and_noteworthy, openshift_v3, server_adapter, server_adapter_wizard
> Fix For: 4.4.3.Final
>
>
> When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to create an OpenShift server adapters to deploy new version of the application.
> The only that we are sure that will be always available are pods so it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds when there is no service provided.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23490) Server adapter: provide ability to link pods/'deployment config'/'replication controller'(?) when no service is available
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23490?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-23490:
---------------------------------------
[~aurelien.pupier] could you be more specific "several camel router are just polling something and expose no services"? Because routes can be linked ONLY to services. IP addresses of pods and services are internal, thus only way to show application from outside is via route which expose public DNS.
[~jeffmaury] I wrote "probably" to the always. The argument you are using with daemon is what I was going to write in previous post (database, daemon), but I removed it because this issue was not initially about this use case thus I don't think that is the reason why this feature has been implemented. If FIS consists of several containers communicating to each other, it would be enough to have intranet communication in OpenShift. But than... isn't it more probable that in such case would be deployed a container to OpenShift with configuration e.g. via parameters/env. vars, instead of having an application deployed with source code which can be changed via Server adapter?
> Server adapter: provide ability to link pods/'deployment config'/'replication controller'(?) when no service is available
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23490
> URL: https://issues.jboss.org/browse/JBIDE-23490
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: new_and_noteworthy, openshift_v3, server_adapter, server_adapter_wizard
> Fix For: 4.4.3.Final
>
>
> When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to create an OpenShift server adapters to deploy new version of the application.
> The only that we are sure that will be always available are pods so it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds when there is no service provided.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month