[
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.
JBoss Tools creates unnecessary Linked Resources
------------------------------------------------
Key: JBIDE-9420
URL:
https://issues.jboss.org/browse/JBIDE-9420
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 3.3.0.M2
Reporter: Fred Bricon
Assignee: Viacheslav Kabanovich
Fix For: 3.3.0.Beta1
Attachments: extra-linked-resources.jpg, extra-linked-resources.zip
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 non-maven projects to reproduce the issue.
--
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