[jbosstools-issues] [JBoss JIRA] (JBIDE-16379) Using symbolic links in the workspace path causes an infinite loop for m2e builder

[ https://issues.jboss.org/browse/JBIDE-16379?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-16379: ---------------------------------- Comment: was deleted (was: I have tested importing the wildfly distribution using Eclipse 4.4.1/JBT 4.2.0.CR1 Test case 1: When excluding all the m2e/JBT Maven configurators, suspending all the WTP validators and disabling the "Auto Share EGit" projects (unchecking all the three checkboxes in Window>Preferences>Team>Git>Projects), importing the wildfly distribution takes 5-6 minutes. Since that operation creates and compiles 50+ Eclipse projects, I think, it can't be significantly improved. Cleaning/rebuilding all the projects lasts about 3 minutes. Test case 2: When including the m2e/JBT maven configurators and the default WTP validators, disabling the "Auto Share EGit" projects, importing the wildfly distribution lasts less than 15 minutes. Cleaning/rebuilding all the projects takes about 6-8 minutes. Test case 3: If all the validators and the m2e/JBT configurators are included and the "Auto Share EGit" projects enabled, importing the wildfly distribution takes less than 20 minutes. EGit doesn't significantly affect cleaning/rebuilding projects. In these cases, Eclipse requires less than 1GB Java heap space. As I can see, there is noticeable improvements in Eclipse 4.4.1/JBT 4.2.0 I encounter issues in the test case 3 when there are more .git directories in the hierarchy and there is .git in a directory with a lot of entries. On Linux, such a situation can happen when using symbolic links. If EGit finds the .git directory, it will scan the complete hierarchy which can slow down Eclipse/JBDS/JBT or even lock it. In my opinion, we should advice users to disable the "Auto Share EGit" projects and maybe even, to disable this property in JBDS using plugin_customization.ini.) -- This message was sent by Atlassian JIRA (v6.3.1#6329)