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

Java EE Web Project Wizard does not set target runtime when user selected one

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • 4.1.0.Alpha1
    • 4.0.0.Final
    • central
    • None
    • Hide

      0. Start JBDS.
      1. Create a EAP 6 server instance.
      2. Start the Java EE Web Project wizard.
      3. Select the Target Runtime as jboss-eap-6.0 Runtime and click Next.
      5. Keep default project name and package and click Finish.
      7. Click cancel for Quick Fix window.

      This project generates several warnings. One warning in particular is (viewed in Problems tab):
      "Build path specifies execution environment JavaSE-1.6. There are no JREs installed in the workspace that are strictly compatible with this environment."

      I think this occurs because the wizard is not actually setting the target runtime property of the project. (See 'Workaround description'.)

      Show
      0. Start JBDS. 1. Create a EAP 6 server instance. 2. Start the Java EE Web Project wizard. 3. Select the Target Runtime as jboss-eap-6.0 Runtime and click Next. 5. Keep default project name and package and click Finish. 7. Click cancel for Quick Fix window. This project generates several warnings. One warning in particular is (viewed in Problems tab): "Build path specifies execution environment JavaSE-1.6. There are no JREs installed in the workspace that are strictly compatible with this environment." I think this occurs because the wizard is not actually setting the target runtime property of the project. (See 'Workaround description'.)
    • Hide

      8. Right-click on the project name in Project Explorer view and click properties.
      9. Click Target Runtimes. The jboss-eap-6.0. Runtime checkbox is not selected.
      10. Select the jboss-eap-6.0 Runtime check box.
      11. Press OK to close the properties window.

      The JavaSE-1.6 warning is resolved.

      [Setting the target runtime manually once the project was created automatically changed the Java Libraries hence resolving the JavaSE-1.6 warning. But perhaps this wasn't necessarily the best way to correct the issue.]

      Show
      8. Right-click on the project name in Project Explorer view and click properties. 9. Click Target Runtimes. The jboss-eap-6.0. Runtime checkbox is not selected. 10. Select the jboss-eap-6.0 Runtime check box. 11. Press OK to close the properties window. The JavaSE-1.6 warning is resolved. [Setting the target runtime manually once the project was created automatically changed the Java Libraries hence resolving the JavaSE-1.6 warning. But perhaps this wasn't necessarily the best way to correct the issue.]

      I chose jboss-eap-6.0 Runtime as the target runtime in the Java EE Web Project wizard, but this was then not set in the project's properties when the project was created. I had to go and set it manually.

      Original (perhaps confusing) description:
      [In the Java EE Web Project wizard I chose jboss-eap-6.0 Runtime as the target runtime. When the wizard completed there were several warnings. One in particular:
      "Build path specifies execution environment JavaSE-1.6. There are no JREs installed in the workspace that are strictly compatible with this environment."

      This warning was resolved by setting the target runtime to jboss-eap-6.0 again in the project's Properties > Targeted Runtimes.

      So although I had chosen jboss-eap-6.0 Runtime as the target runtime in the wizard, this was not set in the project's properties when the project was created. As a user, this seems like counter-intuitive behavior. I would have thought it would have been set.]

        1. TargetRuntime1.png
          TargetRuntime1.png
          67 kB
        2. TargetRuntime2.png
          TargetRuntime2.png
          82 kB

              snjeza_jira Snjezana Peco (Inactive)
              mmurray1@redhat.com Michelle Murray (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: