[JBoss JIRA] (JBIDE-23565) Add mechanism for detecting if internal browser is able to communicate with eclipse.
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23565?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23565:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Add mechanism for detecting if internal browser is able to communicate with eclipse.
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-23565
> URL: https://issues.jboss.org/browse/JBIDE-23565
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.4.2.Final
> Reporter: Radim Hopp
> Assignee: Snjezana Peco
> Fix For: 4.6.x
>
>
> Context: I have fresh installation of Fedora 25 (KDE spin). In that installation, webkitgtk3 is not installed by default. As a result of this, Central in eclipse is behaving exactly the same as in normal web browser (only some forge example is displayed (no archetypes) and when this example is clicked on, popup (this one: https://github.com/jbosstools/jbosstools-central-webpage/blob/master/src/...) pops up instead of wizard). This leaves Central unusable.
> Installing webkitgtk3 solved this issue, but it would be great if Central had some mechanism for detecting this and in case it is not able to communicate with eclipse instance it could throw recommendation for user to check if he has webkitgtk3 installed.
> Maybe also document this requirement?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-23489) Find out how to run mvn clean verify -Dtest.installBase=path/to/devstudio/rpm
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23489?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23489:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Find out how to run mvn clean verify -Dtest.installBase=path/to/devstudio/rpm
> ------------------------------------------------------------------------------
>
> Key: JBIDE-23489
> URL: https://issues.jboss.org/browse/JBIDE-23489
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, integration-tests, qa
> Affects Versions: 4.4.2.AM3
> Reporter: Pavol Srna
> Assignee: Vojtech Prusa
> Fix For: 4.6.x
>
> Attachments: FreeMarket_rhscl_enabled.log, Freemarker_testRuntime_p2Installed.log
>
>
> We need to find a way how to run automated tests agains devstudio rpm.
> I've tried the following paths:
> 1) (as root) mvn clean verify -Dtest.installBase=/opt/rh/rh-eclipse46/root/usr/shareclipse/droplets/devstudio/eclipse/
> 2) (as hudson) mvn clean verify -Dtest.installBase=~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64
> But none of the above works.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-22953) FileNotFoundException below CordovaPluginXmlUtil.getPluginsfromFiles (thrown in FileInputStream.open0)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22953?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22953:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> FileNotFoundException below CordovaPluginXmlUtil.getPluginsfromFiles (thrown in FileInputStream.open0)
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22953
> URL: https://issues.jboss.org/browse/JBIDE-22953
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cordovasim
> Reporter: Automated Error Reporting Bot
> Assignee: Ilya Buziuk
> Fix For: 4.6.x
>
>
> The following problem was reported via the automated error reporting:
> Message: java.io.FileNotFoundException: C:\vso-tfs\CareTrail\StatChat\plugins\cordova-plugin-ionic-keyboard\plugin.xml (The system cannot find the file specified)
> {noformat}
> java.io.FileNotFoundException: C:\vso-tfs\CareTrail\StatChat\plugins\cordova-plugin-ionic-keyboard\plugin.xml (The system cannot find the file specified)
> at java.io.FileInputStream.open0(null:-2)
> at java.io.FileInputStream.open(null:-1)
> at java.io.FileInputStream.<init>(null:-1)
> at java.io.FileInputStream.<init>(null:-1)
> at sun.net.www.protocol.file.FileURLConnection.connect(null:-1)
> at sun.net.www.protocol.file.FileURLConnection.getInputStream(null:-1)
> at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(null:-1)
> at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(null:-1)
> at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(null:-1)
> at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(null:-1)
> at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(null:-1)
> at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(null:-1)
> at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(null:-1)
> at javax.xml.parsers.DocumentBuilder.parse(null:-1)
> at org.jboss.tools.cordovasim.eclipse.internal.util.CordovaPluginXmlUtil.getPluginsfromFiles(CordovaPluginXmlUtil.java:83)
> at org.jboss.tools.cordovasim.eclipse.servlet.internal.CordovaPluginJsServlet.doGet(CordovaPluginJsServlet.java:55)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:808)
> at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587)
> at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:221)
> at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
> at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
> at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
> at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
> at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
> at org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:332)
> at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
> at org.eclipse.jetty.server.Server.handle(Server.java:499)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310)
> at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)
> at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
> at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
> at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
> at java.lang.Thread.run(null:-1)
> {noformat}
> Bundles:
> | javax.servlet | 3.1.0.v201410161800 | 3.1.0.v201410161800 |
> | javax.xml | 1.3.4.v201005080400 | 1.3.4.v201005080400 |
> | org.eclipse.jetty.io | 9.2.13.v20150730 | 9.2.13.v20150730 |
> | org.eclipse.jetty.rewrite | 9.2.13.v20150730 | 9.2.13.v20150730 |
> | org.eclipse.jetty.server | 9.2.13.v20150730 | 9.2.13.v20150730 |
> | org.eclipse.jetty.servlet | 9.2.13.v20150730 | 9.2.13.v20150730 |
> | org.eclipse.jetty.util | 9.2.13.v20150730 | 9.2.13.v20150730 |
> | org.jboss.tools.cordovasim.eclipse | 3.7.1.Final-v20160331-0435-B86 | 3.7.1.Final-v20160331-0435-B86 |
> Operating Systems:
> | Windows | 10.0.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5772820ce4b03c6ed0...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-22918) RuntimeException below DomUtil.nodeToString (thrown in SerializerBase.getNamespaceURI)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22918?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22918:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> RuntimeException below DomUtil.nodeToString (thrown in SerializerBase.getNamespaceURI)
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-22918
> URL: https://issues.jboss.org/browse/JBIDE-22918
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Reporter: Automated Error Reporting Bot
> Assignee: Ilya Buziuk
> Fix For: 4.6.x
>
>
> The following problem was reported via the automated error reporting:
> Message: HIDDEN
> {noformat}
> java.lang.RuntimeException: HIDDEN
> at com.sun.org.apache.xml.internal.serializer.SerializerBase.getNamespaceURI(null:-1)
> at com.sun.org.apache.xml.internal.serializer.SerializerBase.addAttribute(null:-1)
> at com.sun.org.apache.xml.internal.serializer.ToUnknownStream.addAttribute(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transformIdentity(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(null:-1)
> at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(null:-1)
> at org.jboss.tools.vpe.preview.core.transform.DomUtil.nodeToString(DomUtil.java:45)
> at org.jboss.tools.vpe.preview.core.transform.VpvController.getResource(VpvController.java:84)
> at org.jboss.tools.vpe.preview.core.server.VpvSocketProcessor.processRequest(VpvSocketProcessor.java:83)
> at org.jboss.tools.vpe.preview.core.server.VpvSocketProcessor.run(VpvSocketProcessor.java:68)
> at java.lang.Thread.run(null:-1)
> {noformat}
> Bundles:
> | org.jboss.tools.vpe.preview.core | 3.7.1.Final-v20160331-0327-B91 | 3.8.0.Final-v20160609-2229-B3 |
> Operating Systems:
> | Linux | 3.19.0 | 4.2.0 |
> | MacOSX | 10.11.4 | 10.11.4 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/56fcda44e4b08ccb7b...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-24777) Creating an application from project should allow to connect project to Git if missing
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24777?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24777:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Creating an application from project should allow to connect project to Git if missing
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-24777
> URL: https://issues.jboss.org/browse/JBIDE-24777
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Mickael Istria
> Fix For: 4.6.x
>
>
> Using Red Hat Developer Studio 11.0.AM2.
> I'm trying to deploy a new project to OpenShift (Online). As this project is new, it's not connected to any Git repo.
> When going through the wizards to create an application, the wizard shows an error message because project isn't connected to Git. The only way to connect to Git is to quit the current OpenShift wizard, use the Git wizards to connect project and then re-open the OpenShift wizard.
> I believe a better workflow would be to show in the error message or in the wizard a link to connect the selected repo to Git if it's missing. Then the workflow is more linear and progressive so it's easier for user to move forward.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-23660) CDK Server adapter should have an option to configure stop command
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23660?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23660:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> CDK Server adapter should have an option to configure stop command
> ------------------------------------------------------------------
>
> Key: JBIDE-23660
> URL: https://issues.jboss.org/browse/JBIDE-23660
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: cdk
> Affects Versions: 4.4.2.Final
> Reporter: Ricardo Martinelli Oliveira
> Assignee: Rob Stryker
> Fix For: 4.6.x
>
>
> CDK Server adapter lets configure the vagrant startup options. There should have an option to do the same in the stop.
> Why?
> It seems that CDK Server adapter uses _vagrant destroy_ to stop CDK, but using that option has its drawbacks, like for example:
> * If I'm stopping it to save resources, then I'm loosing all my job in it.
> * All images already pulled will be lost, so I cannot work offline
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-22277) Connection wizard: Auto guess Openshift connections
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22277?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22277:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Connection wizard: Auto guess Openshift connections
> ---------------------------------------------------
>
> Key: JBIDE-22277
> URL: https://issues.jboss.org/browse/JBIDE-22277
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Jeff MAURY
> Priority: Minor
> Labels: connection_wizard, new_and_noteworthy, openshift_v3
> Fix For: 4.6.x
>
>
> When creating a new Openshift connection, it would be possible to provide default values for the differents fields by looking at the $HOME/.kube/config YAML files that stores various Openshift installations the user has been connected to through the Openshift oc client.
> The same feature exists in the Docker tooling so this might be interesting to have the same at the Openshift side.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months