[JBoss JIRA] (JBIDE-26891) Connection wizard: "Override oc version" complains even though nothing to complain about
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26891?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26891:
-------------------------------
Sprint: devex #174 Oct 2019, devex #175 Nov 2019, devex #176 Nov/Dec 2019 (was: devex #174 Oct 2019, devex #175 Nov 2019)
> Connection wizard: "Override oc version" complains even though nothing to complain about
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-26891
> URL: https://issues.jboss.org/browse/JBIDE-26891
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.13.0.AM1
> Reporter: André Dietisheim
> Assignee: André Dietisheim
> Priority: Major
> Labels: connection_wizard
> Fix For: 4.14.x
>
> Attachments: image-2019-10-14-22-57-02-582.png
>
>
> Steps:
> # ASSERT: make sure that you have a valid *oc* binary set in your preferences (Preferences > OpenShift > 'oc' executable location
> # EXEC: launch connection wizard (New > Other > OpenShift)
> # EXEC: hit "Advanced >>" & check "Override 'oc' location:"
> Result:
> The input field for "Override 'oc' location:" is decorated with a warning even though the path that is used (that is taken from necessarily valid preferences) is perfectly valid
> !image-2019-10-14-22-57-02-582.png!
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (JBIDE-26899) Refreshing non-functional connection to CRC doesnt help (need to create new)
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26899?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26899:
-------------------------------
Sprint: devex #174 Oct 2019, devex #175 Nov 2019, devex #176 Nov/Dec 2019 (was: devex #174 Oct 2019, devex #175 Nov 2019)
> Refreshing non-functional connection to CRC doesnt help (need to create new)
> ----------------------------------------------------------------------------
>
> Key: JBIDE-26899
> URL: https://issues.jboss.org/browse/JBIDE-26899
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.13.0.Final
> Environment: CRC
> Reporter: André Dietisheim
> Assignee: André Dietisheim
> Priority: Major
> Fix For: 4.14.0.AM1
>
>
> *Steps* - not reproducibe at 100%, happens from time to time:
> # ASSERT: have ~/.crc folder killed
> # EXEC: create new CRC server adapter & Start it
> # ASSERT: OpenShift connection is created
> # ASSERT: Connection fails to authorize, reports that it cannot access resources using system:anonymous.
> # EXEC: try to login with *oc login*. If oc reports *Error from server (InternalError): Internal error occurred: unexpected response: 400*, repeat until it succeeds (waiting required)
> # EXEC: Once oc login succeeds: refresh the connection in Eclipse
> Result:
> Connecting still fails with the same error.
> Expected result:
> Refreshing the connection should succeed once the server is fully up and running and oc succeeds to log in.
> Workaround:
> # EXEC: edit the connection instead of refreshing it (ex. remove a character from username and add it back again)
> Result:
> Connecting succeeds
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (JBIDE-24899) Deploy Docker Image wizard: Image not found
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-24899?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24899:
-------------------------------
Sprint: devex #169 July 2019, devex #172 Sep 2019, devex #171 Aug 2019, devex #173 Oct 2019, devex #174 Oct 2019, devex #175 Nov 2019, devex #176 Nov/Dec 2019 (was: devex #169 July 2019, devex #172 Sep 2019, devex #171 Aug 2019, devex #173 Oct 2019, devex #174 Oct 2019, devex #175 Nov 2019)
> Deploy Docker Image wizard: Image not found
> -------------------------------------------
>
> Key: JBIDE-24899
> URL: https://issues.jboss.org/browse/JBIDE-24899
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, docker, openshift
> Affects Versions: 4.5.1.AM1
> Reporter: Josef Kopriva
> Priority: Major
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.14.x
>
> Attachments: image-2017-08-29-09-50-20-927.png
>
>
> Exception in Error log:
> {code:java}
> Failed to inspect image: '172.30.1.1:5000/test/hola:latest'
> com.spotify.docker.client.exceptions.ImageNotFoundException: Image not found: 172.30.1.1:5000/test/hola:latest
> at com.spotify.docker.client.DefaultDockerClient.inspectImage(DefaultDockerClient.java:1330)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImageInfo(DockerConnection.java:896)
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.lookupImageMetadata(DeployImageWizardModel.java:655)
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.initializeContainerInfo(DeployImageWizardModel.java:354)
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage$1ImageValidatorJob.run(DeployImagePage.java:154)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: com.spotify.docker.client.exceptions.DockerRequestException: Request error: GET https://192.168.42.121:2376/images/172.30.1.1:5000/test/hola:latest/json: 404
> at com.spotify.docker.client.DefaultDockerClient.propagate(DefaultDockerClient.java:2084)
> at com.spotify.docker.client.DefaultDockerClient.request(DefaultDockerClient.java:2023)
> at com.spotify.docker.client.DefaultDockerClient.inspectImage(DefaultDockerClient.java:1326)
> ... 5 more
> Caused by: javax.ws.rs.NotFoundException: HTTP 404 Not Found
> at org.glassfish.jersey.client.JerseyInvocation.convertToException(JerseyInvocation.java:1008)
> at org.glassfish.jersey.client.JerseyInvocation.translate(JerseyInvocation.java:816)
> at org.glassfish.jersey.client.JerseyInvocation.access$700(JerseyInvocation.java:92)
> at org.glassfish.jersey.client.JerseyInvocation$5.completed(JerseyInvocation.java:773)
> at org.glassfish.jersey.client.ClientRuntime.processResponse(ClientRuntime.java:198)
> at org.glassfish.jersey.client.ClientRuntime.access$300(ClientRuntime.java:79)
> at org.glassfish.jersey.client.ClientRuntime$2.run(ClientRuntime.java:180)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:267)
> at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:340)
> at org.glassfish.jersey.client.ClientRuntime$3.run(ClientRuntime.java:210)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> eclipse.buildId=11.1.0.AM1-v20170824-1835-B873
> java.version=1.8.0_141
> 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
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (JBIDE-26970) Validator: The annotation @PathParam must define the attribute value
by nimo stephan (Jira)
[ https://issues.jboss.org/browse/JBIDE-26970?page=com.atlassian.jira.plugi... ]
nimo stephan updated JBIDE-26970:
---------------------------------
Description:
According to https://developer.jboss.org/en/resteasy/blog/2018/05/29/new-blog, I can define a resource with
{code:java}
public String hello(@PathParam String name) {
..
}
{code}
instead of
{code:java}
public String hello(@PathParam(value="name") String name) {
..
}
{code}
when setting the following in pom.xml:
{code:java}
<maven.compiler.parameters>true</maven.compiler.parameters>
{code}
However, jboss tools validator complains about it as an validator error ("The annotation @PathParam must define the attribute value") and compilation fails. So I tried to disable some validators according to JbossPath-Params (see attachement).
However, the error is still shown in my editor by the validator.
was:
According to https://developer.jboss.org/en/resteasy/blog/2018/05/29/new-blog, I can define a resource with
{code:java}
public String hello(@PathParam String name) {
..
}
{code}
instead of
{code:java}
public String hello(@PathParam(value="name") String name) {
..
}
{code}
when setting the following in pom.xml:
{code:java}
<maven.compiler.parameters>true</maven.compiler.parameters>
{code}
However, jboss tools validator complains about it as an error and compilation fails. So I tried to disable some validators according to JbossPath-Params (see attachement).
However, the error is still shown in my editor by the validator.
> Validator: The annotation @PathParam must define the attribute value
> --------------------------------------------------------------------
>
> Key: JBIDE-26970
> URL: https://issues.jboss.org/browse/JBIDE-26970
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Reporter: nimo stephan
> Priority: Major
> Attachments: jax-rs-validator.png
>
>
> According to https://developer.jboss.org/en/resteasy/blog/2018/05/29/new-blog, I can define a resource with
> {code:java}
> public String hello(@PathParam String name) {
> ..
> }
> {code}
> instead of
> {code:java}
> public String hello(@PathParam(value="name") String name) {
> ..
> }
> {code}
> when setting the following in pom.xml:
> {code:java}
> <maven.compiler.parameters>true</maven.compiler.parameters>
> {code}
> However, jboss tools validator complains about it as an validator error ("The annotation @PathParam must define the attribute value") and compilation fails. So I tried to disable some validators according to JbossPath-Params (see attachement).
> However, the error is still shown in my editor by the validator.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (JBIDE-26970) Validator: The annotation @PathParam must define the attribute value
by nimo stephan (Jira)
[ https://issues.jboss.org/browse/JBIDE-26970?page=com.atlassian.jira.plugi... ]
nimo stephan updated JBIDE-26970:
---------------------------------
Description:
According to https://developer.jboss.org/en/resteasy/blog/2018/05/29/new-blog, I can define a resource with
{code:java}
public String hello(@PathParam String name) {
..
}
{code}
instead of
{code:java}
public String hello(@PathParam(value="name") String name) {
..
}
{code}
when setting the following in pom.xml:
{code:java}
<maven.compiler.parameters>true</maven.compiler.parameters>
{code}
However, jboss tools validator complains about it as an validator error:
{code:java}
The annotation @PathParam must define the attribute value")
{code}
and compilation fails.
So I tried to disable some validators according to JbossPath-Params (see attachement).
However, the error is still shown in my editor by the validator.
was:
According to https://developer.jboss.org/en/resteasy/blog/2018/05/29/new-blog, I can define a resource with
{code:java}
public String hello(@PathParam String name) {
..
}
{code}
instead of
{code:java}
public String hello(@PathParam(value="name") String name) {
..
}
{code}
when setting the following in pom.xml:
{code:java}
<maven.compiler.parameters>true</maven.compiler.parameters>
{code}
However, jboss tools validator complains about it as an validator error ("The annotation @PathParam must define the attribute value") and compilation fails. So I tried to disable some validators according to JbossPath-Params (see attachement).
However, the error is still shown in my editor by the validator.
> Validator: The annotation @PathParam must define the attribute value
> --------------------------------------------------------------------
>
> Key: JBIDE-26970
> URL: https://issues.jboss.org/browse/JBIDE-26970
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Reporter: nimo stephan
> Priority: Major
> Attachments: jax-rs-validator.png
>
>
> According to https://developer.jboss.org/en/resteasy/blog/2018/05/29/new-blog, I can define a resource with
> {code:java}
> public String hello(@PathParam String name) {
> ..
> }
> {code}
> instead of
> {code:java}
> public String hello(@PathParam(value="name") String name) {
> ..
> }
> {code}
> when setting the following in pom.xml:
> {code:java}
> <maven.compiler.parameters>true</maven.compiler.parameters>
> {code}
> However, jboss tools validator complains about it as an validator error:
> {code:java}
> The annotation @PathParam must define the attribute value")
> {code}
> and compilation fails.
> So I tried to disable some validators according to JbossPath-Params (see attachement).
> However, the error is still shown in my editor by the validator.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (JBIDE-26970) Validator: The annotation @PathParam must define the attribute value
by nimo stephan (Jira)
[ https://issues.jboss.org/browse/JBIDE-26970?page=com.atlassian.jira.plugi... ]
nimo stephan updated JBIDE-26970:
---------------------------------
Description:
According to https://developer.jboss.org/en/resteasy/blog/2018/05/29/new-blog, I can define a resource with
{code:java}
public String hello(@PathParam String name) {
..
}
{code}
instead of
{code:java}
public String hello(@PathParam(value="name") String name) {
..
}
{code}
when setting the following in pom.xml:
{code:java}
<maven.compiler.parameters>true</maven.compiler.parameters>
{code}
However, jboss tools validator complains about it as a validator error:
{code:java}
The annotation @PathParam must define the attribute value")
{code}
and compilation fails.
So I tried to disable some validators according to JbossPath-Params (see attachement).
However, the error is still shown in my editor by the validator.
was:
According to https://developer.jboss.org/en/resteasy/blog/2018/05/29/new-blog, I can define a resource with
{code:java}
public String hello(@PathParam String name) {
..
}
{code}
instead of
{code:java}
public String hello(@PathParam(value="name") String name) {
..
}
{code}
when setting the following in pom.xml:
{code:java}
<maven.compiler.parameters>true</maven.compiler.parameters>
{code}
However, jboss tools validator complains about it as an validator error:
{code:java}
The annotation @PathParam must define the attribute value")
{code}
and compilation fails.
So I tried to disable some validators according to JbossPath-Params (see attachement).
However, the error is still shown in my editor by the validator.
> Validator: The annotation @PathParam must define the attribute value
> --------------------------------------------------------------------
>
> Key: JBIDE-26970
> URL: https://issues.jboss.org/browse/JBIDE-26970
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Reporter: nimo stephan
> Priority: Major
> Attachments: jax-rs-validator.png
>
>
> According to https://developer.jboss.org/en/resteasy/blog/2018/05/29/new-blog, I can define a resource with
> {code:java}
> public String hello(@PathParam String name) {
> ..
> }
> {code}
> instead of
> {code:java}
> public String hello(@PathParam(value="name") String name) {
> ..
> }
> {code}
> when setting the following in pom.xml:
> {code:java}
> <maven.compiler.parameters>true</maven.compiler.parameters>
> {code}
> However, jboss tools validator complains about it as a validator error:
> {code:java}
> The annotation @PathParam must define the attribute value")
> {code}
> and compilation fails.
> So I tried to disable some validators according to JbossPath-Params (see attachement).
> However, the error is still shown in my editor by the validator.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (JBIDE-26970) Validator: The annotation @PathParam must define the attribute value
by nimo stephan (Jira)
nimo stephan created JBIDE-26970:
------------------------------------
Summary: Validator: The annotation @PathParam must define the attribute value
Key: JBIDE-26970
URL: https://issues.jboss.org/browse/JBIDE-26970
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Reporter: nimo stephan
Attachments: jax-rs-validator.png
According to https://developer.jboss.org/en/resteasy/blog/2018/05/29/new-blog, I can define a resource with
{code:java}
public String hello(@PathParam String name) {
..
}
{code}
instead of
{code:java}
public String hello(@PathParam(value="name") String name) {
..
}
{code}
when setting the following in pom.xml:
{code:java}
<maven.compiler.parameters>true</maven.compiler.parameters>
{code}
However, jboss tools validator complains about it as an error and compilation fails. So I tried to disable some validators according to JbossPath-Params (see attachement).
However, the error is still shown in my editor by the validator.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months