[forge-issues] [JBoss JIRA] (FORGE-877) Addon sub-module is not imported into eclipse workspace

[ https://issues.jboss.org/browse/FORGE-877?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on FORGE-877: --------------------------------------- Transcript from a chat with [~maxandersen]: {quote} <maxandersen> gastaldi: btw. just saw your chat with fbricon about folders in workspaces…..just never import/create projects *inside* your workspace. its a bad practice in almost any scenario. gastaldi> maxandersen, cool, that would solve this importing problem <gastaldi> which folder do you recommend besides the workspace folder ? <gastaldi> the user dir location ? <maxandersen> gastaldi: what is the importing problem actually ? i couldn't figure out what you were bumping into ? is it a committer of forge problem or a user of forge problem ? <maxandersen> gastaldi: where the user has his projects. <gastaldi> there is a forge addon that creates a multi-project structure <maxandersen> gastaldi: there unfortunately aren't any preference for it in eclipse -the closest is egit setting forwhere git projects will be defalt cloned to since egit also doees not like living "inside" workspace. <maxandersen> gastaldi: okey ? <gastaldi> I'm fine with that <maxandersen> that shouldn't be done inside a workspace anyway IMO <maxandersen> (if the multi project follows the eclipse anti—pattern of nested layout ;) <gastaldi> yes, it is nested <gastaldi> maxandersen, we're following the eclipse pattern of using the workspace as a default location for new projects <gastaldi> If you try to create a new Java project you'll see this behavior <maxandersen> gastaldi: noone uses that … it is not sane. <maxandersen> gastaldi: always annoyed me forge tooling did that - its just wrong for anyhing but toy projects {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira