[ https://issues.jboss.org/browse/JBIDE-9420?page=com.atlassian.jira.plugin... ] Fred Bricon updated JBIDE-9420: ------------------------------- Summary: JBoss Tools creates unnecessary Linked Resources (was: JBoss Tools create unnecessary Linked Resources) Description: When creating a multi module project with maven (war + jar for instance), if the war project installs the JSF facet, then all the sources of its dependent projects are added as linked resources. It occurs when the KB nature is added. However, I've seen other occurences of the problem, where my eclipse plugins (not dependent on any JavaEE/JSF features) in the workspace also showcase this annoying behavior if JBT is installed. !extra-linked-resources.jpg! I'm attaching 2 projects to reproduce the issue. was: When creating a multi module project with maven (war + jar for instance), if the war project installs the JSF facet, then all the sources of its dependent projects are added as linked resources. It occurs when the KB nature is added. However, I've seen other occurences of the problem, where my eclipse plugins (not dependent on any JavaEE/JSF features) in the workspace also showcase this annoying behavior if JBT is installed. I'm attaching 2 projects to reproduce the issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9420?page=com.atlassian.jira.plugin... ] Fred Bricon edited comment on JBIDE-9420 at 7/28/11 8:07 AM: ------------------------------------------------------------- It becomes higly annoying when each dependent maven projects declares 4 source folders (src/main/java, src/main/resources, src/test/java, src/test/resources). Also, I can not measure the impact of these Linked Resources on the resulting classpath, and that's a bit scary. was (Author: fbricon): It become higly annoying when each dependent maven projects declares 4 source folders (src/main/java, src/main/resources, src/test/java, src/test/resources). Also, I can not measure the impact of these Linked Resources on the resulting classpath, and that's a bit scary. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9420?page=com.atlassian.jira.plugin... ] Alexey Kazakov updated JBIDE-9420: ---------------------------------- Fix Version/s: 3.3.0.M3 Assignee: Viacheslav Kabanovich (was: Alexey Kazakov) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9420?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-9420: -------------------------------------------- reopen for clarification: What caused this and is this also present by any chance in 3.2.x branch? If yes, that needs fixing too. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9420?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-9420: -------------------------------------------- Okey - but why would we *ever* automatically create linked resources "out of the blue" ? sounds like you are saying that our code would still do that if someone added more paths to our model ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9420?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen resolved JBIDE-9420. ---------------------------------------- Resolution: Done okey - resolving this as fixed but it sounds like we are mixing different concerns here. Explicit Import and scanning for resources implicitly are very different things and requires different approaches. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9420?page=com.atlassian.jira.plugin... ] Fred Bricon updated JBIDE-9420: ------------------------------- Fix Version/s: 3.3.0.Beta1 (was: 3.3.0.M3) Updating fix Version to 3.3.0.Beta1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9420?page=com.atlassian.jira.plugin... ] Viacheslav Kabanovich commented on JBIDE-9420: ---------------------------------------------- In this case, linked resources are external class folders. So, it is easy to reproduce the problem with a simple JSFKickStart project by adding to its class path an external class folder - link will be created. Eclipse does not provide IResource objects for external folders, and to reduce that case to handling 'traditional' IResource objects, I found linking to be the only way. However, after studying ExternalPackageFragmentRoot, now I see that JDT creates a fake IResource link to the folder and we can use it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9420?page=com.atlassian.jira.plugin... ] Alexey Kazakov resolved JBIDE-9420. ----------------------------------- Assignee: Viacheslav Kabanovich (was: Alexey Kazakov) Resolution: Done fixed -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira