[ https://jira.jboss.org/browse/JBIDE-6402?page=com.atlassian.jira.plugin.s... ] Nick Boldt updated JBIDE-6402: ------------------------------ Description: 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 was: 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 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6402?page=com.atlassian.jira.plugin.s... ] Nick Boldt commented on JBIDE-6402: ----------------------------------- The issue is that if we *do* depend on either of those two features, we now need to depend on another. If we only depend on plugins (which is frankly better) then you can close this jira as WORKSFORME or INVALID. My point was to raise the issue and have someone who knows the jsf/jst code ensure that we're all good here even after this change. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira