[JBoss JIRA] (JBIDE-23490) Provide ability to link pods 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 updated JBIDE-23490:
------------------------------------
Summary: Provide ability to link pods when no service is available (was: Provide ability to link nodes when no service is available)
> Provide ability to link pods 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
> Fix For: 4.4.2.Final
>
>
> When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to bind to a node to deploy a new version.
> it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23490) Provide ability to link pods 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 updated JBIDE-23490:
------------------------------------
Description:
When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to bind to a pod to deploy a new version.
it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds
was:
When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to bind to a node to deploy a new version.
it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds
> Provide ability to link pods 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
> Fix For: 4.4.2.Final
>
>
> When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to bind to a pod to deploy a new version.
> it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23490) Provide ability to link nodes 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:
---------------------------------------
I think this is a duplicate of JBIDE-21627 which should provide more universal solution no just for pods. Marking as duplicate.
> Provide ability to link nodes 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
> Fix For: 4.4.2.Final
>
>
> When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to bind to a node to deploy a new version.
> it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23490) Provide ability to link nodes 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 resolved JBIDE-23490.
-----------------------------------
Fix Version/s: 4.4.2.Final
Resolution: Duplicate Issue
> Provide ability to link nodes 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
> Fix For: 4.4.2.Final
>
>
> When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to bind to a node to deploy a new version.
> it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4176) Useless-provides detected by RPMlint
by Václav Kadlčík (JIRA)
[ https://issues.jboss.org/browse/JBDS-4176?page=com.atlassian.jira.plugin.... ]
Václav Kadlčík commented on JBDS-4176:
--------------------------------------
Yes, "useless-provides" is a more of style check, it doesn't prevent from using an affected RPM. Sometimes there are legitimate reasons a RPM provides two or more versions of the same library though it's not quite usual. It just suggests to check if it's intentional, not an uncontrolled load taken by mistake. If it's clear that we know about all those Provides and want (or have to) to keep them as they are now I'm sure Lukáš will be happy to cut them out as false-positives.
> Useless-provides detected by RPMlint
> ------------------------------------
>
> Key: JBDS-4176
> URL: https://issues.jboss.org/browse/JBDS-4176
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.2.0.AM3
> Environment: RHEL7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Priority: Optional
> Fix For: 10.x
>
> Attachments: opt-rh-list.2.txt, opt-rh-list.2.txt.sh, opt-rh-list.txt, opt-rh-list.txt.sh
>
>
> The rpmlint detects some problems in rpm package:
> {code}
> rpmlint -f ./rpmlint.conf ./rh-eclipse46-devstudio-10.2-0.20161111.1151.el7.x86_64.rpm
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(com.google.guava)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(com.google.inject)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(javax.wsdl)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.apache.commons.collections)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.apache.commons.io)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.apache.commons.lang3)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.apache.commons.logging)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.eclipse.aether.api)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.eclipse.aether.connector.basic)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.eclipse.aether.impl)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.eclipse.aether.spi)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.eclipse.aether.util)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(com.fasterxml.classmate)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.jboss.logging.jboss-logging)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.yaml.snakeyaml)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(slf4j.api)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.objectweb.asm)
> 1 packages and 0 specfiles checked; 17 errors, 0 warnings.
> {code}
> There are only important problems in the list above, another errors/warnings were suppressed according to discussion with [~vkadlcik].
> There is configuration of rpmlint filter:
> {code}
> addFilter("W: ") # Warnings can be suppressed
> addFilter("E: dir-or-file-in-opt") # False positive
> addFilter("E: devel-dependency") # False positive
> addFilter("E: explicit-lib-dependency") # May be improved but is not important for now
> addFilter("E: non-executable-script") # 99% of these errors are false positive comming from upstream, there is a very small chance to get relevant error
> addFilter("E: wrong-script-interpreter") # The same as above
> addFilter("E: zero-length") # The same as above
> {code}
> [~vkadlcik] please correct me if I'm wrong.
> RPMlint test has been automated, you can find it in [jenkins|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-13851) Add source lookup classes to Java Search
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13851?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-13851:
---------------------------------------
I have rebased the patch.
The patch enables debugging of arquillian tests (see JBIDE-13852) and excluding duplicate jars (which, for instance, enables debugging different versions of Hibernate on a JBoss server).
> Add source lookup classes to Java Search
> ----------------------------------------
>
> Key: JBIDE-13851
> URL: https://issues.jboss.org/browse/JBIDE-13851
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: maven
> Affects Versions: 4.1.0.Alpha1
> Reporter: Snjezana Peco
> Assignee: Snjezana Peco
> Fix For: LATER
>
>
> This feature would be implemented in a similar way to adding PDE plugins to the Java Search.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4149) Run Browsersim > java.lang.NoClassDefFoundError: javax/servlet/Servlet on exit
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4149?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-4149:
--------------------------------------
It looks like you are testing devstudio without the PR from Ilya. Otherwise you would get different stacktrace. I like the PR and going to apply it.
> Run Browsersim > java.lang.NoClassDefFoundError: javax/servlet/Servlet on exit
> ------------------------------------------------------------------------------
>
> Key: JBDS-4149
> URL: https://issues.jboss.org/browse/JBDS-4149
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: browsersim, maven, rpm
> Affects Versions: 10.2.0.AM3
> Environment: RHEL7 64bit
> Reporter: Lukáš Valach
> Assignee: Ilya Buziuk
> Priority: Critical
> Fix For: 10.2.0.GA
>
> Attachments: browsersim-error-on-close.png, ClassNotFoundEx_20161102_095940.png, eclipse.log, eclipse_10.2-0.20161101.1258.log, javax.servlet.310rpm_vs_orbit.png, rh-eclipse46-devstudio-snapshots-10_2.repo, rh-eclipse46-devstudio10.2.log.20161102-1855.txt, rh-eclipse46.repo, Screenshot_2016-11-14_16-43-57.png
>
>
> I launch the browsersim (from Quick Access > Run Browsersim), and then exit the sim (right-click > Close), this error appears:
> !browsersim-error-on-close.png|thumbnail!
> {code}
> javax/servlet/Servlet
> Stack trace:
> java.lang.NoClassDefFoundError: javax/servlet/Servlet
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at org.jboss.tools.browsersim.ui.util.ReflectionUtil.call(ReflectionUtil.java:21)
> at org.jboss.tools.browsersim.ui.BrowserSim$3.widgetDisposed(BrowserSim.java:201)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:124)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1366)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1345)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:1153)
> at org.eclipse.swt.widgets.Control.release(Control.java:3988)
> at org.eclipse.swt.widgets.Widget.dispose(Widget.java:479)
> at org.eclipse.swt.widgets.Shell.dispose(Shell.java:2666)
> at org.eclipse.swt.widgets.Shell.closeWidget(Shell.java:670)
> at org.eclipse.swt.widgets.Shell.close(Shell.java:665)
> at org.jboss.tools.browsersim.ui.menu.BrowserSimMenuCreator$9.widgetSelected(BrowserSimMenuCreator.java:263)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4553)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4143)
> at org.jboss.tools.browsersim.ui.launch.BrowserSimRunner.main(BrowserSimRunner.java:127)
> Caused by: java.lang.ClassNotFoundException: javax.servlet.Servlet
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 24 more
> {code}
> So... Maybe another javax.servlet requirement that's not properly defined?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months