In JBDS trunk [1], I've moved ESB refs in ./features/com.jboss.jbds.product.feature/feature.xml and ./site/site.xml to ./features/com.jboss.jbds.product.soa.feature/feature.xml and ./soa-site/site.xml, but other refs persist.

[1] http://svn.jboss.org/repos/devstudio/trunk/product/

—

These references should be removed and dealt with as downstream extensions, etc.

• • [3] ./plugins/com.jboss.jbds.product/themes/jbds/html/internal-page.css **
    506-a#new_seam_project_by_generate_entities:hover img { background-image : url('../graphics/icons/ctool/new_seam_project_small_hov.png'); width : 83px; height : 48px; }

    507-
    508:a#new_jbpm_process_project img

    { background-image : url('../graphics/icons/ctool/new_jbpm_process_project_small.png'); width : 83px; height : 48px; }

    509:a#new_jbpm_process_project:hover img

    { background-image : url('../graphics/icons/ctool/new_jbpm_process_project_small_hov.png'); width : 83px; height : 48px; }

    510-
    511-a#new_jsf_project img

    { background-image : url('../graphics/icons/ctool/new_jsf_project.png'); width : 48px; height : 48px; }

• • [4] ./plugins/com.jboss.jbds.product/themes/jbds/html/overview.css **
    263-a#new_seam_project_by_generate_entities:hover img { background-image : url('../graphics/icons/ctool/new_seam_project_small_hov.png'); width : 83px; height : 48px; }

    264-
    265:a#new_jbpm_process_project img

    { background-image : url('../graphics/icons/ctool/new_jbpm_process_project_small.png'); width : 83px; height : 48px; }

    266:a#new_jbpm_process_project:hover img

    { background-image : url('../graphics/icons/ctool/new_jbpm_process_project_small_hov.png'); width : 83px; height : 48px; }

    267-
    268-a#new_jsf_project img

    { background-image : url('../graphics/icons/ctool/new_jsf_project.png'); width : 48px; height : 48px; }

• • [5] ./plugins/com.jboss.jbds.product/themes/jbds/swt/createnew.properties **
    16-createnew.page-content.seam_project.new_seam_project_by_generate_entities.hover-icon = ../graphics/icons/ctool/new_seam_project_small.png
    17-
    18:createnew.page-content.seam_project.new_jbpm_process_project.link-icon = ../graphics/icons/ctool/new_jbpm_process_project_small.png
    19:#createnew.page-content.seam_project.new_jbpm_process_project.hover-icon = ../graphics/icons/ctool/new_jbpm_process_project_small_hov.png
    20:createnew.page-content.seam_project.new_jbpm_process_project.hover-icon = ../graphics/icons/ctool/new_jbpm_process_project_small.png
    21-
    22-createnew.page-content.new_struts_project.link-icon = ../graphics/icons/ctool/new_struts_project.png

• • [6] ./plugins/com.jboss.jbds.product/plugin.xml **
    254- value="%createnewLinkDescriptionSeam" />
    255- <property
    256: name="createnewLinkjbpm"
    257: value="%createnewLinkjbpm" />
    258- <property
    259: name="createnewLinkDescriptionjbpm"
    260: value="%createnewLinkDescriptionjbpm" />
    261- <property
    262- name="createnewLinkJSF"

• • [7] ./plugins/com.jboss.jbds.product/plugin.properties **
    95-createnewLinkSeam=Create Seam Project
    96-createnewLinkDescriptionSeam=JBoss Developer Studio includes a New Seam Project Wizard that allows you to setup project for full featured web application in Seam. You can use any combination of Java EE frameworks integrated to JBoss Seam.
    97:createnewLinkjbpm=Create jBPM Process Project
    98:createnewLinkDescriptionjbpm=JBoss Developer Studio includes a New jBPM Process Project that allows you to create applications using jBPM Framework
    99-createnewLinkJSF=Create JSF Project
    100-createnewLinkDescriptionJSF=JBoss Developer Studio allows you to create brand new JSF projects. A new JSF project will have all JSF libraries, tag libraries and a JSF configuration file. JBoss Developer Studio comes with a number of predefined project templates. These templates are flexible and easily customizable.

• • [8] ./plugins/com.jboss.jbds.product/plugin_customization.ini **
    62-# the uri to be used to deploy the process. There is a preference for this
    63-# property that initially contains the path for the jBPM standalone runtime
    64:# (i.e. jbpm-console/upload). This value should be changed because in SOA-P
    65-# another path is used (i.e. gpd-deployer/upload see
    66-# https://jira.jboss.org/jira/browse/JBPM-2678)
    67:org.jbpm.gd.jpdl/server\ deployer=/gpd-deployer/upload