November 2019 - jbosstools-issues

[JBoss JIRA] (JBIDE-26954) Upgrade Mac machines to latest MacOS

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26954?page=com.atlassian.jira.plugi... ] Josef Kopriva edited comment on JBIDE-26954 at 11/22/19 6:59 AM: ----------------------------------------------------------------- dev-platform-mac1 updated to catalina zamek - upgraded to mojave was (Author: jkopriva): dev-platform-mac1 updated to catalina zamek - upgraded to majave > Upgrade Mac machines to latest MacOS > ------------------------------------ > > Key: JBIDE-26954 > URL: https://issues.jboss.org/browse/JBIDE-26954 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests > Affects Versions: 4.14.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.14.0.AM1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26954) Upgrade Mac machines to latest MacOS

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26954?page=com.atlassian.jira.plugi... ] Josef Kopriva commented on JBIDE-26954: --------------------------------------- dev-platform-mac1 updated to catalina zamek - upgraded to majave > Upgrade Mac machines to latest MacOS > ------------------------------------ > > Key: JBIDE-26954 > URL: https://issues.jboss.org/browse/JBIDE-26954 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests > Affects Versions: 4.14.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.14.0.AM1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26916) Dynamic Web Project shows errors after converting to maven project when using WildFly 18 as target runtime and Java 11

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-26916?page=com.atlassian.jira.plugi... ] Zbyněk Červinka edited comment on JBIDE-26916 at 11/22/19 6:24 AM: ------------------------------------------------------------------- [~jkopriva] I have reproduced this issue again, this time without adding the repos. I got the same error messages captured on the following printscreen (screen included in the description of this JIRA since I have created this JIRA): !dynamic_web_project_after_converting_to_maven.png|thumbnail! By the way, [~jkopriva], you metioned, that you get more error including *{color:#DE350B}Missing artifact jakarta.jws:jakarta.jws-api:jar:2.1.0{color}*. This error I got since the beginning of investigation of this issue, the error message is captured on the above added printscreen. I am going to add the error messages to the description of this issue to make the messages searchable, not just captured on image. h2. Additional info: The solution to this issue (adding dependency to the pom.xml) mentioned in the description of this JIRA is still valid, tested in the following 2 devstudios: h3. Red Hat CodeReady Studio (same version as it was used when creating this JIRA): Version: 12.13.0.GA Build id: GA-v20191024-0752-B5215 Build date: 20191024-0752 h3. Red Hat CodeReady Studio (todays devstudio, newest version): Version: 12.14.0.AM1 Build id: AM1-v20191122-0713-B5330 Build date: 20191122-0713 was (Author: zcervink): [~jkopriva] I have reproduced this issue again, this time without adding the repos. I got the same error messages captured on the following printscreen (screen included in the description of this JIRA since I have created this JIRA): !dynamic_web_project_after_converting_to_maven.png|thumbnail! By the way, [~jkopriva], you metioned, that you get more error including *{color:#DE350B}Missing artifact jakarta.jws:jakarta.jws-api:jar:2.1.0{color}*. This error I got since the beginning of investigation of this issue, the error message is captured on the above added printscreen. I am going to add the error messages to the description of this issue to make the messages searchable, not just captured on image. h2. Additional info: The solution to this issue (adding dependency to the pom.xml) mentioned in the description of this JIRA is still valid, tested in the following 2 devstudios: h2. Red Hat CodeReady Studio (same version as it was used when creating this JIRA): Version: 12.13.0.GA Build id: GA-v20191024-0752-B5215 Build date: 20191024-0752 h3. Red Hat CodeReady Studio (todays devstudio, newest version): Version: 12.14.0.AM1 Build id: AM1-v20191122-0713-B5330 Build date: 20191122-0713 > Dynamic Web Project shows errors after converting to maven project when using WildFly 18 as target runtime and Java 11 > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26916 > URL: https://issues.jboss.org/browse/JBIDE-26916 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.13.0.AM1 > Environment: All OSes > Reporter: Zbyněk Červinka > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.14.0.AM1 > > Attachments: RHCRS_preferences.png, dynamic_web_project_after_converting_to_maven.png, new_server_settings.png, project_facets_when_creating_the_project.png > > > h2. Basic information on this issue: > - Issue appears only when using WildFly 18 as target runtime and Java 11 (see the 'Steps to reproduce' section and printscreens in the attachment) > - Issue does not appear on WildFly 16 and on WildFly 17 (tested on both Java 8 and 11; this issue has not appeared even if I have mixed Java version settings in workspace/server runtime JRE/Project fFacets, no issue for any combination) > h2. Error messages from the Problems view: > * Missing artifact jakarta.jws:jakarta.jws-api:jar:2.1.0 pom.xml > * The container 'Maven Dependencies' references non existing library '/Users/zcervink/.m2/repository/jakarta/jws/jakarta.jws-api/2.1.0/jakarta.jws-api-2.1.0.jar' > * The project cannot be built until build path errors are resolved > h2. Tested solution - insert the following dependency into the pom.xml and all the problems in the Problems view disappear > {code:java} > <dependency> > <groupId>jakarta.jws</groupId> > <artifactId>jakarta.jws-api</artifactId> > <version>1.1.1</version> > </dependency> > {code} > h2. Red Hat CodeReady Studio version (version used to testing when creating this JIRA): > Version: 12.13.0.GA > Build id: GA-v20191024-0752-B5215 > Build date: 20191024-0752 > h2. Red Hat CodeReady Studio (newest version used to testing when updating this JIRA): > Version: 12.14.0.AM1 > Build id: AM1-v20191122-0713-B5330 > Build date: 20191122-0713 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26916) Dynamic Web Project shows errors after converting to maven project when using WildFly 18 as target runtime and Java 11

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-26916?page=com.atlassian.jira.plugi... ] Zbyněk Červinka updated JBIDE-26916: ------------------------------------ Description: h2. Basic information on this issue: - Issue appears only when using WildFly 18 as target runtime and Java 11 (see the 'Steps to reproduce' section and printscreens in the attachment) - Issue does not appear on WildFly 16 and on WildFly 17 (tested on both Java 8 and 11; this issue has not appeared even if I have mixed Java version settings in workspace/server runtime JRE/Project fFacets, no issue for any combination) h2. Error messages from the Problems view: * Missing artifact jakarta.jws:jakarta.jws-api:jar:2.1.0 pom.xml * The container 'Maven Dependencies' references non existing library '/Users/zcervink/.m2/repository/jakarta/jws/jakarta.jws-api/2.1.0/jakarta.jws-api-2.1.0.jar' * The project cannot be built until build path errors are resolved h2. Tested solution - insert the following dependency into the pom.xml and all the problems in the Problems view disappear {code:java} <dependency> <groupId>jakarta.jws</groupId> <artifactId>jakarta.jws-api</artifactId> <version>1.1.1</version> </dependency> {code} h2. Red Hat CodeReady Studio version (version used to testing when creating this JIRA): Version: 12.13.0.GA Build id: GA-v20191024-0752-B5215 Build date: 20191024-0752 h2. Red Hat CodeReady Studio (newest version used to testing when updating this JIRA): Version: 12.14.0.AM1 Build id: AM1-v20191122-0713-B5330 Build date: 20191122-0713 was: h2. Basic information on this issue: - Issue appears only when using WildFly 18 as target runtime and Java 11 (see the 'Steps to reproduce' section and printscreens in the attachment) - Issue does not appear on WildFly 16 and on WildFly 17 (tested on both Java 8 and 11; this issue has not appeared even if I have mixed Java version settings in workspace/server runtime JRE/Project fFacets, no issue for any combination) h2. Tested solution - insert the following dependency into the pom.xml and all the problems in the Problems view disappear {code:java} <dependency> <groupId>jakarta.jws</groupId> <artifactId>jakarta.jws-api</artifactId> <version>1.1.1</version> </dependency> {code} h2. Red Hat CodeReady Studio version: Version: 12.13.0.GA Build id: GA-v20191024-0752-B5215 Build date: 20191024-0752 > Dynamic Web Project shows errors after converting to maven project when using WildFly 18 as target runtime and Java 11 > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26916 > URL: https://issues.jboss.org/browse/JBIDE-26916 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.13.0.AM1 > Environment: All OSes > Reporter: Zbyněk Červinka > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.14.0.AM1 > > Attachments: RHCRS_preferences.png, dynamic_web_project_after_converting_to_maven.png, new_server_settings.png, project_facets_when_creating_the_project.png > > > h2. Basic information on this issue: > - Issue appears only when using WildFly 18 as target runtime and Java 11 (see the 'Steps to reproduce' section and printscreens in the attachment) > - Issue does not appear on WildFly 16 and on WildFly 17 (tested on both Java 8 and 11; this issue has not appeared even if I have mixed Java version settings in workspace/server runtime JRE/Project fFacets, no issue for any combination) > h2. Error messages from the Problems view: > * Missing artifact jakarta.jws:jakarta.jws-api:jar:2.1.0 pom.xml > * The container 'Maven Dependencies' references non existing library '/Users/zcervink/.m2/repository/jakarta/jws/jakarta.jws-api/2.1.0/jakarta.jws-api-2.1.0.jar' > * The project cannot be built until build path errors are resolved > h2. Tested solution - insert the following dependency into the pom.xml and all the problems in the Problems view disappear > {code:java} > <dependency> > <groupId>jakarta.jws</groupId> > <artifactId>jakarta.jws-api</artifactId> > <version>1.1.1</version> > </dependency> > {code} > h2. Red Hat CodeReady Studio version (version used to testing when creating this JIRA): > Version: 12.13.0.GA > Build id: GA-v20191024-0752-B5215 > Build date: 20191024-0752 > h2. Red Hat CodeReady Studio (newest version used to testing when updating this JIRA): > Version: 12.14.0.AM1 > Build id: AM1-v20191122-0713-B5330 > Build date: 20191122-0713 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26916) Dynamic Web Project shows errors after converting to maven project when using WildFly 18 as target runtime and Java 11

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-26916?page=com.atlassian.jira.plugi... ] Zbyněk Červinka commented on JBIDE-26916: ----------------------------------------- [~jkopriva] I have reproduced this issue again, this time without adding the repos. I got the same error messages captured on the following printscreen (screen included in the description of this JIRA since I have created this JIRA): !dynamic_web_project_after_converting_to_maven.png|thumbnail! By the way, [~jkopriva], you metioned, that you get more error including *{color:#DE350B}Missing artifact jakarta.jws:jakarta.jws-api:jar:2.1.0{color}*. This error I got since the beginning of investigation of this issue, the error message is captured on the above added printscreen. I am going to add the error messages to the description of this issue to make the messages searchable, not just captured on image. h2. Additional info: The solution to this issue (adding dependency to the pom.xml) mentioned in the description of this JIRA is still valid, tested in the following 2 devstudios: h2. Red Hat CodeReady Studio (same version as it was used when creating this JIRA): Version: 12.13.0.GA Build id: GA-v20191024-0752-B5215 Build date: 20191024-0752 h3. Red Hat CodeReady Studio (todays devstudio, newest version): Version: 12.14.0.AM1 Build id: AM1-v20191122-0713-B5330 Build date: 20191122-0713 > Dynamic Web Project shows errors after converting to maven project when using WildFly 18 as target runtime and Java 11 > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26916 > URL: https://issues.jboss.org/browse/JBIDE-26916 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.13.0.AM1 > Environment: All OSes > Reporter: Zbyněk Červinka > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.14.0.AM1 > > Attachments: RHCRS_preferences.png, dynamic_web_project_after_converting_to_maven.png, new_server_settings.png, project_facets_when_creating_the_project.png > > > h2. Basic information on this issue: > - Issue appears only when using WildFly 18 as target runtime and Java 11 (see the 'Steps to reproduce' section and printscreens in the attachment) > - Issue does not appear on WildFly 16 and on WildFly 17 (tested on both Java 8 and 11; this issue has not appeared even if I have mixed Java version settings in workspace/server runtime JRE/Project fFacets, no issue for any combination) > h2. Tested solution - insert the following dependency into the pom.xml and all the problems in the Problems view disappear > {code:java} > <dependency> > <groupId>jakarta.jws</groupId> > <artifactId>jakarta.jws-api</artifactId> > <version>1.1.1</version> > </dependency> > {code} > h2. Red Hat CodeReady Studio version: > Version: 12.13.0.GA > Build id: GA-v20191024-0752-B5215 > Build date: 20191024-0752 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26954) Upgrade Mac machines to latest MacOS

by Josef Kopriva (Jira)

Josef Kopriva created JBIDE-26954: ------------------------------------- Summary: Upgrade Mac machines to latest MacOS Key: JBIDE-26954 URL: https://issues.jboss.org/browse/JBIDE-26954 Project: Tools (JBoss Tools) Issue Type: Task Components: integration-tests Affects Versions: 4.14.0.AM1 Reporter: Josef Kopriva Assignee: Josef Kopriva Fix For: 4.14.0.AM1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4813) Pls add more camel elements in GUI palette

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBDS-4813?page=com.atlassian.jira.plugin.... ] Jeff MAURY reassigned JBDS-4813: -------------------------------- Assignee: Aurélien Pupier > Pls add more camel elements in GUI palette > ------------------------------------------ > > Key: JBDS-4813 > URL: https://issues.jboss.org/browse/JBDS-4813 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Feature Request > Components: integration > Affects Versions: 12.13.0.GA > Reporter: Vicky Wu > Assignee: Aurélien Pupier > Priority: Major > > I am using the CodeReady Studio to design my camel route, but I found some elements are missing from the GUI, I have to modify the source code, it is not convenient. Would you pls add more components on the GUI palette, especially belows: > toD > normal http/https (not netty) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26947) CDI Web Project created with CDI 1.2 settings shows version 1.1 in the beans.xml

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26947?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26947: ------------------------------- Fix Version/s: 4.14.0.AM1 (was: 4.13.0.Final) > CDI Web Project created with CDI 1.2 settings shows version 1.1 in the beans.xml > -------------------------------------------------------------------------------- > > Key: JBIDE-26947 > URL: https://issues.jboss.org/browse/JBIDE-26947 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi, cdi-extensions > Affects Versions: 4.13.0.Final > Environment: OS X > Reporter: Zbyněk Červinka > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.14.0.AM1 > > Attachments: Project Facets with CDI 1.2 settings.png, beans.xml-gui.png, beans.xml-source.png > > > When you create new CDI Web Project and during the process of project creation you set CDI 1.2 (in the Project Facets window), you will get a project with CDI 1.1 set in the beans.xml. > h3. See the Project Facets with the CDI 1.2 settings (window accessible during creating new CDI Web Project): > * !Project Facets with CDI 1.2 settings.png|thumbnail! > h3. See the beans.xml with the CDI 1.1 settings: > * beans.xml GUI: > * !beans.xml-gui.png|thumbnail! > * beans.xml text source code: > * !beans.xml-source.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26953) consider to integrade wad.jar code hot deploymend within jboss tools

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26953?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26953: ------------------------------- Affects Version/s: 4.13.0.Final > consider to integrade wad.jar code hot deploymend within jboss tools > -------------------------------------------------------------------- > > Key: JBIDE-26953 > URL: https://issues.jboss.org/browse/JBIDE-26953 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Affects Versions: 4.13.0.Final > Reporter: nimo stephan > Priority: Major > Fix For: LATER > > > Would be nice to integrate https://wad.sh/ into jboss tools to enable hot code deployment of java source files. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26953) consider to integrade wad.jar code hot deploymend within jboss tools

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26953?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26953: ------------------------------- Component/s: server > consider to integrade wad.jar code hot deploymend within jboss tools > -------------------------------------------------------------------- > > Key: JBIDE-26953 > URL: https://issues.jboss.org/browse/JBIDE-26953 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.13.0.Final > Reporter: nimo stephan > Priority: Major > Fix For: LATER > > > Would be nice to integrate https://wad.sh/ into jboss tools to enable hot code deployment of java source files. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 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 November 2019