June 2020 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26970) Validator: The annotation @PathParam must define the attribute value

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-26970?page=com.atlassian.jira.plug... ] Jeff MAURY updated JBIDE-26970: ------------------------------- Story Points: 5 > Validator: The annotation @PathParam must define the attribute value > -------------------------------------------------------------------- > > Key: JBIDE-26970 > URL: https://issues.redhat.com/browse/JBIDE-26970 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: webservices > Affects Versions: 4.13.0.Final > Reporter: nimo stephan > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.16.0.Final > > 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)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27323) Installing all SW from central throws multiple dependency errors in Studio/Tools with openjdk 1.8

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-27323?page=com.atlassian.jira.plug... ] Jeff MAURY updated JBIDE-27323: ------------------------------- Sprint: devex #186 July 2020 > Installing all SW from central throws multiple dependency errors in Studio/Tools with openjdk 1.8 > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-27323 > URL: https://issues.redhat.com/browse/JBIDE-27323 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, central-update > Affects Versions: 4.16.0.AM1 > Reporter: Ondrej Dockal > Assignee: Stephane Bouchet > Priority: Critical > Attachments: Screenshot_20200622_120608.png, eclipse-tools.log > > > Installing all SW from central with enabled early access in BYOE scenario (including eclipse-jee 2020-06 R and JBoss Tools installed from staging update site for 4.16.0.AM1) ended up with many errors. > > ie.: > {code} > eclipse.buildId=12.16.0.AM1-v20200619-0713-B6514eclipse.buildId=12.16.0.AM1-v20200619-0713-B6514java.version=1.8.0_252java.vendor=Oracle CorporationBootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_USFramework arguments: -product com.jboss.devstudio.core.productCommand-line arguments: -data file:/home/odockal/workspace_12160AM1-B6514/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.springframework.ide.eclipse.wizardErrorMon Jun 22 11:57:00 CEST 2020FrameworkEvent ERROR > org.osgi.framework.BundleException: Could not resolve module: org.springframework.ide.eclipse.wizard [1477] Unresolved requirement: Require-Bundle: org.springsource.ide.eclipse.commons.gettingstarted; bundle-version="3.5.0"; resolution:="optional" Unresolved requirement: Require-Bundle: org.springsource.ide.eclipse.commons.browser; bundle-version="[3.5.0,4.0.0)"; resolution:="optional" Unresolved requirement: Require-Bundle: org.springframework.ide.eclipse.quickfix -> Bundle-SymbolicName: org.springframework.ide.eclipse.quickfix; bundle-version="3.9.12.202003180620-RELEASE"; singleton:="true" org.springframework.ide.eclipse.quickfix [1469] No resolution report for the bundle. Bundle was not resolved because of a uses constraint violation. org.apache.felix.resolver.reason.ReasonException: Uses constraint violation. Unable to resolve resource org.springframework.ide.eclipse.quickfix [osgi.identity; osgi.identity="org.springframework.ide.eclipse.quickfix"; type="osgi.bundle"; version:Version="3.9.12.202003180620-RELEASE"; singleton:="true"] because it is exposed to package 'javax.annotation' from resources org.eclipse.osgi [osgi.identity; type="osgi.bundle"; version:Version="3.15.300.v20200520-1959"; osgi.identity="org.eclipse.osgi"; singleton:="true"] and javax.annotation [osgi.identity; type="osgi.bundle"; version:Version="1.3.5.v20200504-1837"; osgi.identity="javax.annotation"] via two dependency chains. > Chain 1: org.springframework.ide.eclipse.quickfix [osgi.identity; osgi.identity="org.springframework.ide.eclipse.quickfix"; type="osgi.bundle"; version:Version="3.9.12.202003180620-RELEASE"; singleton:="true"] require: (osgi.wiring.bundle=org.eclipse.core.runtime) | provide: osgi.wiring.bundle: org.eclipse.core.runtime org.eclipse.osgi [osgi.identity; type="osgi.bundle"; version:Version="3.15.300.v20200520-1959"; osgi.identity="org.eclipse.osgi"; singleton:="true"] > Chain 2: org.springframework.ide.eclipse.quickfix [osgi.identity; osgi.identity="org.springframework.ide.eclipse.quickfix"; type="osgi.bundle"; version:Version="3.9.12.202003180620-RELEASE"; singleton:="true"] require: (osgi.wiring.bundle=org.springframework.context) | provide: osgi.wiring.bundle; bundle-version:Version="4.3.23.20190313-CI"; osgi.wiring.bundle="org.springframework.context" org.springframework.context [osgi.identity; osgi.identity="org.springframework.context"; type="osgi.bundle"; version:Version="4.3.23.20190313-CI"] import: (&(osgi.wiring.package=javax.annotation)(version>=0.0.0)) | export: osgi.wiring.package: javax.annotation javax.annotation [osgi.identity; type="osgi.bundle"; version:Version="1.3.5.v20200504-1837"; osgi.identity="javax.annotation"] at org.eclipse.osgi.container.Module.start(Module.java:463) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1845) at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1838) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1779) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1743) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1665) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345) > {code} > > Please see attached log. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26970) Validator: The annotation @PathParam must define the attribute value

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-26970?page=com.atlassian.jira.plug... ] Jeff MAURY updated JBIDE-26970: ------------------------------- Fix Version/s: 4.16.0.Final (was: 4.16.0.AM1) > Validator: The annotation @PathParam must define the attribute value > -------------------------------------------------------------------- > > Key: JBIDE-26970 > URL: https://issues.redhat.com/browse/JBIDE-26970 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: webservices > Affects Versions: 4.13.0.Final > Reporter: nimo stephan > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.16.0.Final > > 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)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27125) OpenShift: Create Service` command should ask input for required and optionally not required service template properties

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-27125?page=com.atlassian.jira.plug... ] Jeff MAURY updated JBIDE-27125: ------------------------------- Sprint: devex #183 May 2020, devex #184 May 2020 (was: devex #183 May 2020, devex #184 May 2020, devex #186 July 2020) > OpenShift: Create Service` command should ask input for required and optionally not required service template properties > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-27125 > URL: https://issues.redhat.com/browse/JBIDE-27125 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.14.0.Final > Reporter: Jeff MAURY > Assignee: Stephane Bouchet > Priority: Major > Fix For: 4.16.0.AM1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27322) Cannot start Eclipse when installing from update site

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27322?page=com.atlassian.jira.plug... ] Stephane Bouchet commented on JBIDE-27322: ------------------------------------------ Master is unfrozen, let's see if some TP updates for 4.16.0.Final may improve the situation. > Cannot start Eclipse when installing from update site > ----------------------------------------------------- > > Key: JBIDE-27322 > URL: https://issues.redhat.com/browse/JBIDE-27322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, install-tests > Affects Versions: 4.16.0.AM1 > Reporter: Stephane Bouchet > Priority: Critical > Fix For: 4.16.0.Final > > Attachments: .log, .log > > > when smoke testing4.16.0.AM1, using a bare Eclipse 4.16 and installing everything from update site, I cannot restart eclipse. > the attached log indicates an SWT theme problem, but no JBoss stacktrace involved. > Test performed using Linux RHEL 8, with jdk1.8 > Affect both Devstudio and jbosstools. > When switching to JDK11, the problem went away. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27322) Cannot start Eclipse when installing from update site

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27322?page=com.atlassian.jira.plug... ] Stephane Bouchet edited comment on JBIDE-27322 at 6/23/20 11:10 AM: -------------------------------------------------------------------- [~jeffmaury], [~odockal]: I *may* have found the feature that causes issues because I tried to pinpoint by installing not all features at once. The ones that are failing are the *hibernate tools* and the *JBoss Maven hibernate Configurator* Installing *all* but not these two is successful, then when I tried to install either one of these, I always get the error. was (Author: stephane.bouchet): [~jeffmaury], [~odockal]: I *may* have found the feature that causes issues because I tried to pinpoint by installing not all features at once. The ones that are failing are the *hibernate tools* and the *JBoss Maven hibernate Configurator* Installing *all* but not these two is successful, but when I tried to install either one of these, I always get the error. > Cannot start Eclipse when installing from update site > ----------------------------------------------------- > > Key: JBIDE-27322 > URL: https://issues.redhat.com/browse/JBIDE-27322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, install-tests > Affects Versions: 4.16.0.AM1 > Reporter: Stephane Bouchet > Priority: Critical > Fix For: 4.16.0.Final > > Attachments: .log, .log > > > when smoke testing4.16.0.AM1, using a bare Eclipse 4.16 and installing everything from update site, I cannot restart eclipse. > the attached log indicates an SWT theme problem, but no JBoss stacktrace involved. > Test performed using Linux RHEL 8, with jdk1.8 > Affect both Devstudio and jbosstools. > When switching to JDK11, the problem went away. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27285) Add support for Wildfly 20.0.0.Beta1

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-27285?page=com.atlassian.jira.plug... ] Josef Kopriva commented on JBIDE-27285: --------------------------------------- [~rstryker] I suppose this is resolved now? > Add support for Wildfly 20.0.0.Beta1 > ------------------------------------ > > Key: JBIDE-27285 > URL: https://issues.redhat.com/browse/JBIDE-27285 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.15.0.Final > Reporter: Jeff MAURY > Assignee: Robert Stryker > Priority: Major > Fix For: 4.16.0.AM1 > > > Widlfy 20.0.0.Beta1 is out, we should add a server adapter. Seems to be a bug fix release -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27322) Cannot start Eclipse when installing from update site

by Ondrej Dockal (Jira)

[ https://issues.redhat.com/browse/JBIDE-27322?page=com.atlassian.jira.plug... ] Ondrej Dockal commented on JBIDE-27322: --------------------------------------- [~stephane.bouchet] I could not reproduce using dark theme neither all bits from studio update site nor hibernate only... > Cannot start Eclipse when installing from update site > ----------------------------------------------------- > > Key: JBIDE-27322 > URL: https://issues.redhat.com/browse/JBIDE-27322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, install-tests > Affects Versions: 4.16.0.AM1 > Reporter: Stephane Bouchet > Priority: Critical > Fix For: 4.16.0.Final > > Attachments: .log, .log > > > when smoke testing4.16.0.AM1, using a bare Eclipse 4.16 and installing everything from update site, I cannot restart eclipse. > the attached log indicates an SWT theme problem, but no JBoss stacktrace involved. > Test performed using Linux RHEL 8, with jdk1.8 > Affect both Devstudio and jbosstools. > When switching to JDK11, the problem went away. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27188) Cannot create Web Service Client using CXF 3.3.5 and wildfly 18 on Java 11

by Ondrej Dockal (Jira)

[ https://issues.redhat.com/browse/JBIDE-27188?page=com.atlassian.jira.plug... ] Ondrej Dockal commented on JBIDE-27188: --------------------------------------- [~rstryker] [~jeffmaury] I think this has been resolved, right? Can we state that in Jira resolution? > Cannot create Web Service Client using CXF 3.3.5 and wildfly 18 on Java 11 > -------------------------------------------------------------------------- > > Key: JBIDE-27188 > URL: https://issues.redhat.com/browse/JBIDE-27188 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.15.0.AM1 > Reporter: Ondrej Dockal > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.16.x > > > When trying to create Web Service client I get: > {code} > -Djava.endorsed.dirs=/home/odockal/git/jbosstools-integration-tests/tests/org.jboss.tools.ws.ui.bot.test/target/requirements/apache-cxf-2.x/apache-cxf-3.3.5 is not supported. Endorsed standards and standalone APIs > in modular form will be supported via the concept of upgradeable modules. > Error: Could not create the Java Virtual Machine. > Error: A fatal exception has occurred. Program will exit. > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27318) org.osgi.framework.BundleException: Could not resolve module: org.eclipse.linuxtools.docker.core in jbosstools-openshift

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27318?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-27318: ------------------------------------- Sprint: devex #186 July 2020 (was: devex #185 June 2020) > org.osgi.framework.BundleException: Could not resolve module: org.eclipse.linuxtools.docker.core in jbosstools-openshift > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-27318 > URL: https://issues.redhat.com/browse/JBIDE-27318 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.16.0.AM1 > Reporter: Ondrej Dockal > Assignee: Stephane Bouchet > Priority: Blocker > Fix For: 4.16.0.Final > > Attachments: cdk-itests-build.log > > > We got broken dependencies coming from org.eclipse.linuxtools.docker.core/reddeer appearing in openshift/cdk itests when starting IDE. > > Please see attached log. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 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 June 2020