[JBoss JIRA] (JBIDE-23815) NPE in BuildConfigPropertySource.getResourcePropertyDescriptors
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23815?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23815:
------------------------------------------
[~aurelien.pupier] can you please provide me the means to replicate this or see what exactly is null in your case?
> 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
> Priority: Critical
> Fix For: 4.4.3.Final
>
>
> {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-23815) NPE in BuildConfigPropertySource.getResourcePropertyDescriptors
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23815?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-23815:
----------------------------------------
Assignee: Andre Dietisheim
> 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
>
>
> {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-23817) Scaling: is not working with OpenShift 3.4 (CDK 2.4)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23817?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23817:
-------------------------------------
Labels: openshift_v3 scaling_pods_wizard (was: openshift_v3)
> Scaling: is not working with OpenShift 3.4 (CDK 2.4)
> ----------------------------------------------------
>
> Key: JBIDE-23817
> URL: https://issues.jboss.org/browse/JBIDE-23817
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.AM2
> Environment: CDK 2.4
> Devstudio 10.3.0.AM2
> Reporter: Radim Hopp
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift_v3, scaling_pods_wizard
> Fix For: 4.4.3.Final
>
> Attachments: Spectacle.yJ3971.png
>
>
> Scaling pods is broken when using Openshift 3.4 from CDK 2.4. I was not able to try it with another Openshift 3.4 installation (https://open.paas.redhat.com/ is not working properly from Devstudio either - ticket INC0496390 with service-now).
> When I select scale to -> and select "4" to scale to 4 pods, the pods get started but they are immediately terminated and the scaling is "1" again.
> This is not happening when I used https://console.engint.openshift.com/ (OpenShift v3.3.1.4).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-21895) Application wizard: Resource name collisions after deleting and recreating the application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21895?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-21895:
----------------------------------------
Assignee: Andre Dietisheim
> Application wizard: Resource name collisions after deleting and recreating the application
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-21895
> URL: https://issues.jboss.org/browse/JBIDE-21895
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Pavol Srna
> Assignee: Andre Dietisheim
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.3.Final
>
> Attachments: 1st-child-of-project.png, Screen Shot 2016-03-17 at 16.19.05.png, Screenshot 2017-02-02 18.22.34.png, Screenshot 2017-02-02 18.22.43.png, os-resources-empty.png
>
>
> 1) Create e.g. node application in a openshift project
> 2) Right click from project explorer -> Delete the application
> 3) repeat step 1)
> Result:
> !Screen Shot 2016-03-17 at 16.19.05.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBDS-4273) Problem installing Teiid from IS discovery site - possible use constraint violation from slf4j / slf4j-api
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4273?page=com.atlassian.jira.plugin.... ]
Lukáš Valach commented on JBDS-4273:
------------------------------------
Thank you all for help.
I verified that Teiid 11.0.1.Final-v20170208-2046-B4143 works with:
Devstudio RPM 10.3-0.20170206.0203.el7
Devstudio RPM 10.2-0.20161128.1631.el7
Jboss Tools 4.4.2.Final
Can I close this jira or is there any other work to do? Will be the latest version of Teiid added to integration stack repository automatically?
> Problem installing Teiid from IS discovery site - possible use constraint violation from slf4j / slf4j-api
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4273
> URL: https://issues.jboss.org/browse/JBDS-4273
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: build, rpm
> Affects Versions: 10.3.0.GA
> Environment: RHEL7, RHSCL 2.4 Alpha 1.1, rh-eclipse46-devstudio.x86_64 10.3-0.20170206.0203.el7
> Integration Stack Discovery site: http://download.jboss.org/jbosstools/neon/integration/updates/integration...
> Reporter: Lukáš Valach
> Assignee: Lukáš Valach
> Fix For: 10.3.0.GA
>
> Attachments: home_eclipse.txt, opt_rh.txt, rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.Jboss_Data_Virtualization_Developement_form_IS_repo_strict.txt
>
>
> [~lvalach] said: {quote}
> Hi Nick,
> I tested installation of stuff from central as you described. I am not finished yet, but here is what I found.
> -install latest integration stack bits from IS
> -JBoss Fule Development - OK
> -JBoss Business P. and Rules D. - OK
> -JBoss Integration and SOA D. - OK
> -JBoss Data Virtualization D. (IS early acess)
> -there is problem with slf4j
> -IS contains Teiid 11.0.1.CR1-v20170117-222 which should be fixed
> -there are error like this:
> {code}
> !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.equinox.preferences".
> !STACK 0
> java.lang.LinkageError: loader constraint violation: when resolving method
> "org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory;" the class loader
> (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) of the current class,
> org/slf4j/LoggerFactory, and the class loader
> (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) for the method's defining class,
> org/slf4j/impl/StaticLoggerBinder, have different
> Class objects for the type org/slf4j/ILoggerFactory
> used in the signature{code}
> -install everything from Central (including PMD and Findbugs, and early access stuff. NOTE: newer versions of the Integration Stack connectors should already be installed from the step above)
> -I installed everything using Central-Software/update, *no remediation action* was needed.
> -Eclipse started but with many errors. So I have to find out which feature causes the problem.{quote}
> [~nickboldt] said:
> {quote}
> loader constraint violation == two different versions of slf4j in the installed plugins
> check in :~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64 vs. in /opt/rh/
> Problem appears to be in *org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory*. {quote}
> [~lvalach] said:
> {quote}
> {code}
> cd ~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64
> find . -iname *slf4j*
> ./configuration/org.eclipse.osgi/1293/0/.cp/lib/slf4j-api-1.6.1.jar
> {code}
> The output for /opt/rh/ is quite long but I can say that it contains slf4j.api_1.7.4.jar
> {quote}
> [~nickboldt] said:
> {quote}
> So, we may have a conflict between slf4j and slf4j-api, which both use the same bundle names, but expose packages differently.
> Unclear which IS project is causing this problem as I thought we'd fixed both SY and TD already.
> * https://issues.jboss.org/browse/SWITCHYARD-2976
> * https://issues.jboss.org/browse/TEIIDDES-2999
> {quote}
> [~lvalach] said:
> {quote}
> I tried to install Jboss Data Virtualization Developement from [IS discovery site|http://download.jboss.org/jbosstools/neon/integration/updates/integr...] again.
> Whole log:
> [^rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.Jboss_Data_Virtualization_Developement_form_IS_repo_strict.txt]
> Slf4j files in ~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64/
> [^home_eclipse.txt]
> Slf4j files in /opt/rh/
> [^opt_rh.txt]
> The problem is caused by Teiid Designer and Teiid Designer Runtime.
> Teiid DataTools Connectivity and Teiid Runtime Clients don't cause problem.
> IS repository contains SwitchYard 2.3.0.CR1-v20170120-1347-B20 which works properly.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23822) Server adapter: is not working with oc v1.4.x
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23822?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23822:
------------------------------------------
change in openshift-restclient java were merged and maven artifact published.
The change in JBT to use the latest client was already merged with JBIDE-23862
> Server adapter: is not working with oc v1.4.x
> ---------------------------------------------
>
> Key: JBIDE-23822
> URL: https://issues.jboss.org/browse/JBIDE-23822
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.AM2
> Environment: Devstudio 10.3.0.AM2.
> CDK 2.4 (OpenShift 3.4)
> oc v1.4.1
> Reporter: Radim Hopp
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.3.Final
>
>
> {noformat}
> !ENTRY org.jboss.tools.openshift.core 2 0 2017-02-01 13:46:34.181
> !MESSAGE Error while publishing server eap-app at OpenShift 3 (10.1.2.2). Could not sync all pods to folder /home/rhopp/workspace-iosdnfuiwne/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample-project@eap-app/deploy
> !STACK 1
> org.eclipse.core.runtime.CoreException: Error while publishing server eap-app at OpenShift 3 (10.1.2.2). Could not sync all pods to folder /home/rhopp/workspace-iosdnfuiwne/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample-project@eap-app/deploy
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftPublishController.publishStart(OpenShiftPublishController.java:83)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.CachedPublisherProfileBehavior.publishStart(CachedPublisherProfileBehavior.java:47)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:942)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
> at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3172)
> at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Contains: OpenShiftBinaryCapability process exited: error: auth info "openshift-dev" does not exist
> !SUBENTRY 1 org.jboss.tools.openshift.core 4 0 2017-02-01 13:46:34.181
> !MESSAGE Error while publishing server eap-app at OpenShift 3 (10.1.2.2). Could not sync all pods to folder /home/rhopp/workspace-iosdnfuiwne/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample-project@eap-app/deploy
> !SUBENTRY 2 org.jboss.tools.openshift.core 4 0 2017-02-01 13:46:34.181
> !MESSAGE OpenShiftBinaryCapability process exited: error: auth info "openshift-dev" does not exist
> !ENTRY org.jboss.tools.openshift.core 4 0 2017-02-01 13:46:35.219
> !MESSAGE Could not sync /home/rhopp/workspace-iosdnfuiwne/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample-project@eap-app/deploy to all pods running the service eap-app
> !SUBENTRY 1 org.jboss.tools.openshift.core 4 0 2017-02-01 13:46:35.219
> !MESSAGE OpenShiftBinaryCapability process exited: error: auth info "openshift-dev" does not exist
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-22141) jboss-app.xml validate problem in JBDS 8.0.0.GA.
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22141?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-22141:
---------------------------------------
I need some help with verifying this.
Just to make it clear, the conclusion is that the original jboss-app.xml from the article is wrong and is not gonna work, correct?
The one Rob provided is still wrong as the version needs to be 6. So something that should work is:
{code}
<?xml version="1.1" encoding="UTF-8"?>
<jboss-app version="6" xmlns="http://www.jboss.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:jee="http://www.jboss.com/xml/ns/javaee"
xsi:schemaLocation="
http://www.jboss.com/xml/ns/javaee
http://www.jboss.org/schema/jbossas/jboss-app_7_0.xsd">
<description>test</description>
</jboss-app>
{code}
And that will give you:
{code}
cvc-complex-type.2.4.a: Invalid content was found starting with element
'description'. One of '{"http://java.sun.com/xml/ns/javaee":application-name, "http://
java.sun.com/xml/ns/javaee":description, "http://java.sun.com/xml/ns/
javaee":display-name, "http://java.sun.com/xml/ns/javaee":icon, "http://
java.sun.com/xml/ns/javaee":initialize-in-order, "http://java.sun.com/xml/ns/
javaee":module}' is expected.
{code}
And that's what your patch will fix so that the xml above should work, [~rob.stryker] ?
Now, how do I try this out in Eclipse? Change it in the catalog bundle? Or if I add the modified xsd in the xml catalog, will that take preference? I tried this and noticed that the patched xsd actually specifies version 7.0, so now I'm confused. With that it seems that actually what should be used is the original xml that Rob provided. But that still tells me that version 7.0 is not defined, even though I added the new xsd to the catalog.
[~rob.stryker], please clarify and advice how to test, thanks.
> jboss-app.xml validate problem in JBDS 8.0.0.GA.
> ------------------------------------------------
>
> Key: JBIDE-22141
> URL: https://issues.jboss.org/browse/JBIDE-22141
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.3.Final
> Reporter: xu zhang
> Assignee: Rob Stryker
> Fix For: 4.5.0.AM1
>
>
> Create "jboss-app.xml" from attachment of article "https://access.redhat.com/solutions/268733" in JBDS 8.0.0, error shows:
> ~~~
> No grammar constraints (DTD or XML Schema) referenced in the document.
> ~~~
> Customer wants JBDS to validate "jboss-app.xml" correctly.
> Please let us know if it will be resolved in the next release/patch.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBDS-4066) DevSuite Installer Account step styles are inconsistent with Target Folder step
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4066?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4066:
--------------------------------
Description:
Account page looks different from Target Location page:
1. Fields with invalid values have red glow border with gradient;
2. There are three areas to show error messages one for each field and one for login error;
3. Username and password error have styling different from login error and from validation messages on Target Location page;
4. Field height is different from Target Location field;
5. When validation messages appear they move elements on Account Page back and forth;
To Do:
1. Always show only one message between fields and buttons
2. If username and password are empty show error message: "Please enter your username and password"
3. If username is empty show error message: "Please enter your username"
4. If password is empty show error message: "Please enter your password"
5. Show only one message at a time, if there is "Invalid account information, please try again" message and password or username is changed hide error message.
Account Step:
!screenshot-1.png!
Target Location Step:
!screenshot-2.png!:
was:
Account page looks different from Target Location page:
1. Fields with invalid values have red glow border with gradient;
2. There are three areas to show error messages one for each field and one for login error;
3. Username and password error have styling different from login error and from validation messages on Target Location page;
4. Field height is different from Target Location field;
5. When validation messages appear they move elements on Account Page back and forth;
To Do:
1. Always show only one message between fields and buttons
2. If username and password are empty show error message: "Please enter your username and password"
3. If username is empty show error message: "Please enter your username"
4. If password is empty show error message: "Please enter your password"
5. Show only one message at a time, if there is "Invalid account information, try again" message and password or username is changed
Account Step:
!screenshot-1.png!
Target Location Step:
!screenshot-2.png!:
> DevSuite Installer Account step styles are inconsistent with Target Folder step
> -------------------------------------------------------------------------------
>
> Key: JBDS-4066
> URL: https://issues.jboss.org/browse/JBDS-4066
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 10.1.0.GA
> Reporter: Denis Golovin
> Assignee: Sudhir Verma
> Labels: ui
> Fix For: 10.3.0.AM2
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> Account page looks different from Target Location page:
> 1. Fields with invalid values have red glow border with gradient;
> 2. There are three areas to show error messages one for each field and one for login error;
> 3. Username and password error have styling different from login error and from validation messages on Target Location page;
> 4. Field height is different from Target Location field;
> 5. When validation messages appear they move elements on Account Page back and forth;
> To Do:
> 1. Always show only one message between fields and buttons
> 2. If username and password are empty show error message: "Please enter your username and password"
> 3. If username is empty show error message: "Please enter your username"
> 4. If password is empty show error message: "Please enter your password"
> 5. Show only one message at a time, if there is "Invalid account information, please try again" message and password or username is changed hide error message.
> Account Step:
> !screenshot-1.png!
> Target Location Step:
> !screenshot-2.png!:
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBDS-4066) DevSuite Installer Account step styles are inconsistent with Target Folder step
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4066?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4066:
--------------------------------
Description:
Account page looks different from Target Location page:
1. Fields with invalid values have red glow border with gradient;
2. There are three areas to show error messages one for each field and one for login error;
3. Username and password error have styling different from login error and from validation messages on Target Location page;
4. Field height is different from Target Location field;
5. When validation messages appear they move elements on Account Page back and forth;
To Do:
1. Always show only one message between fields and buttons
2. If username and password are empty show error message: "Please enter your username and password"
3. If username is empty show error message: "Please enter your username"
4. If password is empty show error message: "Please enter your password"
5. Show only one message at a time, if there is "Invalid account information, try again" message and password or username is changed
Account Step:
!screenshot-1.png!
Target Location Step:
!screenshot-2.png!:
was:
Account page looks different from Target Location page:
1. Fields with invalid values have red glow border with gradient;
2. There are three areas to show error messages one for each field and one for login error;
3. Username and password error have styling different from login error and from validation messages on Target Location page;
4. Field height is different from Target Location field;
5. When validation messages appear they move elements on Account Page back and forth;
To Do:
1. Always show only one message between fields and buttons
2. If username and password are empty show error message: "Please enter your username and password"
3. If username is empty show error message: "Please enter your username"
4. If password is empty show error message: "Please enter your password"
5. Show only one message at a time, if there is
Account Step:
!screenshot-1.png!
Target Location Step:
!screenshot-2.png!:
> DevSuite Installer Account step styles are inconsistent with Target Folder step
> -------------------------------------------------------------------------------
>
> Key: JBDS-4066
> URL: https://issues.jboss.org/browse/JBDS-4066
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 10.1.0.GA
> Reporter: Denis Golovin
> Assignee: Sudhir Verma
> Labels: ui
> Fix For: 10.3.0.AM2
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> Account page looks different from Target Location page:
> 1. Fields with invalid values have red glow border with gradient;
> 2. There are three areas to show error messages one for each field and one for login error;
> 3. Username and password error have styling different from login error and from validation messages on Target Location page;
> 4. Field height is different from Target Location field;
> 5. When validation messages appear they move elements on Account Page back and forth;
> To Do:
> 1. Always show only one message between fields and buttons
> 2. If username and password are empty show error message: "Please enter your username and password"
> 3. If username is empty show error message: "Please enter your username"
> 4. If password is empty show error message: "Please enter your password"
> 5. Show only one message at a time, if there is "Invalid account information, try again" message and password or username is changed
> Account Step:
> !screenshot-1.png!
> Target Location Step:
> !screenshot-2.png!:
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBDS-4066) DevSuite Installer Account step styles are inconsistent with Target Folder step
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4066?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4066:
--------------------------------
Description:
Account page looks different from Target Location page:
1. Fields with invalid values have red glow border with gradient;
2. There are three areas to show error messages one for each field and one for login error;
3. Username and password error have styling different from login error and from validation messages on Target Location page;
4. Field height is different from Target Location field;
5. When validation messages appear they move elements on Account Page back and forth;
To Do:
1. Always show only one message between fields and buttons
2. If username and password are empty show error message: "Please enter your username and password"
3. If username is empty show error message: "Please enter your username"
4. If password is empty show error message: "Please enter your password"
5. Show only one message at a time, if there is
Account Step:
!screenshot-1.png!
Target Location Step:
!screenshot-2.png!:
was:
Account page looks different from Target Location page:
1. Fields with invalid values have red glow border with gradient;
2. There are three areas to show error messages one for each field and one for login error;
3. Username and password error have styling different from login error and from validation messages on Target Location page;
4. Field height is different from Target Location field;
5. When validation messages appear they move elements on Account Page back and forth;
To Do:
1. Always show only one message between fields and buttons
2. If username and password are empty show
Account Step:
!screenshot-1.png!
Target Location Step:
!screenshot-2.png!:
> DevSuite Installer Account step styles are inconsistent with Target Folder step
> -------------------------------------------------------------------------------
>
> Key: JBDS-4066
> URL: https://issues.jboss.org/browse/JBDS-4066
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 10.1.0.GA
> Reporter: Denis Golovin
> Assignee: Sudhir Verma
> Labels: ui
> Fix For: 10.3.0.AM2
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> Account page looks different from Target Location page:
> 1. Fields with invalid values have red glow border with gradient;
> 2. There are three areas to show error messages one for each field and one for login error;
> 3. Username and password error have styling different from login error and from validation messages on Target Location page;
> 4. Field height is different from Target Location field;
> 5. When validation messages appear they move elements on Account Page back and forth;
> To Do:
> 1. Always show only one message between fields and buttons
> 2. If username and password are empty show error message: "Please enter your username and password"
> 3. If username is empty show error message: "Please enter your username"
> 4. If password is empty show error message: "Please enter your password"
> 5. Show only one message at a time, if there is
> Account Step:
> !screenshot-1.png!
> Target Location Step:
> !screenshot-2.png!:
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month