May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21877) Connection wizard: Make error message shown in OpenShift Explorer for outdated token more user friendly

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21877?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21877: -------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha1) > Connection wizard: Make error message shown in OpenShift Explorer for outdated token more user friendly > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21877 > URL: https://issues.jboss.org/browse/JBIDE-21877 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: connection_wizard, openshift_v3 > Fix For: 4.4.x > > > When I am trying to connect to OpenShift connection with outdated token stored in secure storage, an error tree item is shown in OpenShift Explorer under the connection. Erro tree item is "java.lang.NullPointerException", but it could be something more user friendly such as "Expired credentials" or the one we are already using in other scenarious - You must obtain an API token by .... Following stack trace is in error log > {code} > There was an error retrieving children in the OpenShift explorer > java.lang.NullPointerException > at org.eclipse.epp.internal.mpc.core.util.ProxyHelper$ProxyAuthenticator.getPasswordAuthentication(ProxyHelper.java:124) > at java.net.Authenticator.requestPasswordAuthentication(Authenticator.java:317) > at org.apache.http.impl.client.SystemDefaultCredentialsProvider.getSystemCreds(SystemDefaultCredentialsProvider.java:92) > at org.apache.http.impl.client.SystemDefaultCredentialsProvider.getCredentials(SystemDefaultCredentialsProvider.java:113) > at com.openshift.internal.restclient.authorization.OpenShiftCredentialsProvider.getCredentials(OpenShiftCredentialsProvider.java:69) > at org.apache.http.impl.client.AuthenticationStrategyImpl.select(AuthenticationStrategyImpl.java:184) > at org.apache.http.impl.client.TargetAuthenticationStrategy.select(TargetAuthenticationStrategy.java:43) > at org.apache.http.impl.auth.HttpAuthenticator.handleAuthChallenge(HttpAuthenticator.java:154) > at org.apache.http.impl.execchain.MainClientExec.needAuthentication(MainClientExec.java:557) > at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:275) > at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195) > at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86) > at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108) > at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) > at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) > at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106) > at com.openshift.internal.restclient.authorization.AuthorizationClient.getContextUsingCredentials(AuthorizationClient.java:134) > at com.openshift.internal.restclient.authorization.AuthorizationClient.getContext(AuthorizationClient.java:99) > at com.openshift.internal.restclient.DefaultClient.getContext(DefaultClient.java:504) > at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:236) > at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:226) > at org.jboss.tools.openshift.core.connection.Connection.retryList(Connection.java:445) > at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:389) > at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:376) > at org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectCache.getProjectsFor(OpenShiftProjectCache.java:59) > at org.jboss.tools.openshift.internal.ui.explorer.OpenShiftExplorerContentProvider.getChildrenFor(OpenShiftExplorerContentProvider.java:93) > at org.jboss.tools.openshift.internal.common.ui.explorer.BaseExplorerContentProvider$1.run(BaseExplorerContentProvider.java:167) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22035) Server adapter: Stopping of J2EE module does not work

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22035?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22035: -------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha1) > Server adapter: Stopping of J2EE module does not work > ----------------------------------------------------- > > Key: JBIDE-22035 > URL: https://issues.jboss.org/browse/JBIDE-22035 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Labels: openshift_v3, server_adapter > Fix For: 4.4.x > > > Stopping of J2EE Web module lying under an OpenShift 3 Server Adapter does nothing. After discussion with Rob in JBIDE-21989, stop of J2EE module should create an .undeploy marker and rsync it, but that's not happening. Only output from rsync when stopping J2EE module is following > {code}sent 46 bytes received 1,333 bytes 2,758.00 bytes/sec > total size is 8,523,390 speedup is 6,180.85 > sending incremental file list > ROOT.war.isdeploying > sent 1,428 bytes received 149 bytes 3,154.00 bytes/sec > total size is 8,523,390 speedup is 5,404.81{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21962) See if we can use higher resolution for openshift/patternfly icons

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21962?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21962: -------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha1) > See if we can use higher resolution for openshift/patternfly icons > ------------------------------------------------------------------ > > Key: JBIDE-21962 > URL: https://issues.jboss.org/browse/JBIDE-21962 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Catherine Robson > Priority: Minor > Fix For: 4.4.x > > > This is a follow up on JBIDE-21911. Current patternfly 16px icons used for openshift tooling were scaled down via icomoon.io or manually, eg.: > - Route !https://raw.githubusercontent.com/jbosstools/jbosstools-openshift/master/plugins/org.jboss.tools.openshift.ui/icons/route.png! > - Service !https://raw.githubusercontent.com/jbosstools/jbosstools-openshift/master/plugins/org.jboss.tools.openshift.ui/icons/service.png! > Resolution seems suboptimal, would be nice to use nicer looking icons for the full openshift icons set. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21611) Reduce bloat in CDK server adapter menus

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21611?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21611: -------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha1) > Reduce bloat in CDK server adapter menus > ---------------------------------------- > > Key: JBIDE-21611 > URL: https://issues.jboss.org/browse/JBIDE-21611 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.4.x > > Attachments: cdk-server-menus.png > > > The CDK server adapter menus display a lot of useless/disabled menus: > !cdk-server-menus.png|width=650! > It'd be nice to clean that up. Keep > -(re)start > -stop > -Show in> OpenShift, Docker > -Delete > -rename > -properties > It reckon it might not be possible to get rid of all the cruft (when menus are defined upstream), but we might be able to clean some of the menus we "own". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3679) Add incremental deployment for Docker images on OpenShift

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3679?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3679: ------------------------------ Fix Version/s: 10.x (was: 10.0.0.Alpha1) > Add incremental deployment for Docker images on OpenShift > --------------------------------------------------------- > > Key: JBDS-3679 > URL: https://issues.jboss.org/browse/JBDS-3679 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: docker, openshift > Reporter: Fred Bricon > Assignee: Max Rydahl Andersen > Fix For: 10.x > > > Make Docker images deployed on OpenShift support incremental deployment -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21364) [CDK] Change how fetching environment vars via adbinfo works

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21364?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21364: -------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha1) > [CDK] Change how fetching environment vars via adbinfo works > ------------------------------------------------------------ > > Key: JBIDE-21364 > URL: https://issues.jboss.org/browse/JBIDE-21364 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.3.1.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.x > > > Current behavior runs adbinfo directly via runtime.exec(etc). > Investigate upstream solutions as shown here: https://github.com/eclipse/linuxtools/blob/master/containers/org.eclipse.... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21364) [CDK] Change how fetching environment vars via adbinfo works

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21364?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21364: -------------------------------- Issue Type: Enhancement (was: Feature Request) > [CDK] Change how fetching environment vars via adbinfo works > ------------------------------------------------------------ > > Key: JBIDE-21364 > URL: https://issues.jboss.org/browse/JBIDE-21364 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk > Affects Versions: 4.3.1.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.x > > > Current behavior runs adbinfo directly via runtime.exec(etc). > Investigate upstream solutions as shown here: https://github.com/eclipse/linuxtools/blob/master/containers/org.eclipse.... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21785) enable hybrid jobs which can handle both commits and PRs with different publishing patterns

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21785?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21785: ------------------------------------ Latest experiment is here [1]. Result: {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server__pull-request_master/1/console} 17:29:11 GitHub pull request #412 of commit 6ef861a47026124596a20fa24bd80d22507e9665, no merge conflicts. 17:29:11 Setting status of 6ef861a47026124596a20fa24bd80d22507e9665 to PENDING with url http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server__pu... and message: Build started, sha1 is merged 17:29:11 FileNotFoundException means that the credentials Jenkins is using is probably wrong. Or the user account does not have write access to the repo. 17:29:11 java.io.FileNotFoundException: {"message":"Not Found","documentation_url":"https://developer.github.com/v3"}{code} [1] https://github.com/jbosstools/jbosstools-build-ci/commit/a45ff3671b09b577... So, still need to figure out what credentials to use to talk to github. > enable hybrid jobs which can handle both commits and PRs with different publishing patterns > ------------------------------------------------------------------------------------------- > > Key: JBIDE-21785 > URL: https://issues.jboss.org/browse/JBIDE-21785 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.3.1.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.0.Alpha2 > > > Currently we have jobs which handle building from commits, then publishing to a builds/ folder. > And I've prototyped a couple jobs [1], [2] which can handle building from PRs, then publishing to a pulls/ folder. > [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... > Now we need to combine the jobs so that we can do both deployments from the same job, eg., > {code} > if [[ ! ${ghprbPullId} ]]; then > mvnStep1="clean install -DskipTests" # build without tests > mvnStep2="deploy -Pdeploy-to-jboss.org" # deploy if p2diff or SHA check shows difference into /builds/ folder > mvnStep3="verify" # run tests & fail job if problems found > else > mvnStep1="clean deploy -Pdeploy-pr" # build and test, then deploy to /pulls/ folder if successful or fail if tests fail > mvnStep2="NONE" > mvnStep3="NONE" > fi > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3799) Installer - rsync failures seen during post-install JBDS startup of CDK as server runtime

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3799?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3799: ------------------------------ Fix Version/s: 10.0.0.Alpha2 (was: 10.0.0.Alpha1) > Installer - rsync failures seen during post-install JBDS startup of CDK as server runtime > ----------------------------------------------------------------------------------------- > > Key: JBDS-3799 > URL: https://issues.jboss.org/browse/JBDS-3799 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: cdk, upstream > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Hardy Ferentschik > Priority: Critical > Labels: havoc > Fix For: 10.0.0.Alpha2 > > > This unresolved issue: https://github.com/projectatomic/adb-atomic-developer-bundle/issues/272 > Is causing rsync issues such as: > default: Rsyncing folder: /c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ => /vagrant > There was an error when attempting to rsync a synced folder. > Please inspect the error message below for more info. > Host path: /c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ > Guest path: /vagrant > Command: rsync --verbose --archive --delete -z --copy-links --chmod=ugo=rwX --no-perms --no-owner --no-group --rsync-path sudo rsync -e ssh -p 2222 -o StrictHostKeyChecking=no -o IdentitiesOnly=true -o UserKnownHostsFile=/dev/null -i 'C:/DeveloperPlatform/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/private_key' --exclude .vagrant/ /c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ vagrant@127.0.0.1:/vagrant > Error: Warning: Permanently added '[127.0.0.1]:2222' (ECDSA) to the list of known hosts. > dup() in/out/err failed > rsync: connection unexpectedly closed (0 bytes received so far) [sender] > rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.2] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21968) Automatically stop server adapters when connection is severed

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21968?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21968: -------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha1) > Automatically stop server adapters when connection is severed > ------------------------------------------------------------- > > Key: JBIDE-21968 > URL: https://issues.jboss.org/browse/JBIDE-21968 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk, openshift > Affects Versions: 4.3.1.CR1 > Reporter: Jan Richter > Assignee: Rob Stryker > Labels: server_adapter > Fix For: 4.4.x > > > It would be nice to automatically stop the server adapter when no longer connected to openshift (i.e. after shutting down CDK) - that way it would reflect the actual state of things. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 May 2016