[JBoss JIRA] (JBIDE-15793) Cordova Feature multiselection is not working
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15793?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-15793:
-------------------------------------
Could be for me it's not working because if you select Cancel button it's not added properly and Cordova Configuration Editor gets broken https://issues.jboss.org/browse/JBIDE-15843
For me it's almost the same situation as before this fix. User selects more Plug-ins and they are not added if he says Cancel to Overwrite Files. It's improvement because if he says Yes to all Plug-Ins are added but I don't like how it's fixed because after some adding/removing plugins Cordova Configuration Editor seems to be confused.
I can close this Jira because I already reported https://issues.jboss.org/browse/JBIDE-15843 so malfunction of Cordova Feature Multiselection is recorded properly in Jira.
So [~maxandersen] should I close this one?
> Cordova Feature multiselection is not working
> ---------------------------------------------
>
> Key: JBIDE-15793
> URL: https://issues.jboss.org/browse/JBIDE-15793
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Environment: JBT 4.1.1 Beta1-v20131020-0207-B454
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Labels: respin-b
> Fix For: 4.1.1.Beta1
>
> Attachments: overwritefilesdialog.png
>
>
> 1. Create new Hybrid Mobile project
> 2. Open config.xml file via Cordova Configuration Editor
> 3. Choose Add.. to add features, select more than one feature and click Finish
> ERROR: Only first selected feature is added to project and to config.xml file
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15835) Timeout when add/remove postgresql cartridge to application (Openshift Enterprise)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15835?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-15835:
------------------------------------------
IMHO all the errors you saw with our internal OSE (OpenShift Enterprise) instance show far worse performance/responsiveness compared to OpenShift Online. This is IMHO not OSE specific but caused by the infrastructure this instance is running on/in.
I checked our code and I see us embedding with default timeout values whereas application creation is using a specific timeout. What we could do here is increasing the embedding timeout. What makes me doubt about it is that OpenShift Online (in the current setup) does not need it. Increasing timeouts is always having users eventually blocked for more time.
> Timeout when add/remove postgresql cartridge to application (Openshift Enterprise)
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-15835
> URL: https://issues.jboss.org/browse/JBIDE-15835
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
>
> Attempt to add to existing (or can be added when creating new) application PostgreSQL database cartridge cause connection time out. Dialog with text
> {code}Could not request url https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati..., connection timed out {code} is shown.
> Finally, cartridge seems to be added correctly (seems to be embedded well, environment variables are correctly set up for the given cartridge etc.)
> This happens only on Openshift Enterprise (Openshift Online works fine)
> Eclipse log:
> {code}
> !ENTRY org.jboss.tools.openshift.express.ui 4 0 2013-11-01 12:54:14.209
> !MESSAGE Could not embed cartridges for application dasda
> !STACK 0
> com.openshift.client.OpenShiftTimeoutException: Could not request url https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati..., connection timed out
> at com.openshift.internal.client.RestService.request(RestService.java:139)
> at com.openshift.internal.client.RestService.request(RestService.java:109)
> at com.openshift.internal.client.RestService.request(RestService.java:92)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:142)
> at com.openshift.internal.client.ApplicationResource$AddEmbeddedCartridgeRequest.execute(ApplicationResource.java:1026)
> at com.openshift.internal.client.ApplicationResource.addEmbeddableCartridge(ApplicationResource.java:353)
> at com.openshift.internal.client.ApplicationResource.addEmbeddableCartridges(ApplicationResource.java:368)
> at org.jboss.tools.openshift.express.internal.ui.job.EmbedCartridgesJob.addEmbeddedCartridges(EmbedCartridgesJob.java:94)
> at org.jboss.tools.openshift.express.internal.ui.job.EmbedCartridgesJob.doRun(EmbedCartridgesJob.java:56)
> at org.jboss.tools.openshift.express.internal.ui.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Caused by: java.net.SocketTimeoutException: Read timed out
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(SocketInputStream.java:150)
> at java.net.SocketInputStream.read(SocketInputStream.java:121)
> at sun.security.ssl.InputRecord.readFully(InputRecord.java:442)
> at sun.security.ssl.InputRecord.read(InputRecord.java:480)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:927)
> at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:884)
> at sun.security.ssl.AppInputStream.read(AppInputStream.java:102)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:275)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:334)
> at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:633)
> at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:579)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1322)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:146)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:125)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:101)
> at com.openshift.internal.client.RestService.request(RestService.java:179)
> at com.openshift.internal.client.RestService.request(RestService.java:123)
> ... 10 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15835) Timeout when add/remove postgresql cartridge to application (Openshift Enterprise)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15835?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-15835:
----------------------------------------
Assignee: Max Rydahl Andersen (was: Andre Dietisheim)
[~maxandersen] plz comment
> Timeout when add/remove postgresql cartridge to application (Openshift Enterprise)
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-15835
> URL: https://issues.jboss.org/browse/JBIDE-15835
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Marián Labuda
> Assignee: Max Rydahl Andersen
>
> Attempt to add to existing (or can be added when creating new) application PostgreSQL database cartridge cause connection time out. Dialog with text
> {code}Could not request url https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati..., connection timed out {code} is shown.
> Finally, cartridge seems to be added correctly (seems to be embedded well, environment variables are correctly set up for the given cartridge etc.)
> This happens only on Openshift Enterprise (Openshift Online works fine)
> Eclipse log:
> {code}
> !ENTRY org.jboss.tools.openshift.express.ui 4 0 2013-11-01 12:54:14.209
> !MESSAGE Could not embed cartridges for application dasda
> !STACK 0
> com.openshift.client.OpenShiftTimeoutException: Could not request url https://console.itos.redhat.com/broker/rest/domains/domainequo2/applicati..., connection timed out
> at com.openshift.internal.client.RestService.request(RestService.java:139)
> at com.openshift.internal.client.RestService.request(RestService.java:109)
> at com.openshift.internal.client.RestService.request(RestService.java:92)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:142)
> at com.openshift.internal.client.ApplicationResource$AddEmbeddedCartridgeRequest.execute(ApplicationResource.java:1026)
> at com.openshift.internal.client.ApplicationResource.addEmbeddableCartridge(ApplicationResource.java:353)
> at com.openshift.internal.client.ApplicationResource.addEmbeddableCartridges(ApplicationResource.java:368)
> at org.jboss.tools.openshift.express.internal.ui.job.EmbedCartridgesJob.addEmbeddedCartridges(EmbedCartridgesJob.java:94)
> at org.jboss.tools.openshift.express.internal.ui.job.EmbedCartridgesJob.doRun(EmbedCartridgesJob.java:56)
> at org.jboss.tools.openshift.express.internal.ui.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Caused by: java.net.SocketTimeoutException: Read timed out
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(SocketInputStream.java:150)
> at java.net.SocketInputStream.read(SocketInputStream.java:121)
> at sun.security.ssl.InputRecord.readFully(InputRecord.java:442)
> at sun.security.ssl.InputRecord.read(InputRecord.java:480)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:927)
> at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:884)
> at sun.security.ssl.AppInputStream.read(AppInputStream.java:102)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:275)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:334)
> at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:633)
> at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:579)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1322)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:146)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:125)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.post(UrlConnectionHttpClient.java:101)
> at com.openshift.internal.client.RestService.request(RestService.java:179)
> at com.openshift.internal.client.RestService.request(RestService.java:123)
> ... 10 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15612) install-grinder gets stuck after installing JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15612?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-15612:
------------------------------------
Yes, seems like the issue is either:
* Jenkins -> http requests to -> www.qa, or
* Jenkins -> http requests to -> devstudio.jb
Since the Central site used to perform the install tests contains links to both servers.
Whereas for the JBT Central install tests, everything points to dl.jb.org, and the tests never timeout/stall.
> install-grinder gets stuck after installing JBDS
> ------------------------------------------------
>
> Key: JBIDE-15612
> URL: https://issues.jboss.org/browse/JBIDE-15612
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: qa
> Affects Versions: 4.1.1.Alpha2
> Reporter: Nick Boldt
> Assignee: Pavol Srna
> Fix For: 4.1.1.Beta1, 4.1.1.CR1
>
> Attachments: install-grinder-gets-stuck.png
>
>
> Seems that the prompt at the end of the installation of JBDS is not being caught and clicked by the install grinder, so the eclipse instance stays open forever (until the job times out).
> Steps to reproduce locally:
> {code}
> # as root, install these if not already installed
> yum install tigervnc.x86_64 tigervnc-server.x86_64 vinagre -y
> exit
> # in a terminal, run this:
> vncserver
> # then launch vinagre to connect to the VNC session:
> vinagre localhost:1
> # within the VNC session, run this:
> git clone https://github.com/jbosstools/jbosstools-install-grinder/
> cd jbosstools-install-grinder
> mvn org.apache.maven.plugins:maven-dependency-plugin:2.7:unpack \
> -Dartifact=org.jboss.tools.installation-tests:scripts:4.1.0.Beta1-SNAPSHOT:zip:delivery
> cd scripts/target/scripts-*-delivery/
> SCRIPTDIR=`pwd`
> WORKSPACE=/tmp/jbtcentraltarget-verify
> rm -fr ${WORKSPACE}; mkdir -p ${WORKSPACE}; cd ${WORKSPACE}
> # must be lowercase kepler
> eclipseBundleVersion=kepler.R
> # or
> eclipseBundleVersion=kepler.SR1
> # path to where you store eclipse tar.gz files
> eclipseCacheDirectory=${HOME}/tmp/Eclipse_Bundles
> groovy ${SCRIPTDIR}/getAndInstallEclipse.groovy \
> eclipseCacheDirectory=${eclipseCacheDirectory} \
> eclipseBundleVersion=${eclipseBundleVersion}
> INSTALL_PLAN="http://download.jboss.org/jbosstools/discovery/nightly/core/trunk/;http:/..."
> # or
> INSTALL_PLAN="http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/trunk/;http:..."
> groovy ${SCRIPTDIR}/testInstall.groovy ${WORKSPACE}/eclipse/ $INSTALL_PLAN
> {code}
> Here's a screenshot:
> !install-grinder-gets-stuck.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15612) install-grinder gets stuck after installing JBDS
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15612?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-15612:
----------------------------------------
This seems to be very dependent of network and other slave performances as tests succeed in 40% of cases. Anyway, the timeout should be increased and made configurable to overcome those failing cases.
> install-grinder gets stuck after installing JBDS
> ------------------------------------------------
>
> Key: JBIDE-15612
> URL: https://issues.jboss.org/browse/JBIDE-15612
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: qa
> Affects Versions: 4.1.1.Alpha2
> Reporter: Nick Boldt
> Assignee: Pavol Srna
> Fix For: 4.1.1.Beta1, 4.1.1.CR1
>
> Attachments: install-grinder-gets-stuck.png
>
>
> Seems that the prompt at the end of the installation of JBDS is not being caught and clicked by the install grinder, so the eclipse instance stays open forever (until the job times out).
> Steps to reproduce locally:
> {code}
> # as root, install these if not already installed
> yum install tigervnc.x86_64 tigervnc-server.x86_64 vinagre -y
> exit
> # in a terminal, run this:
> vncserver
> # then launch vinagre to connect to the VNC session:
> vinagre localhost:1
> # within the VNC session, run this:
> git clone https://github.com/jbosstools/jbosstools-install-grinder/
> cd jbosstools-install-grinder
> mvn org.apache.maven.plugins:maven-dependency-plugin:2.7:unpack \
> -Dartifact=org.jboss.tools.installation-tests:scripts:4.1.0.Beta1-SNAPSHOT:zip:delivery
> cd scripts/target/scripts-*-delivery/
> SCRIPTDIR=`pwd`
> WORKSPACE=/tmp/jbtcentraltarget-verify
> rm -fr ${WORKSPACE}; mkdir -p ${WORKSPACE}; cd ${WORKSPACE}
> # must be lowercase kepler
> eclipseBundleVersion=kepler.R
> # or
> eclipseBundleVersion=kepler.SR1
> # path to where you store eclipse tar.gz files
> eclipseCacheDirectory=${HOME}/tmp/Eclipse_Bundles
> groovy ${SCRIPTDIR}/getAndInstallEclipse.groovy \
> eclipseCacheDirectory=${eclipseCacheDirectory} \
> eclipseBundleVersion=${eclipseBundleVersion}
> INSTALL_PLAN="http://download.jboss.org/jbosstools/discovery/nightly/core/trunk/;http:/..."
> # or
> INSTALL_PLAN="http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/trunk/;http:..."
> groovy ${SCRIPTDIR}/testInstall.groovy ${WORKSPACE}/eclipse/ $INSTALL_PLAN
> {code}
> Here's a screenshot:
> !install-grinder-gets-stuck.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15802) Unable to import Cordova Plugin from Git
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15802?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-15802.
-------------------------------
Verified with JBDS7.1.0.Beta1b Beta1-v20131102-1529-B493
> Unable to import Cordova Plugin from Git
> ----------------------------------------
>
> Key: JBIDE-15802
> URL: https://issues.jboss.org/browse/JBIDE-15802
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Environment: JBT 4.1.1 Beta1-v20131020-0207-B454
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Labels: respin-b
> Fix For: 4.1.1.Beta1
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> 1. Create Hybrid Mobile project
> 2. Open config.xml in Corodova Configuration editor
> 3. Click on button Add.. to add Feature
> 4. Click on Git tab of Cordova Plugins Discovery dialog
> 5. Write some Plugins git repo to URL text
> ERROR: Finish button is always disabled so it's not possible to add Plugin from Git repo
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBDS-2818) Text in Early Access and Update page needs minor editing
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2818?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2818:
----------------------------------
Confused by some of your suggested changes.
On line https://github.com/jbdevstudio/jbdevstudio-website/pull/45/files#diff-5c4... you changed "JBDS" to "JBoss Developer Studio" per the branding guidelines for the abbreviated name usage. This is good.
But on line https://github.com/jbdevstudio/jbdevstudio-website/pull/45/files#diff-3f4... you changed "installer" to "JBDS universal installer", which reverts to using the no-longer acceptable "JBDS" abbreviation, and adds "universal" which is not needed any more than "for your platform" is.
You also change "Double-click the installer file to run it, or open a terminal and type" to "To start the installer, double-click the installer file or in a CLI enter" ... surely "open a terminal" is more Windows user friendly than "in a CLI" ? Would "To start the installer, double-click the installer file or open a *console* and in it type ... " be better?
I also see that you've added more occurrences of "Red Hat JBoss Developer Studio" so that there are more than 1 per page, eg., on https://github.com/jbdevstudio/jbdevstudio-website/pull/45/files#diff-035... - I thought we only needed the full name for the first occurrence on the page, and could use the simplified/abbreviated "JBoss Developer Studio" for subsequent instances?
> Text in Early Access and Update page needs minor editing
> --------------------------------------------------------
>
> Key: JBDS-2818
> URL: https://issues.jboss.org/browse/JBDS-2818
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: documentation
> Affects Versions: 7.0.1.GA
> Reporter: Michelle Murray
> Assignee: Nick Boldt
> Fix For: 7.1.0.Beta1
>
>
> Both of these templates need the text modifying (to fit Red Hat writing style and 508 compliance):
> https://devstudio.jboss.com/updates/7.0/
> https://devstudio.jboss.com/earlyaccess/7.0.0.GA.html
> *Common text modifications:*
> * Section "Installation :: Core Tooling"
> {quote}
> 1. If not already installed, download and install Oracle JDK or OpenJDK 7 (or 6).
> 2. Download the JBDS universal installer from <link>.
> 3. To start the installer, double-click the installer file or in a CLI enter java -jar jbdevstudio-*.jar
> {quote}
> * Section "Looking for JBoss EAP ..."
> Logo has changed, now just logotype. Looking for link.
> * Section "Getting Started Guide:"
> {quote}
> Adding *JBoss* EAP to JBDS
> {quote}
> *Early Access text modifications:*
> * Title should be "*Red Hat* JBoss Developer Studio ......"
> * Intro text
> {quote}
> We wish to give customers and users early access to *JBoss Developer Studio* so *that* we can make the next version of JBoss Developer Studio an even better environment for developing with and for Red Hat JBoss Middleware.
> {quote}
> *Updates text modifications*
> * Why do we have this text? I ask because, for example, in https://devstudio.jboss.com/updates/7.0/, on the right-hand side the "installer" link in installation step 2 takes you to https://devstudio.jboss.com/earlyaccess/7.0.0.GA.html where you can download what looks like the GA version without subscription or opting in to a trial. Also you can get JBDS BYOE without subscription or trial on Eclipse marketplace. Seems the text is outdated but I don't know all the ins and outs of JBDS marketing and alike - hence asking the question.
> {quote}
> If you do not already have a copy of JBoss Developer Studio, you can purchase a subscription or get a
> 30-day Free Trial from here: https://access.redhat.com/downloads/.
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months