[ https://jira.jboss.org/jira/browse/JBIDE-4955?page=com.atlassian.jira.plu... ] Rob Stryker commented on JBIDE-4955: ------------------------------------ ugh i'm not sure how feasible this is at all. On the WTP side there's simply no API for exclusions, and on our code side it's possible but would be a very very messy change. I'd really need to think of a way to do it without breaking everything -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-4955?page=com.atlassian.jira.plu... ] Rob Stryker updated JBIDE-4955: ------------------------------- Fix Version/s: LATER no good way to do this for now -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-4955?page=com.atlassian.jira.plu... ] Adrian Mitev commented on JBIDE-4955: ------------------------------------- I would like to use this on a Seam web project -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-4955?page=com.atlassian.jira.plu... ] Rob Stryker resolved JBIDE-4955. -------------------------------- Resolution: Done Feasible? Yes. Make any sense at all? No. Definitely not. The modules expose their resources. If we wanted the server to handle it differently, we'd need to configure each server with additional filesets for each module. As an example, imagine we have ProjectA and server1-5. In this example, you'd first configure ProjectA in the Module Assembly page. Then you'd add ProjectA to one or more servers. Then you'd have to open a second page dedicated to each server you've deployed to and outline how THAT server should override / filter the resources exposed by ProjectA / ModuleA. (If you had more than one project you wanted deployed to these servers you'd need to do the same for each project on each server) In addition, this wouldn't be placed on the module assembly page (because the module assembly page does not reference servers at all)... It would need to be on a server-dedicated page, and would confuse the user. Where should they configure how their project is assembled? On the module assembly page? Or in the property page for each server? They'd have to do it in both. It would be very confusing for the user, make the code horrendously ugly, and be difficult to get to work. Since the goal is that WTP 3.2 has support for this fileset type (already coded), anything I could code now would be quick and ad-hoc and not up to the standards that we'd desire. And then it would be duplicated by the more fully integrated fileset component in future versions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira