[
https://issues.jboss.org/browse/JBIDE-16379?page=com.atlassian.jira.plugi...
]
Snjezana Peco commented on JBIDE-16379:
---------------------------------------
{quote}
okey, so if symbolic links are not a problem nor freezing/slowing down m2e and the only
thing we are finding is that things get slow if you import projects that are located in a
massive and huge .git repository then things are slower then i'm really not following
what this bug is about ?
{quote}
The issue Andre had was that importing wildfly was very slow. See JBIDE-16286.
It isn't easy to reproduce it. Alexey and I have noticed it happens when using
symbolic links on Linux
(
https://issues.jboss.org/browse/JBIDE-16286?focusedCommentId=12936688&...).
After detailed testing, I have concluded that symbolic links aren't a problem. The
problem is that using symbolic links we create a git repository with a lot of untracked
files.
{quote}
issue about superlarge directories is perfectly fine warning to give.
{quote}
Agree. In my opinion, all that we can do is to warn users if they have extremely bad
performance.
EGit is very slow when importing of a big file structure with .git in
the grand-parent dir
------------------------------------------------------------------------------------------
Key: JBIDE-16379
URL:
https://issues.jboss.org/browse/JBIDE-16379
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: upstream
Affects Versions: 4.2.0.Alpha1
Reporter: Snjezana Peco
Assignee: Snjezana Peco
Fix For: 4.3.x
See JBIDE-16286
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)