Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-26916

Dynamic Web Project shows errors after converting to maven project when using WildFly 18 as target runtime and Java 11

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • 4.30.x
    • 4.13.0.AM1
    • maven
    • None
    • Hide

      1) Add and configure 2 maven repositories to the RHCRS (Preferences -> JBoss Tools -> JBoss Maven Integration -> Configure Maven Repositories...):

      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 (whether the "Delete original references from project" checkbox is or is not checked does not matter, the issue appears anyway)
      5) Now you see the following errors in the Problems view:

      For more information about used settings to reproduce this issue see the 3 following printscreens:

      Show
      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 (whether the "Delete original references from project" checkbox is or is not checked does not matter, the issue appears anyway) 5) Now you see the following errors in the Problems view: For more information about used settings to reproduce this issue see the 3 following printscreens:
    • Hide

      Insert the following code to the dependency section in the pom.xml:

      <dependency>
   <groupId>jakarta.jws</groupId>
   <artifactId>jakarta.jws-api</artifactId>
   <version>1.1.1</version>
</dependency>
      Show
      Insert the following code to the dependency section in the pom.xml: <dependency> <groupId>jakarta.jws</groupId> <artifactId>jakarta.jws-api</artifactId> <version>1.1.1</version> </dependency>

      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)

      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

      Tested solution - insert the following dependency into the pom.xml and all the problems in the Problems view disappear

      <dependency>
   <groupId>jakarta.jws</groupId>
   <artifactId>jakarta.jws-api</artifactId>
   <version>1.1.1</version>
</dependency>

      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

      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

        1. dynamic_web_project_after_converting_to_maven.png
          dynamic_web_project_after_converting_to_maven.png
          341 kB
        2. new_server_settings.png
          new_server_settings.png
          242 kB
        3. project_facets_when_creating_the_project.png
          project_facets_when_creating_the_project.png
          293 kB
        4. RHCRS_preferences.png
          RHCRS_preferences.png
          277 kB

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

            Zbyněk Červinka (Inactive) added a comment - - edited

            jkopriva@redhat.com 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):

            By the way, jkopriva@redhat.com, you metioned, that you get more error including Missing artifact jakarta.jws:jakarta.jws-api:jar:2.1.0. 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.

            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:

            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

            Red Hat CodeReady Studio (todays devstudio, newest version):

            Version: 12.14.0.AM1
            Build id: AM1-v20191122-0713-B5330
            Build date: 20191122-0713

            Zbyněk Červinka (Inactive) added a comment - - edited jkopriva@redhat.com 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): By the way, jkopriva@redhat.com , you metioned, that you get more error including Missing artifact jakarta.jws:jakarta.jws-api:jar:2.1.0 . 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. 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: 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 Red Hat CodeReady Studio (todays devstudio, newest version): Version: 12.14.0.AM1 Build id: AM1-v20191122-0713-B5330 Build date: 20191122-0713

            Josef Kopriva added a comment - - edited

            zcervink I was able to reproduce it and I get more missing artifacts:

            Missing artifact jakarta.jws:jakarta.jws-api:jar:2.1.0
Missing artifact org.apache.taglibs:taglibs-standard-compat:jar:1.2.6-RC1
Missing artifact org.apache.taglibs:taglibs-standard-impl:jar:1.2.6-RC1		
Missing artifact org.apache.taglibs:taglibs-standard-spec:jar:1.2.6-RC1

            I have not added your repos, it should be working with settings.xml from testing machines.
            It seems to me, that there is missing repo.

            Josef Kopriva added a comment - - edited zcervink I was able to reproduce it and I get more missing artifacts: Missing artifact jakarta.jws:jakarta.jws-api:jar:2.1.0 Missing artifact org.apache.taglibs:taglibs-standard-compat:jar:1.2.6-RC1 Missing artifact org.apache.taglibs:taglibs-standard-impl:jar:1.2.6-RC1 Missing artifact org.apache.taglibs:taglibs-standard-spec:jar:1.2.6-RC1 I have not added your repos, it should be working with settings.xml from testing machines. It seems to me, that there is missing repo.

              jmaury@redhat.com Jeff MAURY
              zcervink Zbyněk Červinka (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: