[JBoss JIRA] (JBIDE-26970) Validator: The annotation @PathParam must define the attribute value
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26970?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-26970:
----------------------------------
Assignee: Jeff MAURY
> 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
> Affects Versions: 4.13.0.Final
> Reporter: nimo stephan
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 4.14.0.AM1
>
> 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)
4 years, 6 months
[JBoss JIRA] (JBIDE-26970) Validator: The annotation @PathParam must define the attribute value
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26970?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26970:
-------------------------------
Affects Version/s: 4.13.0.Final
> 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
> Affects Versions: 4.13.0.Final
> Reporter: nimo stephan
> Priority: Major
> Fix For: 4.14.0.AM1
>
> 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)
4 years, 6 months
[JBoss JIRA] (JBIDE-26970) Validator: The annotation @PathParam must define the attribute value
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26970?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26970:
-------------------------------
Fix Version/s: 4.14.0.AM1
> 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
> Affects Versions: 4.13.0.Final
> Reporter: nimo stephan
> Priority: Major
> Fix For: 4.14.0.AM1
>
> 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)
4 years, 6 months
[JBoss JIRA] (JBIDE-26971) Rename CRC server adapter to CodeReady Containers 1.x
by Jeff MAURY (Jira)
Jeff MAURY created JBIDE-26971:
----------------------------------
Summary: Rename CRC server adapter to CodeReady Containers 1.x
Key: JBIDE-26971
URL: https://issues.jboss.org/browse/JBIDE-26971
Project: Tools (JBoss Tools)
Issue Type: Task
Components: openshift
Affects Versions: 4.13.0.Final
Reporter: Jeff MAURY
Assignee: André Dietisheim
Fix For: 4.14.0.AM1
Given the pace of CRC releases, we should rename the CRC server adapter from
{code:java}
CodeReady Containers 1.0
{code}
to
{code:java}
CodeReady Containers 1.x
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (JBDS-4735) Central projects Wizard sometimes fails to open
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBDS-4735?page=com.atlassian.jira.plugin.... ]
Jeff MAURY updated JBDS-4735:
-----------------------------
Sprint: devex #159 December 2018, devex #161 January 2019, devex #162 February 2019, devex #163 March 2019, devex #164 April 2019, devex #165 April 2019, devex #166 May 2019, devex #167 June 2019, devex #168 June 2019, devex #169 July 2019, devex #172 Sep 2019, devex #170 Aug 2019, devex #171 Aug 2019, devex #173 Oct 2019, devex #174 Oct 2019, devex #175 Nov 2019, devex #176 Nov/Dec 2019 (was: devex #159 December 2018, devex #161 January 2019, devex #162 February 2019, devex #163 March 2019, devex #164 April 2019, devex #165 April 2019, devex #166 May 2019, devex #167 June 2019, devex #168 June 2019, devex #169 July 2019, devex #172 Sep 2019, devex #170 Aug 2019, devex #171 Aug 2019, devex #173 Oct 2019, devex #174 Oct 2019, devex #175 Nov 2019)
> Central projects Wizard sometimes fails to open
> -----------------------------------------------
>
> Key: JBDS-4735
> URL: https://issues.jboss.org/browse/JBDS-4735
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Bug
> Components: central
> Affects Versions: 12.9.0.GA
> Environment: manually Fedora 28,
> manually Fedora 29,
> manually RHEL 7.7,
> automation
> Reporter: Vojtech Prusa
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 12.14.0.AM1
>
> Attachments: central.tar.gz, image-2018-10-17-09-24-31-555.png, issue-reproduced-19-11-16.png, screenshot-1.png
>
>
> h2. This issue has been successfully reproduced on the following OSes:
> * Fedora 28
> * Fedora 29, JDK 8
> * RHEL 7.7, JDK 8
> h2. This issue is not reproducible on the following OSes:
> * OS X, JDK 11
> * Windows 10, JDK 8
> h2. Details describing this issue:
> There is "openInIDE" used in 3 places in "main.min.js" in central source code*. When the central reloads and works normally, "openInIDE" is a function (probably defined in Java code or somewhere out of the "main.min.js" file) with following implementation:
> function openInIDE() {
> var result = callJava(1, '9aee3b4a3f3b40ed26f47d66375b25e3', Array.prototype.slice.call(arguments));
> if (typeof result == 'string' && result.indexOf('org.eclipse.swt.browser.error') == 0) {
> var error = new Error(result.substring(29));
> throw error;
> }
> return result;
> }
> After the issue appears, "typedef openInIDE" is undefined, which causes probably the issues.
> *Additional information to the 3 places, where "openInIDE" appears - it appears in 2 functions:
> - registerButtonClicks() - here is the "openInIDE" needed for loading and displaying the central correctly
> - delegateToIDE(a, b) - here is the "openInIDE" needed for opening the wizard to the quickstart
> OLDER DESCRIPTION (does not describes the issue enough, but I decided to keep it for more details about the issue):
> ----------------------------------------------------------------------------------------------------------------------
> Sometimes central examples wizards fail to load and modal dialog is shown instead (screen attached).
> Nothing in Error log view.
> Restarting devstudio solves the issue.
> Adding screen and central tar of:
> devstudio-12.9.0.GA-v20180928-1629-B3448/workspaces/workspace/.metadata/.plugins/org.jboss.tools.central/central
> Addition info:
> Considering that central itests fails for this sometimes fresh installation without restart may cause this. Although it happen again after running devstudio for some time and restarting Central view.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (JBIDE-26697) Possible memory leak during Loading projects job when using cluster with lots of projects
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26697?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26697:
-------------------------------
Sprint: devex #173 Oct 2019, devex #175 Nov 2019, devex #176 Nov/Dec 2019 (was: devex #173 Oct 2019, devex #175 Nov 2019)
> Possible memory leak during Loading projects job when using cluster with lots of projects
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-26697
> URL: https://issues.jboss.org/browse/JBIDE-26697
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.12.0.Final
> Environment: Mac 10.14.5 (18F203), Fedora 29, crstudio GA-v20190626-0604-B4591
> Reporter: Josef Kopriva
> Assignee: André Dietisheim
> Priority: Major
> Fix For: 4.14.0.AM1
>
>
> Exception in error log:
> {code:java}
> eclipse.buildId=12.12.0.GA-v20190626-0604-B4591
> java.version=11.0.2
> java.vendor=Oracle Corporation
> BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_GB
> Framework arguments: -product com.jboss.devstudio.core.product -product com.jboss.devstudio.core.product -keyring /Users/jkopriva/.eclipse_keyring
> Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product com.jboss.devstudio.core.product -data file:/Users/jkopriva/workspace_B4591_3/ -product com.jboss.devstudio.core.product -keyring /Users/jkopriva/.eclipse_keyring
> org.eclipse.core.jobs
> Error
> Wed Jun 26 14:36:11 CEST 2019
> An internal error occurred during: "Loading projects...".
> java.lang.OutOfMemoryError: Java heap space
> at org.jboss.dmr.JSONParser.yyParse(JSONParser.java:877)
> at org.jboss.dmr.ModelNode.fromJSONString(ModelNode.java:1472)
> at com.openshift.internal.restclient.ResourceFactory.create(ResourceFactory.java:100)
> at com.openshift.internal.restclient.ResourceFactory.createInstanceFrom(ResourceFactory.java:149)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:304)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:275)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:264)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:171)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:160)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:151)
> at com.openshift.internal.restclient.capability.resources.ProjectTemplateListCapability.getCommonTemplates(ProjectTemplateListCapability.java:53)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceTreeItems$1.visit(ApplicationSourceTreeItems.java:121)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceTreeItems$1.visit(ApplicationSourceTreeItems.java:1)
> at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:94)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceTreeItems.loadTemplates(ApplicationSourceTreeItems.java:113)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceTreeItems.createChildren(ApplicationSourceTreeItems.java:61)
> at org.jboss.tools.openshift.internal.ui.treeitem.ObservableTreeItem.loadChildren(ObservableTreeItem.java:69)
> at org.jboss.tools.openshift.internal.ui.treeitem.ObservableTreeItem.load(ObservableTreeItem.java:56)
> at org.jboss.tools.openshift.internal.ui.treeitem.ObservableTreeItem.load(ObservableTreeItem.java:59)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.loadResources(NewApplicationWizardModel.java:247)
> at org.jboss.tools.openshift.internal.ui.wizard.common.AbstractProjectPage$3.doRun(AbstractProjectPage.java:255)
> 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, 6 months
[JBoss JIRA] (JBIDE-26869) CRC server adapter: OpenShift connection that is created is unusable at times
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26869?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26869:
-------------------------------
Sprint: devex #173 Oct 2019, devex #175 Nov 2019, devex #176 Nov/Dec 2019 (was: devex #173 Oct 2019, devex #175 Nov 2019)
> CRC server adapter: OpenShift connection that is created is unusable at times
> -----------------------------------------------------------------------------
>
> Key: JBIDE-26869
> URL: https://issues.jboss.org/browse/JBIDE-26869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.13.0.AM1
> Environment: CRC Beta5
> Reporter: André Dietisheim
> Assignee: André Dietisheim
> Priority: Critical
> Fix For: 4.14.0.AM1
>
> Attachments: crc-connection-error.mp4, start-crc-error-openshift-conn.mp4
>
>
> *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
> *Result:*
> Connection fails to authorize, reports that it cannot access resources using system:anonymous. Refreshing the connection doesn't help, so it's apparently not a timing issue (ex. creating the connection before the cluster is fully up and running)
> {code}
> com.openshift.restclient.authorization.ResourceForbiddenException: forbidden: User "system:anonymous" cannot get path "/oauth/authorize" forbidden: User "system:anonymous" cannot get path "/oauth/authorize"
> 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.okhttp.OpenShiftAuthenticator.tryAuth(OpenShiftAuthenticator.java:109)
> at com.openshift.internal.restclient.okhttp.OpenShiftAuthenticator.authenticate(OpenShiftAuthenticator.java:62)
> at okhttp3.internal.http.RetryAndFollowUpInterceptor.followUpRequest(RetryAndFollowUpInterceptor.kt:213)
> at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:102)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:112)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:87)
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:55)
> 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.DefaultClient.request(DefaultClient.java:315)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:307)
> 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.crc.server.core.listeners.ConfigureCRCFrameworksListener.configureOpenshift(ConfigureCRCFrameworksListener.java:102)
> at org.jboss.tools.openshift.internal.crc.server.core.listeners.ConfigureCRCFrameworksListener.configureFrameworks(ConfigureCRCFrameworksListener.java:73)
> at org.jboss.tools.openshift.internal.crc.server.core.listeners.ConfigureCRCFrameworksListener$1.run(ConfigureCRCFrameworksListener.java:66)
> 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, 6 months
[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)
4 years, 6 months