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

Missing dependencies warning doesn't disappear once settings.xml is fixed

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 4.2.0.Alpha2
    • 4.1.1.Final
    • central
    • None
    • Hide

      1. Have JBDS started with an EAP server added (6.1.1 or 6.2.0)
      2. Click the Java EE Web project archetype
      3. In the dialog, you will be shown a missing dependency warning
      4. Click the "repository" link to see suggestion for your settings.xml and accept the changes
      5. After fixing your settings.xml, the warning will still be displayed back in the wizard

      Show
      1. Have JBDS started with an EAP server added (6.1.1 or 6.2.0) 2. Click the Java EE Web project archetype 3. In the dialog, you will be shown a missing dependency warning 4. Click the "repository" link to see suggestion for your settings.xml and accept the changes 5. After fixing your settings.xml, the warning will still be displayed back in the wizard

      Prerequisite :

      • don't reference redhat repositories in your settings.xml
      • have an EAP runtime handy

      When creating the Java EE Web Project from Central, a warning show up about missing dependencies and a link to add the required repository
      Once the repository is added to your settings.xml, the warning should disappear from the wizard. It doesn't. If you close the wizard and reopen it, the warning won't be displayed.

      The problem is caused by the warning composite not being refreshed in the UI thread : https://github.com/jbosstools/jbosstools-central/blob/284a6e5762fd1b3d8000de14b0ca2895335549bd/maven/plugins/org.jboss.tools.maven.project.examples/src/org/jboss/tools/maven/project/examples/wizard/NewProjectExamplesStacksRequirementsPage.java#L614

            fbricon@redhat.com Fred Bricon
            exd-mmalina Martin Malina
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: