July 2019 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22965) CDK tools should work behind proxy

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-22965?page=com.atlassian.jira.plugi... ] André Dietisheim resolved JBIDE-22965. -------------------------------------- Fix Version/s: 4.12.0.Final (was: 4.12.x) Resolution: Rejected > CDK tools should work behind proxy > ---------------------------------- > > Key: JBIDE-22965 > URL: https://issues.jboss.org/browse/JBIDE-22965 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.12.0.Final > > Attachments: create_proxy-test_env.sh > > > Proxy support has been added in CDK vagrant box and in vagrant-registration plugin. > We should make sure our CDK tooling supports it too. > In order to run CDK behind proxy, we need to set environment variables: https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... > Eclipse Proxy Testing link: https://mojo.redhat.com/docs/DOC-989982 > + to create a proxy test environment: https://gist.github.com/LalatenduMohanty/5062050ac78721eda9676bbc15ecfd25 > Standard unix proxy environmet variable $http_proxy has different purpose then $PROXY that CDK uses. Comments from [~lalatendum]: > {noformat} > lalatenduM: we exepect customers workstation is configured to porixy server > that means when you ping subscription-rhn-redhat-com.edge.prod.ext.phx2.redhat.com it should work > lalatenduM: on a customer worksttaion > lalatenduM: now teh challenge is to make openshift , docker and subscription manager in CDK VM aware of proxy server information > lalatenduM: vagrant-registration uses subscription manager for registraton > lalatenduM: whenyou use https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... it will make openshift, docker and vagrant-registration aware of proxy server info > {noformat} > in a mail on the 26th of October 2017 "Re: [openshift-sme] CDK: Usage behind proxy": > {quote} > The CDK supports a number of methods to apply proxy configuration. > You can specify a few of these at startup using the “minishift start” command. > First, you can set the --http-proxy and/or --https-proxy to apply RHEL environment variables. > For Docker Pulls, you can specify environment variables that are applied to the Docker daemon using the --docker-env flag (HTTP_PROXY, HTTPS_PROXY, NO_PROXY). > There are additional considerations for builds as well that can be applied. Please see the following document on the proxy considerations: > https://docs.openshift.com/container-platform/3.6/install_config/http_pro... > - Andy > {quote} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22965) CDK tools should work behind proxy

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-22965?page=com.atlassian.jira.plugi... ] André Dietisheim edited comment on JBIDE-22965 at 7/2/19 11:06 AM: ------------------------------------------------------------------- [~odockal] me thinks that we're not supporting proxies. Even given that CDK4 is soon to be officially release I'd close this as WONT_FIX as I dont expect further work to be done here. was (Author: adietish): [~odockal] me thinks that we're not supporting proxies. Even given that CDK4 is soon to be officially release I'd close this as WONT_FIX. > CDK tools should work behind proxy > ---------------------------------- > > Key: JBIDE-22965 > URL: https://issues.jboss.org/browse/JBIDE-22965 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.12.0.Final > > Attachments: create_proxy-test_env.sh > > > Proxy support has been added in CDK vagrant box and in vagrant-registration plugin. > We should make sure our CDK tooling supports it too. > In order to run CDK behind proxy, we need to set environment variables: https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... > Eclipse Proxy Testing link: https://mojo.redhat.com/docs/DOC-989982 > + to create a proxy test environment: https://gist.github.com/LalatenduMohanty/5062050ac78721eda9676bbc15ecfd25 > Standard unix proxy environmet variable $http_proxy has different purpose then $PROXY that CDK uses. Comments from [~lalatendum]: > {noformat} > lalatenduM: we exepect customers workstation is configured to porixy server > that means when you ping subscription-rhn-redhat-com.edge.prod.ext.phx2.redhat.com it should work > lalatenduM: on a customer worksttaion > lalatenduM: now teh challenge is to make openshift , docker and subscription manager in CDK VM aware of proxy server information > lalatenduM: vagrant-registration uses subscription manager for registraton > lalatenduM: whenyou use https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... it will make openshift, docker and vagrant-registration aware of proxy server info > {noformat} > in a mail on the 26th of October 2017 "Re: [openshift-sme] CDK: Usage behind proxy": > {quote} > The CDK supports a number of methods to apply proxy configuration. > You can specify a few of these at startup using the “minishift start” command. > First, you can set the --http-proxy and/or --https-proxy to apply RHEL environment variables. > For Docker Pulls, you can specify environment variables that are applied to the Docker daemon using the --docker-env flag (HTTP_PROXY, HTTPS_PROXY, NO_PROXY). > There are additional considerations for builds as well that can be applied. Please see the following document on the proxy considerations: > https://docs.openshift.com/container-platform/3.6/install_config/http_pro... > - Andy > {quote} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22965) CDK tools should work behind proxy

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-22965?page=com.atlassian.jira.plugi... ] André Dietisheim commented on JBIDE-22965: ------------------------------------------ [~odockal] me thinks that we're not supporting proxies. Even given that CDK4 is soon to be officially release I'd close this as WONT_FIX. > CDK tools should work behind proxy > ---------------------------------- > > Key: JBIDE-22965 > URL: https://issues.jboss.org/browse/JBIDE-22965 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.12.x > > Attachments: create_proxy-test_env.sh > > > Proxy support has been added in CDK vagrant box and in vagrant-registration plugin. > We should make sure our CDK tooling supports it too. > In order to run CDK behind proxy, we need to set environment variables: https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... > Eclipse Proxy Testing link: https://mojo.redhat.com/docs/DOC-989982 > + to create a proxy test environment: https://gist.github.com/LalatenduMohanty/5062050ac78721eda9676bbc15ecfd25 > Standard unix proxy environmet variable $http_proxy has different purpose then $PROXY that CDK uses. Comments from [~lalatendum]: > {noformat} > lalatenduM: we exepect customers workstation is configured to porixy server > that means when you ping subscription-rhn-redhat-com.edge.prod.ext.phx2.redhat.com it should work > lalatenduM: on a customer worksttaion > lalatenduM: now teh challenge is to make openshift , docker and subscription manager in CDK VM aware of proxy server information > lalatenduM: vagrant-registration uses subscription manager for registraton > lalatenduM: whenyou use https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... it will make openshift, docker and vagrant-registration aware of proxy server info > {noformat} > in a mail on the 26th of October 2017 "Re: [openshift-sme] CDK: Usage behind proxy": > {quote} > The CDK supports a number of methods to apply proxy configuration. > You can specify a few of these at startup using the “minishift start” command. > First, you can set the --http-proxy and/or --https-proxy to apply RHEL environment variables. > For Docker Pulls, you can specify environment variables that are applied to the Docker daemon using the --docker-env flag (HTTP_PROXY, HTTPS_PROXY, NO_PROXY). > There are additional considerations for builds as well that can be applied. Please see the following document on the proxy considerations: > https://docs.openshift.com/container-platform/3.6/install_config/http_pro... > - Andy > {quote} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18526) CordovaSim: Debugger doesn't work properly with the last JDK 8u20

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-18526?page=com.atlassian.jira.plugi... ] André Dietisheim commented on JBIDE-18526: ------------------------------------------ [~odockal], [~jkopriva]: we're now with jdk11 being the official jdk. Nevertheless we're still requiring jdk8 and thus, not sure we can resolve this issue? > CordovaSim: Debugger doesn't work properly with the last JDK 8u20 > ----------------------------------------------------------------- > > Key: JBIDE-18526 > URL: https://issues.jboss.org/browse/JBIDE-18526 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim, upstream > Affects Versions: 4.2.0.CR2 > Environment: Not reproducible with Oracle JDK 7u67 > Affects Oracle JDK 8u20 and above (Not reproducible with JDK 8u5 and 8u11) > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Critical > Labels: upstream > Fix For: 4.12.x > > Attachments: debugger error.png > > > CordovaSim freezes with the following stack trace: > {code} > java.lang.IllegalStateException: Nested event loops are allowed only while handling system events > at com.sun.javafx.tk.quantum.QuantumToolkit.enterNestedEventLoop(QuantumToolkit.java:506) > at com.sun.javafx.webkit.EventLoopImpl.cycle(EventLoopImpl.java:59) > at com.sun.webkit.EventLoop.fwkCycle(EventLoop.java:45) > at com.sun.webkit.Timer.twkFireTimerEvent(Native Method) > at com.sun.webkit.Timer.fireTimerEvent(Timer.java:83) > at com.sun.webkit.Timer.notifyTick(Timer.java:64) > at javafx.scene.web.WebEngine$PulseTimer.lambda$static$44(WebEngine.java:1167) > at javafx.scene.web.WebEngine$PulseTimer$$Lambda$67/10449826.pulse(Unknown Source) > at com.sun.javafx.tk.Toolkit.lambda$runPulse$28(Toolkit.java:314) > at com.sun.javafx.tk.Toolkit$$Lambda$134/26908315.run(Unknown Source) > at java.security.AccessController.doPrivileged(Native Method) > at com.sun.javafx.tk.Toolkit.runPulse(Toolkit.java:313) > at com.sun.javafx.tk.Toolkit.firePulse(Toolkit.java:340) > at com.sun.javafx.tk.quantum.QuantumToolkit.pulse(QuantumToolkit.java:451) > at com.sun.javafx.tk.quantum.QuantumToolkit.pulse(QuantumToolkit.java:431) > at com.sun.javafx.tk.quantum.QuantumToolkit.lambda$runToolkit$363(QuantumToolkit.java:298) > at com.sun.javafx.tk.quantum.QuantumToolkit$$Lambda$40/33541029.run(Unknown Source) > at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) > at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2549) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759) > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.startCordovaSim(CordovaSimRunner.java:114) > at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.main(CordovaSimRunner.java:91) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22678) Run integration-test and report results on incoming Pull Request

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-22678?page=com.atlassian.jira.plugi... ] André Dietisheim edited comment on JBIDE-22678 at 7/2/19 11:03 AM: ------------------------------------------------------------------- [~jkopriva], [~odockal], [~jeffmaury]: all subtasks/linked issues to this seem closed. Can we resolve this old issue? was (Author: adietish): [~jkopriva], [~odockal], [~jeffmaury]: all subtasks to this seem closed. Can we resolve this old issue? > Run integration-test and report results on incoming Pull Request > ---------------------------------------------------------------- > > Key: JBIDE-22678 > URL: https://issues.jboss.org/browse/JBIDE-22678 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, qa > Reporter: Mickael Istria > Assignee: Rastislav Wagner > Priority: Critical > Fix For: 4.12.x > > > It would be interesting to have integraton-tests running on incoming Pull Requests. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22678) Run integration-test and report results on incoming Pull Request

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-22678?page=com.atlassian.jira.plugi... ] André Dietisheim commented on JBIDE-22678: ------------------------------------------ [~jkopriva], [~odockal], [~jeffmaury]: all subtasks to this seem closed. Can we resolve this old issue? > Run integration-test and report results on incoming Pull Request > ---------------------------------------------------------------- > > Key: JBIDE-22678 > URL: https://issues.jboss.org/browse/JBIDE-22678 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, qa > Reporter: Mickael Istria > Assignee: Rastislav Wagner > Priority: Critical > Fix For: 4.12.x > > > It would be interesting to have integraton-tests running on incoming Pull Requests. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26669) Defined basic QE jobs and templates in jenkins-job-dsl repo

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26669?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-26669: ---------------------------------- Component/s: (was: integration-tests) > Defined basic QE jobs and templates in jenkins-job-dsl repo > ----------------------------------------------------------- > > Key: JBIDE-26669 > URL: https://issues.jboss.org/browse/JBIDE-26669 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.12.0.Final > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Labels: dsl, jenkins, jenkins_pipeline, quality > Fix For: 4.12.0.Final > > > Continue work on dev-platform/jenkins-dsl-jobs repo and follow best practices as defined in QE - CI. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18722) Fixing Eclipse/Neon

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-18722?page=com.atlassian.jira.plugi... ] André Dietisheim commented on JBIDE-18722: ------------------------------------------ [~lhein] the 3 upstream bugs listed in the description are still opened and thus should still exist in current Eclipse. > Fixing Eclipse/Neon > ------------------- > > Key: JBIDE-18722 > URL: https://issues.jboss.org/browse/JBIDE-18722 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: upstream > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 4.12.x > > > "container" issue for issues related to fixes important to get into Luna. > Please link your Eclipse/Mars issue to this one instead of using subtasks (edit this description). > Current open WTP bugs with patches waiting to be applied (copy from original issue without fixed): > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=398568 target: Future > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=431910 show in console. target: none > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=318670 - [Workbench] Not all settings copied when switching workspace and "Copy settings" marked -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22145) nio WatchService possibly causing errors / locking files on windows

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-22145?page=com.atlassian.jira.plugi... ] André Dietisheim commented on JBIDE-22145: ------------------------------------------ [~rob.stryker] we're now at java 11 being the standard jdk, does this still exist? > nio WatchService possibly causing errors / locking files on windows > ------------------------------------------------------------------- > > Key: JBIDE-22145 > URL: https://issues.jboss.org/browse/JBIDE-22145 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Final > Environment: - Windows 7 x64 > - jdk1.8.0_77 (32-bit) > - Eclipse Mars.2 (32-bit) > - JBoss Tools 4.3.0.FINAL > - Wildfly 10.0.0.FINAL > Reporter: Tobias van den Berg > Assignee: Thomas Mäder > Priority: Critical > Fix For: 4.12.x > > Attachments: FSWatcherHang.txt, FailureWatchModify1.PML, FileWatchError.zip, Logfile.PML, OkWatchModify1.PML > > > The following error is thrown after publishing a maven webapplication (.war) to Wildfly 10.0: > "Error renaming C:\wildfly-10.0.0.Final\standalone\tmp\tmp8945090880188299781.properties to C:\wildfly-10.0.0.Final\standalone\deployments\WebViewer-0.0.3-SNAPSHOT.war\META-INF\maven\nl.incad.webviewer\WebViewer\pom.properties. > This may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination. > You may adjust these settings in the server editor." > The webapplication is no longer available/online after the error. The only solution is to restart the server and to re-add the webapplication to the server. This makes it very hard to develop/test a webapplication on wildfly 10. The same error is thrown on wildfly 8.0/8.1, but the difference is that the webapplication is still available/online after the error. > I've tried/tested the following: > - Checked/updated Windows file permisions for the wildfly directory > - Take ownership of the wildfly directory (recursively) > - Disabled Windows User Account Control (UAC) > - Run Eclipse as Admin > Relates to: > - JBIDE-18697 > - JBIDE-17545 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26669) Defined basic QE jobs and templates in jenkins-job-dsl repo

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26669?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-26669: --------------------------------------- No, since best practices were not yet fully defined and closed. > Defined basic QE jobs and templates in jenkins-job-dsl repo > ----------------------------------------------------------- > > Key: JBIDE-26669 > URL: https://issues.jboss.org/browse/JBIDE-26669 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.12.0.Final > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Labels: dsl, jenkins, jenkins_pipeline, quality > Fix For: 4.12.0.Final > > > Continue work on dev-platform/jenkins-dsl-jobs repo and follow best practices as defined in QE - CI. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2019