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

features must now depend on org.eclipse.jsf.feature as well as org.eclipse.jst.web_core.feature/org.eclipse.jst.web_ui.feature

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • 3.2.0.M1
    • jsf
    • None

      From David Williams on cross-projects-issues-dev@eclipse.org:

      It is far later than it should be, to be making this kind of change, so I am sending this notice to wtp-dev list and cross-project list to make sure it gets proper visibility.

      In WTP, the JEE and the JSF subprojects have regrouped a set of JSF bundles that used to be mingled in with the JEE bundles for packaging purposes, and pulled them out into their own, new JSF feature.

      This was required to allow more flexible packaging options and, more importantly, independent maintenance releases in the future. See bug 302896.
      https://bugs.eclipse.org/bugs/show_bug.cgi?id=302896

      The implication is that anyone that has a feature that prereqs or installs

      org.eclipse.jst.web_core.feature, or
      org.eclipse.jst.web_ui.feature

      will now have to also prereq or install

      org.eclipse.jsf.feature

      to have the same, JSF functionality and bundles pulled in, that is.

      Similar for SDK counterparts; there is now an org.eclipse.jsf_sdk.feature.

      These new features are versioned as "3.2.0" to match the previous feature and highest bundle version.

      Apologies for the late change. Entirely my fault for not realizing the importance of this change earlier.

      I have, naturally, updated the webtools.build file and opened a bugzilla entry to update EPP Java EE package appropriately.
      See bug 314969
      https://bugs.eclipse.org/bugs/show_bug.cgi?id=314969

              alexeykazakov Alexey Kazakov
              nickboldt Nick Boldt
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: