[JBoss JIRA] (JBIDE-26139) openshift does not compile anymore
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26139?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26139:
-------------------------------------
Story Points: 2
> openshift does not compile anymore
> ----------------------------------
>
> Key: JBIDE-26139
> URL: https://issues.jboss.org/browse/JBIDE-26139
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Fix For: 4.6.0.Final
>
>
> Since a change in the target platform, jbosstools openshift does not compile anymore. an unknown method is used in org.jboss.tools.openshift.egit.test
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:1.1.0:compile (default-compile) on project org.jboss.tools.openshift.egit.test: Compilation failure: Compilation failure:
> [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift-Pull-Request/tests/org.jboss.tools.openshift.egit.test/src/org/jboss/tools/openshift/egit/internal/test/util/TestRepository.java:[477]
> [ERROR] Ref ref = repository.getRef(Constants.HEAD);
> [ERROR] ^^^^^^
> [ERROR] The method getRef(String) is undefined for the type Repository
> [ERROR] 1 problem (1 error)
> [ERROR] -> [Help 1]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26069) Spring Boot Project configurator: Creating child module for main project fails
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26069?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-26069:
----------------------------------------
Assignee: Jeff MAURY (was: Andre Dietisheim)
> Spring Boot Project configurator: Creating child module for main project fails
> -------------------------------------------------------------------------------
>
> Key: JBIDE-26069
> URL: https://issues.jboss.org/browse/JBIDE-26069
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.6.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: project_configurator, springboot
> Fix For: 4.6.0.Final
>
> Attachments: image-2018-05-30-22-31-37-635.png
>
>
> steps:
> # ASSERT: We dont know for now, really. We can only reproduce this on [~jeffmaury]'s machine (happens to him in Windows and Linux - doesn't for others in Linux nor Mac).
> # EXEC: import the 2 maven projects that are attached to JBIDE-25504 (camel-ose-springboot-xml and penguins
> # EXEC: in project properties for project *camel-ose-springboot-xml*: pick "Deployment Assembly"
> # ASSERT: verify that *penguins* is defined as child module
> Result:
> !image-2018-05-30-22-31-37-635.png!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-25586) OpenJDK9 + OpenShift Tooling: Cannot connect to OpenShift on CDK
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25586?page=com.atlassian.jira.plugi... ]
Josef Kopriva commented on JBIDE-25586:
---------------------------------------
[~adietish] Now I get different error:
{code:java}
eclipse.buildId=12.0.0.GA-v20180620-0445-B2795
java.version=9.0.4
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -product com.jboss.devstudio.core.product
Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
org.jboss.tools.openshift.ui
Error
Wed Jun 20 16:18:08 CEST 2018
Unable to read endpoint https://192.168.42.104:8443/api
com.openshift.restclient.OpenShiftException: Unable to read endpoint https://192.168.42.104:8443/api
at com.openshift.internal.restclient.ApiTypeMapper.readEndpoint(ApiTypeMapper.java:192)
at com.openshift.internal.restclient.ApiTypeMapper.getLegacyGroups(ApiTypeMapper.java:177)
at com.openshift.internal.restclient.ApiTypeMapper.init(ApiTypeMapper.java:122)
at com.openshift.internal.restclient.ApiTypeMapper.isSupported(ApiTypeMapper.java:82)
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:243)
at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:217)
at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:203)
at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:320)
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:350)
at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage$ConnectJob.doRun(ConnectionWizardPage.java:432)
at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
Caused by: javax.net.ssl.SSLException: java.net.SocketException: Broken pipe (Write failed)
at java.base/sun.security.ssl.Alerts.getSSLException(Alerts.java:214)
at java.base/sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1969)
at java.base/sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1921)
at java.base/sun.security.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:794)
at java.base/sun.security.ssl.AppOutputStream.write(AppOutputStream.java:67)
at okio.Okio$1.write(Okio.java:80)
at okio.AsyncTimeout$1.write(AsyncTimeout.java:180)
at okio.RealBufferedSink.flush(RealBufferedSink.java:216)
at okhttp3.internal.framed.Http2$Writer.settings(Http2.java:514)
at okhttp3.internal.framed.FramedConnection.start(FramedConnection.java:519)
at okhttp3.internal.framed.FramedConnection.start(FramedConnection.java:509)
at okhttp3.internal.io.RealConnection.establishProtocol(RealConnection.java:210)
at okhttp3.internal.io.RealConnection.buildConnection(RealConnection.java:171)
at okhttp3.internal.io.RealConnection.connect(RealConnection.java:111)
at okhttp3.internal.http.StreamAllocation.findConnection(StreamAllocation.java:187)
at okhttp3.internal.http.StreamAllocation.findHealthyConnection(StreamAllocation.java:123)
at okhttp3.internal.http.StreamAllocation.newStream(StreamAllocation.java:93)
at okhttp3.internal.http.HttpEngine.connect(HttpEngine.java:296)
at okhttp3.internal.http.HttpEngine.sendRequest(HttpEngine.java:248)
at okhttp3.RealCall.getResponse(RealCall.java:243)
at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:201)
at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:55)
at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190)
at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163)
at okhttp3.RealCall.execute(RealCall.java:57)
at com.openshift.internal.restclient.ApiTypeMapper.readEndpoint(ApiTypeMapper.java:189)
... 16 more
Caused by: java.net.SocketException: Broken pipe (Write failed)
at java.base/java.net.SocketOutputStream.socketWrite0(Native Method)
at java.base/java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:111)
at java.base/java.net.SocketOutputStream.write(SocketOutputStream.java:155)
at java.base/sun.security.ssl.SSLSocketOutputRecord.deliver(SSLSocketOutputRecord.java:307)
at java.base/sun.security.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:779)
... 38 more
{code}
Devstudio: 12.0.0.GA-v20180620-0445-B2795
Java version: 9.0.4
With Java 8 if wors without issues in the same environment.
> OpenJDK9 + OpenShift Tooling: Cannot connect to OpenShift on CDK
> ----------------------------------------------------------------
>
> Key: JBIDE-25586
> URL: https://issues.jboss.org/browse/JBIDE-25586
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.2.Final
> Environment: FC27
> OpenJDK 9.0.1
> CDK v3.3.0-rc.1-1
> eclipse.buildId=11.2.0.GA-v20180115-0516-B1866
> java.version=9.0.1
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> Reporter: Josef Kopriva
> Assignee: Rob Stryker
> Priority: Critical
> Labels: cdk, connection
> Fix For: 4.6.0.Final
>
>
> But, connecting to online openshift instance works.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-25109) Server adapter editor: provide ability to only change debug port (and not the debug port key)
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25109?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-25109:
-------------------------------------
Fix Version/s: 4.6.0.Final
(was: 4.6.x)
> Server adapter editor: provide ability to only change debug port (and not the debug port key)
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-25109
> URL: https://issues.jboss.org/browse/JBIDE-25109
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Andre Dietisheim
> Assignee: Dmitrii Bocharov
> Labels: openshift_v3, server_adapter_editor
> Fix For: 4.6.0.Final
>
>
> Currently there's only 1 checkbox to allow the user to set the debugging key and port. If one only wants to set a custom debug port only, he cannot, he also has to provide the debug key at the same time. We should provide an additional checkbox to enable the debug port only, changing the existing one to only enable/disable the debug key.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-25838) Explorer: expand connection to the level that it was expanded to after editing it
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25838?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-25838:
-------------------------------------
Fix Version/s: 4.6.0.Final
(was: 4.6.x)
> Explorer: expand connection to the level that it was expanded to after editing it
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-25838
> URL: https://issues.jboss.org/browse/JBIDE-25838
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.2.AM3
> Reporter: Andre Dietisheim
> Assignee: Dmitrii Bocharov
> Labels: connection, explorer
> Fix For: 4.6.0.Final
>
>
> steps:
> # ASSERT: in OpenShift Explorer: have a connection that is expanded to at least show a/all the projects
> # EXEC: edit the connection, change the url, hit "Finish"
> Result:
> Connection is updated (refreshed) but collapsed, wont show the/all the projects
> Expected result:
> Connection is updated (refreshed) and expanded like it was before editing it, showing the project(s) (and even service(s) if it was expanded to that level before editing it)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26084) Explorer: pods are show twice if they're controlled by an rc (no dc, no service)
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26084?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-26084:
-------------------------------------
Fix Version/s: 4.6.0.Final
(was: 4.6.x)
> Explorer: pods are show twice if they're controlled by an rc (no dc, no service)
> --------------------------------------------------------------------------------
>
> Key: JBIDE-26084
> URL: https://issues.jboss.org/browse/JBIDE-26084
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Dmitrii Bocharov
> Labels: explorer
> Fix For: 4.6.0.Final
>
> Attachments: eap-without-service-nor-deploymentconfig.json, image-2018-06-06-10-33-55-241.png
>
>
> steps:
> # EXEC: Create a new application via the following custom template [^eap-without-service-nor-deploymentconfig.json]
> # EXEC: look into OpenShift explorer and see where the pods for the application are shown
> Result:
> They're listed twice, once as pods on their own and a 2nd time as children for the replication controller (that the template creates)
> !image-2018-06-06-10-33-55-241.png!
> Also see the discussion in the PR Also see discussion for the corresponding [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1748] for JBIDE-24979
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26084) Explorer: pods are show twice if they're controlled by an rc (no dc, no service)
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26084?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-26084:
-------------------------------------
Sprint: devex #151 June 2018
> Explorer: pods are show twice if they're controlled by an rc (no dc, no service)
> --------------------------------------------------------------------------------
>
> Key: JBIDE-26084
> URL: https://issues.jboss.org/browse/JBIDE-26084
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Dmitrii Bocharov
> Labels: explorer
> Fix For: 4.6.x
>
> Attachments: eap-without-service-nor-deploymentconfig.json, image-2018-06-06-10-33-55-241.png
>
>
> steps:
> # EXEC: Create a new application via the following custom template [^eap-without-service-nor-deploymentconfig.json]
> # EXEC: look into OpenShift explorer and see where the pods for the application are shown
> Result:
> They're listed twice, once as pods on their own and a 2nd time as children for the replication controller (that the template creates)
> !image-2018-06-06-10-33-55-241.png!
> Also see the discussion in the PR Also see discussion for the corresponding [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1748] for JBIDE-24979
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26139) openshift does not compile anymore
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26139?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-26139 at 6/20/18 10:13 AM:
--------------------------------------------------------------------
TestRepository marked #getRef as deprecated and tells users to use #extractRef instead
{code}
/**
* Get a ref by name.
*
* @param name
* the name of the ref to lookup. May be a short-hand form, e.g.
* "master" which is is automatically expanded to
* "refs/heads/master" if "refs/heads/master" already exists.
* @return the Ref with the given name, or {@code null} if it does not exist
* @throws java.io.IOException
* @deprecated Use {@link #exactRef(String)} or {@link #findRef(String)}
* instead.
*/
@Deprecated
@Nullable
public Ref getRef(final String name) throws IOException {
return findRef(name);
}
{code}
was (Author: adietish):
TestRepository marked #getRef as deprecated and tells users to use #extractRef instead
> openshift does not compile anymore
> ----------------------------------
>
> Key: JBIDE-26139
> URL: https://issues.jboss.org/browse/JBIDE-26139
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Fix For: 4.6.0.Final
>
>
> Since a change in the target platform, jbosstools openshift does not compile anymore. an unknown method is used in org.jboss.tools.openshift.egit.test
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:1.1.0:compile (default-compile) on project org.jboss.tools.openshift.egit.test: Compilation failure: Compilation failure:
> [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift-Pull-Request/tests/org.jboss.tools.openshift.egit.test/src/org/jboss/tools/openshift/egit/internal/test/util/TestRepository.java:[477]
> [ERROR] Ref ref = repository.getRef(Constants.HEAD);
> [ERROR] ^^^^^^
> [ERROR] The method getRef(String) is undefined for the type Repository
> [ERROR] 1 problem (1 error)
> [ERROR] -> [Help 1]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26084) Explorer: pods are show twice if they're controlled by an rc (no dc, no service)
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26084?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov reassigned JBIDE-26084:
----------------------------------------
Assignee: Dmitrii Bocharov
> Explorer: pods are show twice if they're controlled by an rc (no dc, no service)
> --------------------------------------------------------------------------------
>
> Key: JBIDE-26084
> URL: https://issues.jboss.org/browse/JBIDE-26084
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Dmitrii Bocharov
> Labels: explorer
> Fix For: 4.6.x
>
> Attachments: eap-without-service-nor-deploymentconfig.json, image-2018-06-06-10-33-55-241.png
>
>
> steps:
> # EXEC: Create a new application via the following custom template [^eap-without-service-nor-deploymentconfig.json]
> # EXEC: look into OpenShift explorer and see where the pods for the application are shown
> Result:
> They're listed twice, once as pods on their own and a 2nd time as children for the replication controller (that the template creates)
> !image-2018-06-06-10-33-55-241.png!
> Also see the discussion in the PR Also see discussion for the corresponding [PR|https://github.com/jbosstools/jbosstools-openshift/pull/1748] for JBIDE-24979
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months