October 2016 - jbosstools-issues - Jboss List Archives

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

by Lalatendu Mohanty (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22965?page=com.atlassian.jira.plugi... ] Lalatendu Mohanty commented on JBIDE-22965: ------------------------------------------- Also I have not tested the proxy on Windows. We can ask CDK QE how they did it. If we do not get an answer we need to find out firewall rules to imitate a proxy setup. > 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.4.2.AM2 > > 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} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

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

by Lalatendu Mohanty (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22965?page=com.atlassian.jira.plugi... ] Lalatendu Mohanty commented on JBIDE-22965: ------------------------------------------- [~jeffmaury] [~dbocharov] In a typical proxy setup only http/https access restricted and need to go through proxy. The other traffic like DNS are allowed. For the Prudential proxy setup issue , I am not sure how they are handling DNS. I will ask the question to CEE and find out how they resolve DNS. > 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.4.2.AM2 > > 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} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22816) Create application from image (or builder) may lead to update being detected

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22816?page=com.atlassian.jira.plugi... ] Jeff MAURY edited comment on JBIDE-22816 at 10/7/16 6:59 AM: ------------------------------------------------------------- I think this is fixed by JBIDE-23210. Will check was (Author: jeffmaury): I think this is fixed by JBIDE-2310. Will check > Create application from image (or builder) may lead to update being detected > ---------------------------------------------------------------------------- > > Key: JBIDE-22816 > URL: https://issues.jboss.org/browse/JBIDE-22816 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Fix For: 4.4.2.AM2 > > > When creating a new application from image or builder, an update may be detected and no resources being created. The pb is that the model is set to the Openshift project and asynchronously updated the get the list of projects that will set the Openshift project to the first thus misleading the rest of the processing -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22816) Create application from image (or builder) may lead to update being detected

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22816?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22816: ------------------------------------ I think this is fixed by JBIDE-2310. Will check > Create application from image (or builder) may lead to update being detected > ---------------------------------------------------------------------------- > > Key: JBIDE-22816 > URL: https://issues.jboss.org/browse/JBIDE-22816 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Fix For: 4.4.2.AM2 > > > When creating a new application from image or builder, an update may be detected and no resources being created. The pb is that the model is set to the Openshift project and asynchronously updated the get the list of projects that will set the Openshift project to the first thus misleading the rest of the processing -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4070) DevStudio / external OpenShift fails deployment

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBDS-4070?page=com.atlassian.jira.plugin.... ] Jeff MAURY updated JBDS-4070: ----------------------------- Fix Version/s: 10.2.0.AM3 > DevStudio / external OpenShift fails deployment > ----------------------------------------------- > > Key: JBDS-4070 > URL: https://issues.jboss.org/browse/JBDS-4070 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: openshift > Affects Versions: 10.1.0.GA > Environment: DevStudio as used with an external OpenShift > Reporter: Rick Wagner > Assignee: Jeff MAURY > Fix For: 10.2.0.AM3 > > > If DevStudio (with Server Adapter configured for external OpenShift) is used to deploy an application developed in DevStudio, errors result. > The reporting user shows indications additional 'deploy' directories are being synthesized as the binary target location. The log reports: > 15:59:41,588 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) WFLYDS0010: Scan found incompletely copied file content for deployment /opt/eap/standalone/deployments/deploy/deploy/deploy/deploy/deploy/deploy/activemq-rar.rar. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23127) blog about the improvements RH Eclipse teams did to Neon

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23127?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-23127: ----------------------------------- Fix Version/s: 4.4.2.AM1 > blog about the improvements RH Eclipse teams did to Neon > -------------------------------------------------------- > > Key: JBIDE-23127 > URL: https://issues.jboss.org/browse/JBIDE-23127 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.4.2.AM1 > > > Neon is out and we did a lot of great stuff in the platform > around smart import, auto download of extensions, zoom, etc. > I thought it would be great to do a blog posting about this work > on tools.jboss.org for the Eclipse Neon release > Audience: users of Eclipse and making internal and external to Red Hat aware of the improvements made. > The target would be http://developers.redhat.com/blog > _The following is the current ToC of the blog, it's going to evolve as content is gathered_ > Neon.0: > * JavaScript plugins and “Eclipse for JavaScript Developers” package > * JSon Editor > * Docker Tools > * Vagrant Tools > * Smarter and easier Import of projects in the IDE > * Zoom In/Out with Ctrl+/Ctrl- in text editors > * Discovery and proposal of Marketplace extensions for unknown file types > * SWT on GTK3 > * Theming off > For Neon.1 - released September 28th: > * More Docker: https://wiki.eclipse.org/Linux_Tools_Project/News/NewIn51 > * Image viewer in the Eclipse IDE > For Eclipse Oxygen, next major release to be shipped in June 2018, here are our plans: > * generic and extensible code editor > * Integration with the language server protocol > * UI/UX efforts -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23127) blog about the improvements RH Eclipse teams did to Neon

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23127?page=com.atlassian.jira.plugi... ] Mickael Istria closed JBIDE-23127. ---------------------------------- Resolution: Done Done with http://developers.redhat.com/blog/2016/10/03/red-hat-and-eclipse-ide-look... > blog about the improvements RH Eclipse teams did to Neon > -------------------------------------------------------- > > Key: JBIDE-23127 > URL: https://issues.jboss.org/browse/JBIDE-23127 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.4.2.AM1 > > > Neon is out and we did a lot of great stuff in the platform > around smart import, auto download of extensions, zoom, etc. > I thought it would be great to do a blog posting about this work > on tools.jboss.org for the Eclipse Neon release > Audience: users of Eclipse and making internal and external to Red Hat aware of the improvements made. > The target would be http://developers.redhat.com/blog > _The following is the current ToC of the blog, it's going to evolve as content is gathered_ > Neon.0: > * JavaScript plugins and “Eclipse for JavaScript Developers” package > * JSon Editor > * Docker Tools > * Vagrant Tools > * Smarter and easier Import of projects in the IDE > * Zoom In/Out with Ctrl+/Ctrl- in text editors > * Discovery and proposal of Marketplace extensions for unknown file types > * SWT on GTK3 > * Theming off > For Neon.1 - released September 28th: > * More Docker: https://wiki.eclipse.org/Linux_Tools_Project/News/NewIn51 > * Image viewer in the Eclipse IDE > For Eclipse Oxygen, next major release to be shipped in June 2018, here are our plans: > * generic and extensible code editor > * Integration with the language server protocol > * UI/UX efforts -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4077) Cannot run integration tests against Devstudio with latest target platform

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-4077?page=com.atlassian.jira.plugin.... ] Marián Labuda edited comment on JBDS-4077 at 10/7/16 3:51 AM: -------------------------------------------------------------- Nope, I did this: {code}mvn clean verify -Dtest.installBase=/home/mlabuda/testing/wtf/1006/studio -Dopenshift.username=openshift-dev -Dopenshift.password=devel -Dopenshift.server=https://10.1.2.3:8443 -Dscope=3 -DskipTests=false{code} OpenShift tests need configuration - credentials, scope ("2", "3", "2Smoke" or "3Smoke"). The reason why you get tycho failure is because of scope. Tests got running but fail because of broken Eclipse. was (Author: mlabuda): Nope, I did this: {code}mvn clean verify -Dtest.installBase=/home/mlabuda/testing/wtf/1006/studio -Dopenshift.username=openshift-dev -Dopenshift.password=devel -Dopenshift.server=https://10.1.2.3:8443 -Dscope=3 -DskipTests=false{code} OpenShift tests need configuration - credentials, scope ("2", "3", "2Smoke" or "3Smoke"). The reason why you get tycho failure is because of scope.. > Cannot run integration tests against Devstudio with latest target platform > -------------------------------------------------------------------------- > > Key: JBDS-4077 > URL: https://issues.jboss.org/browse/JBDS-4077 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 10.2.0.AM1 > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Blocker > Attachments: .log, jbosstools-integration-tests.log.txt.zip, org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.txt, org.jboss.tools.deltaspike.ui.bot.test.log.txt, org.jboss.tools.deltaspike.ui.bot.test.log_0.txt, Screenshot_2016-10-05_10-00-03.png, Screenshot_2016-10-05_10-00-21.png, Screenshot_2016-10-05_10-00-28.png, Screenshot_2016-10-05_10-00-57.png, Screenshot_2016-10-05_10-01-14.png, Screenshot_2016-10-05_10-01-32.png, shell.png, TEST-org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.xml, tpfail.png > > > Integration tests run from maven against Devstudio, which was built using the latest target platform (4.61.0.AM1-SNAPSHOT), cannot properly launch all the plugins and fail afterwards. > A full devstudio should open when the tests are run. Instead it looks like this: > !tpfail.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4077) Cannot run integration tests against Devstudio with latest target platform

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-4077?page=com.atlassian.jira.plugin.... ] Marián Labuda commented on JBDS-4077: ------------------------------------- Nope, I did this: {code}mvn clean verify -Dtest.installBase=/home/mlabuda/testing/wtf/1006/studio -Dopenshift.username=openshift-dev -Dopenshift.password=devel -Dopenshift.server=https://10.1.2.3:8443 -Dscope=3 -DskipTests=false{code} OpenShift tests need configuration - credentials, scope ("2", "3", "2Smoke" or "3Smoke"). The reason why you get tycho failure is because of scope.. > Cannot run integration tests against Devstudio with latest target platform > -------------------------------------------------------------------------- > > Key: JBDS-4077 > URL: https://issues.jboss.org/browse/JBDS-4077 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 10.2.0.AM1 > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Blocker > Attachments: .log, jbosstools-integration-tests.log.txt.zip, org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.txt, org.jboss.tools.deltaspike.ui.bot.test.log.txt, org.jboss.tools.deltaspike.ui.bot.test.log_0.txt, Screenshot_2016-10-05_10-00-03.png, Screenshot_2016-10-05_10-00-21.png, Screenshot_2016-10-05_10-00-28.png, Screenshot_2016-10-05_10-00-57.png, Screenshot_2016-10-05_10-01-14.png, Screenshot_2016-10-05_10-01-32.png, shell.png, TEST-org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.xml, tpfail.png > > > Integration tests run from maven against Devstudio, which was built using the latest target platform (4.61.0.AM1-SNAPSHOT), cannot properly launch all the plugins and fail afterwards. > A full devstudio should open when the tests are run. Instead it looks like this: > !tpfail.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23300) After installation with development suite installer, restarting the Studio, cannot connect anymore automatically to OpenShift instance

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23300?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-23300: ----------------------------------------- This morning, the Connection is again on OAuth with empty token field although yesterday I provided User/password on Basic auth > After installation with development suite installer, restarting the Studio, cannot connect anymore automatically to OpenShift instance > -------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23300 > URL: https://issues.jboss.org/browse/JBIDE-23300 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 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 October 2016