September 2019 - jbosstools-issues

[JBoss JIRA] (JBIDE-26865) Fix security warnig due to commons-validator 1.6

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26865?page=com.atlassian.jira.plugi... ] André Dietisheim commented on JBIDE-26865: ------------------------------------------ commons-beanutils was updated to 1.9.4 but the dependency wasn't updated in commons-validator. Nevertheless we only use commons-validator proper, we're not using the commons-beanutils bits: * we only use URLValidator and DomainValidator (which dont use beanutils) * consistently, we only copy commons-validator into our lib/ folder, none of it's dependencies: {code:title=https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/org.jboss.tools.openshift.ui/pom.xml#L39} <configuration> <skip>false</skip> <outputDirectory>${basedir}/lib/</outputDirectory>  <useBaseVersion>true</useBaseVersion> <artifactItems> <artifactItem> <groupId>commons-validator</groupId> <artifactId>commons-validator</artifactId> <version>${commons-validator.version}</version> </artifactItem> </artifactItems> </configuration> {code} > Fix security warnig due to commons-validator 1.6 > ------------------------------------------------ > > Key: JBIDE-26865 > URL: https://issues.jboss.org/browse/JBIDE-26865 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.13.0.AM1 > Reporter: Jeff MAURY > Assignee: André Dietisheim > Priority: Major > Fix For: 4.13.0.Final > > > commons validator 1.6 has a dependency to commons-beanutils 1.9.2 which has a security vulnerability. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26865) Fix security warnig due to commons-validator 1.6

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26865?page=com.atlassian.jira.plugi... ] André Dietisheim commented on JBIDE-26865: ------------------------------------------ In this sense there's nothing to do here. Resolving. > Fix security warnig due to commons-validator 1.6 > ------------------------------------------------ > > Key: JBIDE-26865 > URL: https://issues.jboss.org/browse/JBIDE-26865 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.13.0.AM1 > Reporter: Jeff MAURY > Assignee: André Dietisheim > Priority: Major > Fix For: 4.13.0.Final > > > commons validator 1.6 has a dependency to commons-beanutils 1.9.2 which has a security vulnerability. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26865) Fix security warnig due to commons-validator 1.6

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26865?page=com.atlassian.jira.plugi... ] André Dietisheim resolved JBIDE-26865. -------------------------------------- Resolution: Rejected > Fix security warnig due to commons-validator 1.6 > ------------------------------------------------ > > Key: JBIDE-26865 > URL: https://issues.jboss.org/browse/JBIDE-26865 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.13.0.AM1 > Reporter: Jeff MAURY > Assignee: André Dietisheim > Priority: Major > Fix For: 4.13.0.Final > > > commons validator 1.6 has a dependency to commons-beanutils 1.9.2 which has a security vulnerability. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26808) Assure that npm on the machines uses internal Nexus NPM registry

by Jan Richter (Jira)

[ https://issues.jboss.org/browse/JBIDE-26808?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-26808. ------------------------------- > Assure that npm on the machines uses internal Nexus NPM registry > ----------------------------------------------------------------- > > Key: JBIDE-26808 > URL: https://issues.jboss.org/browse/JBIDE-26808 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.13.0.AM1 > Reporter: Ondrej Dockal > Assignee: Jan Richter > Priority: Major > Fix For: 4.13.0.Final > > Attachments: check_url.sh > > > According to [1] we need to take actions at projects using npm. > [1]: https://docs.google.com/document/d/1dn1gQFaJ_Q0IOeRAnFAsBMgVRnwA8ieLQV-AG... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26868) Connection wizard: errors when login to https://api.openshift4-crs.crs.codereadyqe.com

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26868?page=com.atlassian.jira.plugi... ] André Dietisheim commented on JBIDE-26868: ------------------------------------------ the very same connection works in oc command line: {code} $ oc login --token=XXXXX --server=https://api.openshift4-crs.crs.codereadyqe.com:6443 The server uses a certificate signed by an unknown authority. You can bypass the certificate check, but any data you send to the server could be intercepted by others. Use insecure connections? (y/n): y Logged into "https://api.openshift4-crs.crs.codereadyqe.com:6443" as "developer" using the token provided. You have one project on this server: "sdfasdf" Using project "sdfasdf". {code} > Connection wizard: errors when login to https://api.openshift4-crs.crs.codereadyqe.com > -------------------------------------------------------------------------------------- > > Key: JBIDE-26868 > URL: https://issues.jboss.org/browse/JBIDE-26868 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.13.0.AM1 > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Critical > Labels: connection_wizard > Fix For: 4.13.0.Final > > > Steps: > # EXEC: (VPN required) go to https://console-openshift-console.apps.openshift4-crs.crs.codereadyqe.com/ and login using: htpasswd > developer/developer > # EXEC: once logged in, pick "Copy Login Command" from the menu in the top right corner - you'll have to log in again and hit "Display Token". You'll get a command displayed that you'll have to copy: > {code} > oc login --token=XXXXXX --server=https://api.openshift4-crs.crs.codereadyqe.com:6443 > {code} > # EXEC: open connection wizard, hit "Paste Login Command" button & pick "Finish" > Result: > {code} > com.openshift.restclient.authorization.ResourceForbiddenException: forbidden: User "system:anonymous" cannot get path "/apis" forbidden: User "system:anonymous" cannot get path "/apis" > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:111) > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:66) > at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:112) > at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:87) > at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.kt:184) > at okhttp3.RealCall.execute(RealCall.kt:66) > at com.openshift.internal.restclient.ApiTypeMapper.request(ApiTypeMapper.java:265) > at com.openshift.internal.restclient.ApiTypeMapper.readEndpoint(ApiTypeMapper.java:257) > at com.openshift.internal.restclient.ApiTypeMapper.getApiGroups(ApiTypeMapper.java:220) > at com.openshift.internal.restclient.ApiTypeMapper.init(ApiTypeMapper.java:155) > at com.openshift.internal.restclient.ApiTypeMapper.isSupported(ApiTypeMapper.java:84) > at com.openshift.internal.restclient.URLBuilder.buildWithNamespaceInPath(URLBuilder.java:148) > at com.openshift.internal.restclient.URLBuilder.build(URLBuilder.java:135) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:301) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:275) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:243) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:226) > at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:423) > at com.openshift.internal.restclient.authorization.AuthorizationContext.isAuthorized(AuthorizationContext.java:63) > at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:237) > at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:226) > at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPageModel.connect(ConnectionWizardPageModel.java:300) > at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage$ConnectJob.doRun(ConnectionWizardPage.java:434) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26859) CRC server adapter wizard: Browse buttons are excessively wide

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26859?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26859: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/1876 (was: https://github.com/jbosstools/jbosstools-openshift/pull/1874) > CRC server adapter wizard: Browse buttons are excessively wide > -------------------------------------------------------------- > > Key: JBIDE-26859 > URL: https://issues.jboss.org/browse/JBIDE-26859 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.13.0.AM1 > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Fix For: 4.13.0.Final > > Attachments: screenshot-1.png > > > !screenshot-1.png! > Also noticeable is that when scaling the dialog size horizontally, the buttons grow, too. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26842) Update 4.13.0.Final Target Platform (Docker tooling, ...) for 2019-09.GA

by stephane bouchet (Jira)

[ https://issues.jboss.org/browse/JBIDE-26842?page=com.atlassian.jira.plugi... ] stephane bouchet updated JBIDE-26842: ------------------------------------- Attachment: p2diff_log_jbosstools_2019-09-24_11-48.txt > Update 4.13.0.Final Target Platform (Docker tooling, ...) for 2019-09.GA > ------------------------------------------------------------------------ > > Key: JBIDE-26842 > URL: https://issues.jboss.org/browse/JBIDE-26842 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.13.0.AM1 > Reporter: Jeff MAURY > Assignee: stephane bouchet > Priority: Major > Fix For: 4.13.0.Final > > Attachments: p2diff_log_jbosstools_2019-09-24_11-48.txt > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20014) Explorer: "New" context menu not showing up at times (Linux only, GTK2 and GTK3)

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-20014?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20014: ------------------------------- Fix Version/s: (was: 4.3.x) > Explorer: "New" context menu not showing up at times (Linux only, GTK2 and GTK3) > -------------------------------------------------------------------------------- > > Key: JBIDE-20014 > URL: https://issues.jboss.org/browse/JBIDE-20014 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.Beta1 > Environment: Linux GTK2, GTK3 > Reporter: André Dietisheim > Assignee: Snjezana Peco > Priority: Blocker > Fix For: 4.12.0.Final > > Attachments: new-submenu-not-visible.png, new-submenu-visible.png > > > It is quite frequent that the "New" (and "Show in" for v3) submenu wont show up. This happens even if the submenu is first visible but then, on a 2nd context menu invocation, disappears -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20014) Explorer: "New" context menu not showing up at times (Linux only, GTK2 and GTK3)

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-20014?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-20014. ------------------------------ Resolution: Done > Explorer: "New" context menu not showing up at times (Linux only, GTK2 and GTK3) > -------------------------------------------------------------------------------- > > Key: JBIDE-20014 > URL: https://issues.jboss.org/browse/JBIDE-20014 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.Beta1 > Environment: Linux GTK2, GTK3 > Reporter: André Dietisheim > Assignee: Snjezana Peco > Priority: Blocker > Fix For: 4.12.0.Final > > Attachments: new-submenu-not-visible.png, new-submenu-visible.png > > > It is quite frequent that the "New" (and "Show in" for v3) submenu wont show up. This happens even if the submenu is first visible but then, on a 2nd context menu invocation, disappears -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26558) Update WildFly to version 17 in examples.itests

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26558?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26558: ------------------------------- Fix Version/s: 4.13.0.AM1 (was: 4.14.x) > Update WildFly to version 17 in examples.itests > ----------------------------------------------- > > Key: JBIDE-26558 > URL: https://issues.jboss.org/browse/JBIDE-26558 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: integration-tests > Affects Versions: 4.11.0.AM1 > Environment: All environments > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Critical > Fix For: 4.13.0.AM1 > > > Update WindFly from version 11 to version 17 in examples.itests -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2019