[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-9420) JBoss Tools creates unnecessary Linked Resources
[
https://issues.jboss.org/browse/JBIDE-9420?page=com.atlassian.jira.plugin...
]
Viacheslav Kabanovich commented on JBIDE-9420:
----------------------------------------------
This issue became that severe after improvement in 3.3.x that allowed to build in full kb
model for projects depending on Java non kb projects. I added paths of Java sources from
these projects to the set of scanned paths, and model by default created links to folders
outside project. This fix just prevents creating links whenever folder can be found in
Eclipse workspace.
Now that we are about to fix JBIDE-9120 - by prompting user by markers to add Knowledge
Base capabilities to projects that may be needed by kb builder of that project or of
dependent projects, I think we should remove the non-Eclipse approach of letting builder
of one project go into folders of other projects. Version 3.2.x does not have that.
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: Viacheslav Kabanovich
Fix For: 3.3.0.M3
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira