[jbosstools-issues] [JBoss JIRA] Issue Comment Edited: (JBIDE-9420) JBoss Tools creates unnecessary Linked Resources
[
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.
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
Affects Versions: 3.3.0.M2
Reporter: Fred Bricon
Assignee: Alexey Kazakov
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 projects to reproduce the issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira