Community
Participate
Working Groups
Currently, the deployment assembly page does not show entries from the component file if they are filtered out by a plugin using the extension point org.eclipse.wst.common.modulecore.ui.resourceMappingFilter. For example, the .settings is hidden by org.eclipse.wst.common.modulecore.ui. The deployment assembly page should not hide these entries. It should show them by default, or at least provide an option to display these hidden entries. One scenario that shows why the deployment assembly page should not behave this way is the following: 1. An source folder is added automatically to a project after enabling some function on it (like in the case of annotation processing). This folder is added to the classpath and to the component file 2. The name of the source folder matches a pattern specified by a plugin using the resourceMappingFilter extension point, so this folder is not shown in the deployment assembly page 3. The source folder is somehow deleted, but the component file is not updated, so the entry remains in the component file. Now there is no way to remove the entry from the component file other than directly editing the file. I propose either: a) Show all entries by default, do not hide any mapping, or b) Provide a new UI option (something like a "Show hidden entries" checkbox in the deployment assembly page, or c) Provide a new product preference to enable/disable hiding entries
