[
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)