[ https://jira.jboss.org/jira/browse/JBIDE-5006?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-5006: -------------------------------------------- Would it be sufficient to have support for being able to include all content of a specific eclipse workspace folder into a project or do you need full "filter control" ? About Drools - why not just put the .drl files directly in the project ? The drools tooling should work just as fine in there. If it doesn't then we need to fix that. -- 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-5006?page=com.atlassian.jira.plu... ] Jeff DeLong commented on JBIDE-5006: ------------------------------------ I think we need "full filter control". Often the ESB archive just needs a single file from another project, not the entire workspace folder folder. For example a Drools project might have several JUnit Tests in the Drools project folder along with the DRL file (although one would be in src/main/java and the other in src/main/rules. While it is true that you could use the "Convert to Drools Project" context menu item to add Drools jars to an ESB project, and this will allow you to open the DRL file inside that project and edit it, there are good reasons why a customer might not want use the ESB project to create and maintain their DRL file. First off the developer of the rules is not necessarily the same developer as that creating the ESB service (different skill sets and / or responsibilities); so from a source code control perspective it would be easier for them to work on different projects. Second, you would want the Drools JUnit tests in the project, but now you would worry about these winding up in the ESB archive as well. So what you wind up doing is having two separate projects, and then copying the DRL file between the two. -- 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-5006?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-5006: -------------------------------------------- Rob - this doesnt compute for me ;) You added "pick up jars from classpath info", why can't we add a "pick up this filter set from workspace" extension too ? Len - I don't understand your comment about "Convert to Drools Project" ? Does Drools now require having the jars on the project to open the file ?! Note, this usecase about having files from different locations aren't different than any other project so we should find a way to fix this (WTP won't until some time next year) -- 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-5006?page=com.atlassian.jira.plu... ] Rob Stryker resolved JBIDE-5006. -------------------------------- Resolution: Done A "fileset virtual component" was added as part of JBIDE-4955. However it's not as pretty as ti could be. I'll close this and open new jiras for the perfections that must go into that. -- 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