[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:
------------------------------------
Steps to Reproduce:
1) Add and configure 2 maven repositories to the RHCRS (*Preferences -> JBoss Tools -> JBoss Maven Integration -> Configure Maven Repositories...*):
- *ID:* jboss-public-repository
- *Name:* JBoss Public
- *URL:* https://repository.jboss.org/nexus/content/groups/public-jboss/
- *ID:* jboss-maven-repository
- *Name:* jboss-maven-repository
- *URL:* https://repository.jboss.org/maven2/
2) Create new Dynamic Web Project (use *WildFly 18 runtime*, Java 11 and CDI 2.0)
3) Convert the project to maven project
- right click on the project -> Configure -> Convert to Maven Project
- packaging = WAR
- click *Finish*
4) On the next window wait untill all the Maven Dependencies become GREEN TICKS, then click Finish
5) Now you see the following errors in the Problems view:
!dynamic_web_project_after_converting_to_maven.png|thumbnail!
For more information about used settings to reproduce this issue see the 3 following printscreens:
!dynamic_web_project_after_converting_to_maven.png|thumbnail!
!new_server_settings.png|thumbnail!
!project_facets_when_creating_the_project.png|thumbnail!
was:
1) Add and configure 2 maven repositories to the RHCRS (*Preferences -> JBoss Tools -> JBoss Maven Integration -> Configure Maven Repositories...*):
- *ID:* jboss-public-repository
- *Name:* JBoss Public
- *URL:* https://repository.jboss.org/nexus/content/groups/public-jboss/
- *ID:* jboss-maven-repository
- *Name:* jboss-maven-repository
- *URL:* https://repository.jboss.org/maven2/
2) Create new Dynamic Web Project (use *WildFly 18 runtime*, Java 11 and CDI 2.0)
3) Convert the project to maven project
- right click on the project -> Configure -> Convert to Maven Project
- packaging = WAR
- click *Finish*
4) On the next window wait untill all the Maven Dependencies become GREEN TICKS, then click Finish
5) Now you see the following errors in the Problems view:
!dynamic_web_project_after_converting_to_maven.png|thumbnail!
For more information about used settings to reproduce this issue see the 3 following printscreens:
> 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
> 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
> - 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)
5 years, 1 month
[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:
------------------------------------
Steps to Reproduce:
1) Add and configure 2 maven repositories to the RHCRS (*Preferences -> JBoss Tools -> JBoss Maven Integration -> Configure Maven Repositories...*):
- *ID:* jboss-public-repository
- *Name:* JBoss Public
- *URL:* https://repository.jboss.org/nexus/content/groups/public-jboss/
- *ID:* jboss-maven-repository
- *Name:* jboss-maven-repository
- *URL:* https://repository.jboss.org/maven2/
2) Create new Dynamic Web Project (use *WildFly 18 runtime*, Java 11 and CDI 2.0)
3) Convert the project to maven project
- right click on the project -> Configure -> Convert to Maven Project
- packaging = WAR
- click *Finish*
4) On the next window wait untill all the Maven Dependencies become GREEN TICKS, then click Finish
5) Now you see the following errors in the Problems view:
!dynamic_web_project_after_converting_to_maven.png|thumbnail!
For more information about used settings to reproduce this issue see the 3 following printscreens:
!new_server_settings.png|thumbnail!
!project_facets_when_creating_the_project.png|thumbnail!
was:
1) Add and configure 2 maven repositories to the RHCRS (*Preferences -> JBoss Tools -> JBoss Maven Integration -> Configure Maven Repositories...*):
- *ID:* jboss-public-repository
- *Name:* JBoss Public
- *URL:* https://repository.jboss.org/nexus/content/groups/public-jboss/
- *ID:* jboss-maven-repository
- *Name:* jboss-maven-repository
- *URL:* https://repository.jboss.org/maven2/
2) Create new Dynamic Web Project (use *WildFly 18 runtime*, Java 11 and CDI 2.0)
3) Convert the project to maven project
- right click on the project -> Configure -> Convert to Maven Project
- packaging = WAR
- click *Finish*
4) On the next window wait untill all the Maven Dependencies become GREEN TICKS, then click Finish
5) Now you see the following errors in the Problems view:
!dynamic_web_project_after_converting_to_maven.png|thumbnail!
For more information about used settings to reproduce this issue see the 3 following printscreens:
!dynamic_web_project_after_converting_to_maven.png|thumbnail!
!new_server_settings.png|thumbnail!
!project_facets_when_creating_the_project.png|thumbnail!
> 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
> 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
> - 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)
5 years, 1 month
[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:
------------------------------------
Attachment: project_facets_when_creating_the_project.png
> 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
> 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
> - 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)
5 years, 1 month
[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:
------------------------------------
Attachment: new_server_settings.png
> 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
> 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
> - 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)
5 years, 1 month
[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:
------------------------------------
Attachment: RHCRS_preferences.png
> 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
> Attachments: RHCRS_preferences.png, dynamic_web_project_after_converting_to_maven.png
>
>
> h2. Basic information on this issue:
> - Issue appears only when using WildFly 18 as target runtime and Java 11
> - 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)
5 years, 1 month
[JBoss JIRA] (JBIDE-26914) Remediation page - cannot satisfy dependency when installing JBT from update site into Eclipse
by Stephane Bouchet (Jira)
[ https://issues.jboss.org/browse/JBIDE-26914?page=com.atlassian.jira.plugi... ]
Stephane Bouchet commented on JBIDE-26914:
------------------------------------------
I can confirm that installing everything from central *except* nodeclipse does not shows remediation page.
[~odockal] can you double check the same behavior on your side ?
If so, i assume this is a known issue so far.
> Remediation page - cannot satisfy dependency when installing JBT from update site into Eclipse
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-26914
> URL: https://issues.jboss.org/browse/JBIDE-26914
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, central-update
> Affects Versions: 4.13.0.Final
> Environment: Fedora 29, Java 11
> Reporter: Ondrej Dockal
> Assignee: Stephane Bouchet
> Priority: Critical
>
> When trying to install JBT from update site (http://download.jboss.org/jbosstools/photon/staging/updates/) into Eclipse 2019-09 JEE (https://www.eclipse.org/downloads/packages/release/2019-09/r/eclipse-ide-...) I got remediation page with this errors:
> {code}
> Your original request has been modified.
> "WST JSON Core" is already installed, so an update will be performed instead.
> "Eclipse JSON Editor and Tools" is already installed, so an update will be performed instead.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: Eclipse JSON Editor and Tools 1.1.5.v201908281850 (org.eclipse.wst.json_ui.feature.feature.group 1.1.5.v201908281850)
> Software currently installed: Eclipse Web Developer Tools 3.15.0.v201908192247 (org.eclipse.wst.web_ui.feature.feature.group 3.15.0.v201908192247)
> Only one of the following can be installed at once:
> Eclipse JSON Editor and Tools 1.1.5.v201904210526 (org.eclipse.wst.json_ui.feature.feature.jar 1.1.5.v201904210526)
> Eclipse JSON Editor and Tools 1.1.5.v201908281850 (org.eclipse.wst.json_ui.feature.feature.jar 1.1.5.v201908281850)
> Cannot satisfy dependency:
> From: Eclipse JSON Editor and Tools 1.1.5.v201904210526 (org.eclipse.wst.json_ui.feature.feature.group 1.1.5.v201904210526)
> To: org.eclipse.equinox.p2.iu; org.eclipse.wst.json_ui.feature.feature.jar [1.1.5.v201904210526,1.1.5.v201904210526]
> Cannot satisfy dependency:
> From: Eclipse JSON Editor and Tools 1.1.5.v201908281850 (org.eclipse.wst.json_ui.feature.feature.group 1.1.5.v201908281850)
> To: org.eclipse.equinox.p2.iu; org.eclipse.wst.json_ui.feature.feature.jar [1.1.5.v201908281850,1.1.5.v201908281850]
> Cannot satisfy dependency:
> From: Eclipse Web Developer Tools 3.15.0.v201908192247 (org.eclipse.wst.web_ui.feature.feature.group 3.15.0.v201908192247)
> To: org.eclipse.equinox.p2.iu; org.eclipse.wst.json_ui.feature.feature.group [1.1.5.v201904210526,1.1.5.v201904210526]
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (JBIDE-26914) Remediation page - cannot satisfy dependency when installing JBT from update site into Eclipse
by Stephane Bouchet (Jira)
[ https://issues.jboss.org/browse/JBIDE-26914?page=com.atlassian.jira.plugi... ]
Stephane Bouchet edited comment on JBIDE-26914 at 10/30/19 10:06 AM:
---------------------------------------------------------------------
seems a duplicate of JBIDE-26818.
BTW, Tern is coming from nodeclipse at version 1.1.0 and we provide it as 1.3.0 with Jboss.
As we noticed earlier, new nodeclipse repo (https://nodeclipse.github.io/updates/) is not stable enough to be used as is, as it breaks our CI with egit errors, too.
we decided with [~jeffmaury] to mirror it on jboss side to avoid such errors, but for next release.
was (Author: stephane.bouchet):
seems a duplicate of JBIDE-26818.
Also, i cannot reproduce after updating Mylyn in the first place ( as the same step as WTP update ).
BTW, Tern is coming from nodeclipse at version 1.1.0 and we provide it as 1.3.0 with Jboss.
As we noticed earlier, new nodeclipse repo (https://nodeclipse.github.io/updates/) is not stable enough to be used as is, as it breaks our CI with egit errors, too.
we decided with [~jeffmaury] to mirror it on jboss side to avoid such errors, but for next release.
> Remediation page - cannot satisfy dependency when installing JBT from update site into Eclipse
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-26914
> URL: https://issues.jboss.org/browse/JBIDE-26914
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, central-update
> Affects Versions: 4.13.0.Final
> Environment: Fedora 29, Java 11
> Reporter: Ondrej Dockal
> Assignee: Stephane Bouchet
> Priority: Critical
>
> When trying to install JBT from update site (http://download.jboss.org/jbosstools/photon/staging/updates/) into Eclipse 2019-09 JEE (https://www.eclipse.org/downloads/packages/release/2019-09/r/eclipse-ide-...) I got remediation page with this errors:
> {code}
> Your original request has been modified.
> "WST JSON Core" is already installed, so an update will be performed instead.
> "Eclipse JSON Editor and Tools" is already installed, so an update will be performed instead.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: Eclipse JSON Editor and Tools 1.1.5.v201908281850 (org.eclipse.wst.json_ui.feature.feature.group 1.1.5.v201908281850)
> Software currently installed: Eclipse Web Developer Tools 3.15.0.v201908192247 (org.eclipse.wst.web_ui.feature.feature.group 3.15.0.v201908192247)
> Only one of the following can be installed at once:
> Eclipse JSON Editor and Tools 1.1.5.v201904210526 (org.eclipse.wst.json_ui.feature.feature.jar 1.1.5.v201904210526)
> Eclipse JSON Editor and Tools 1.1.5.v201908281850 (org.eclipse.wst.json_ui.feature.feature.jar 1.1.5.v201908281850)
> Cannot satisfy dependency:
> From: Eclipse JSON Editor and Tools 1.1.5.v201904210526 (org.eclipse.wst.json_ui.feature.feature.group 1.1.5.v201904210526)
> To: org.eclipse.equinox.p2.iu; org.eclipse.wst.json_ui.feature.feature.jar [1.1.5.v201904210526,1.1.5.v201904210526]
> Cannot satisfy dependency:
> From: Eclipse JSON Editor and Tools 1.1.5.v201908281850 (org.eclipse.wst.json_ui.feature.feature.group 1.1.5.v201908281850)
> To: org.eclipse.equinox.p2.iu; org.eclipse.wst.json_ui.feature.feature.jar [1.1.5.v201908281850,1.1.5.v201908281850]
> Cannot satisfy dependency:
> From: Eclipse Web Developer Tools 3.15.0.v201908192247 (org.eclipse.wst.web_ui.feature.feature.group 3.15.0.v201908192247)
> To: org.eclipse.equinox.p2.iu; org.eclipse.wst.json_ui.feature.feature.group [1.1.5.v201904210526,1.1.5.v201904210526]
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[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:
------------------------------------
Steps to Reproduce:
1) Add and configure 2 maven repositories to the RHCRS (*Preferences -> JBoss Tools -> JBoss Maven Integration -> Configure Maven Repositories...*):
- *ID:* jboss-public-repository
- *Name:* JBoss Public
- *URL:* https://repository.jboss.org/nexus/content/groups/public-jboss/
- *ID:* jboss-maven-repository
- *Name:* jboss-maven-repository
- *URL:* https://repository.jboss.org/maven2/
2) Create new Dynamic Web Project (use *WildFly 18 runtime*, Java 11 and CDI 2.0)
3) Convert the project to maven project
- right click on the project -> Configure -> Convert to Maven Project
- packaging = WAR
- click *Finish*
4) On the next window all the Maven Dependencies are GREEN TICKS, now click Finish
5) Now you see the following errors in the Problems view:
!dynamic_web_project_after_converting_to_maven.png|thumbnail!
was:
1) Add and configure 2 maven repositories to the RHCRS (*Preferences -> JBoss Tools -> JBoss Maven Integration -> Configure Maven Repositories...*):
- *ID:* jboss-public-repository
- *Name:* JBoss Public
- *URL:* https://repository.jboss.org/nexus/content/groups/public-jboss/
- *ID:* jboss-maven-repository
- *Name:* jboss-maven-repository
- *URL:* https://repository.jboss.org/maven2/
2) Create new Dynamic Web Project (use *WildFly 18 runtime*, Java 11 and CDI 2.0)
3) Convert the project to maven project
- Right click on the project -> Configure -> Convert to Maven Project
- packaging = WAR
- click *Finish*
4) On the next window all the Maven Dependencies are GREEN TICKS, now click Finish
5) Now you see the following errors in the Problems view:
!dynamic_web_project_after_converting_to_maven.png|thumbnail!
> 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
> Attachments: dynamic_web_project_after_converting_to_maven.png
>
>
> h2. Basic information on this issue:
> - Issue appears only when using WildFly 18 as target runtime and Java 11
> - 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)
5 years, 1 month
[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:
------------------------------------
Steps to Reproduce:
1) Add and configure 2 maven repositories to the RHCRS (*Preferences -> JBoss Tools -> JBoss Maven Integration -> Configure Maven Repositories...*):
- *ID:* jboss-public-repository
- *Name:* JBoss Public
- *URL:* https://repository.jboss.org/nexus/content/groups/public-jboss/
- *ID:* jboss-maven-repository
- *Name:* jboss-maven-repository
- *URL:* https://repository.jboss.org/maven2/
2) Create new Dynamic Web Project (use *WildFly 18 runtime*, Java 11 and CDI 2.0)
3) Convert the project to maven project
- right click on the project -> Configure -> Convert to Maven Project
- packaging = WAR
- click *Finish*
4) On the next window wait untill all the Maven Dependencies become GREEN TICKS, then click Finish
5) Now you see the following errors in the Problems view:
!dynamic_web_project_after_converting_to_maven.png|thumbnail!
was:
1) Add and configure 2 maven repositories to the RHCRS (*Preferences -> JBoss Tools -> JBoss Maven Integration -> Configure Maven Repositories...*):
- *ID:* jboss-public-repository
- *Name:* JBoss Public
- *URL:* https://repository.jboss.org/nexus/content/groups/public-jboss/
- *ID:* jboss-maven-repository
- *Name:* jboss-maven-repository
- *URL:* https://repository.jboss.org/maven2/
2) Create new Dynamic Web Project (use *WildFly 18 runtime*, Java 11 and CDI 2.0)
3) Convert the project to maven project
- right click on the project -> Configure -> Convert to Maven Project
- packaging = WAR
- click *Finish*
4) On the next window all the Maven Dependencies are GREEN TICKS, now click Finish
5) Now you see the following errors in the Problems view:
!dynamic_web_project_after_converting_to_maven.png|thumbnail!
> 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
> Attachments: dynamic_web_project_after_converting_to_maven.png
>
>
> h2. Basic information on this issue:
> - Issue appears only when using WildFly 18 as target runtime and Java 11
> - 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)
5 years, 1 month
[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:
------------------------------------
Steps to Reproduce:
1) Add and configure 2 maven repositories to the RHCRS (*Preferences -> JBoss Tools -> JBoss Maven Integration -> Configure Maven Repositories...*):
- *ID:* jboss-public-repository
- *Name:* JBoss Public
- *URL:* https://repository.jboss.org/nexus/content/groups/public-jboss/
- *ID:* jboss-maven-repository
- *Name:* jboss-maven-repository
- *URL:* https://repository.jboss.org/maven2/
2) Create new Dynamic Web Project (use *WildFly 18 runtime*, Java 11 and CDI 2.0)
3) Convert the project to maven project
- Right click on the project -> Configure -> Convert to Maven Project
- packaging = WAR
- click *Finish*
4) On the next window all the Maven Dependencies are GREEN TICKS, now click Finish
5) Now you see the following errors in the Problems view:
!dynamic_web_project_after_converting_to_maven.png|thumbnail!
was:
1) Add and configure 2 maven repositories to the RHCRS (*Preferences -> JBoss Tools -> JBoss Maven Integration -> Configure Maven Repositories...*):
- *ID:* jboss-public-repository
- *Name:* JBoss Public
- *URL:* https://repository.jboss.org/nexus/content/groups/public-jboss/
- *ID:* jboss-maven-repository
- *Name:* jboss-maven-repository
- *URL:* https://repository.jboss.org/maven2/
2) Create new Dynamic Web Project (use *WildFly 18 runtime*, Java 11 and CDI 2.0)
3) Convert the project to maven project
- Right click -> Configure -> Convert to Maven Project
- packaging = WAR
- click *Finish*
4) On the next window all the Maven Dependencies are GREEN TICKS, now click Finish
5) Now you see the following errors in the Problems view:
!dynamic_web_project_after_converting_to_maven.png|thumbnail!
> 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
> Attachments: dynamic_web_project_after_converting_to_maven.png
>
>
> h2. Basic information on this issue:
> - Issue appears only when using WildFly 18 as target runtime and Java 11
> - 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)
5 years, 1 month