]
Alexey Kazakov commented on JBIDE-16286:
----------------------------------------
[~snjeza] yes, it seems that you are right. And it looks like a serious bug, doesn't
it? What do you think? Using symbolic links in the workspace path should not cause an
infinite loop for m2e builder. Could you please investigate this bug too?
CDI builder (not import, workspace rebuild) is very slow in wildfly
-------------------------------------------------------------------
Key: JBIDE-16286
URL:
https://issues.jboss.org/browse/JBIDE-16286
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi, maven
Affects Versions: 4.1.1.Final
Reporter: Andre Dietisheim
Assignee: Viacheslav Kabanovich
Priority: Critical
Labels: performance
Fix For: 4.1.2.Final, 4.2.0.Alpha2
Attachments: cdi-builder.ogv, cleanBuild.png, full-bundle-listing.txt,
maven-preferences-hide-children.png, thread-dump-7_05.txt, thread-dump-7_19.txt,
updatingPom.png, VisualVM 1.3.2 _083.png
When working in a wildfly workspace with all wildfly projects imported and CDI builder
enabled, workspace rebuilds (that you trigger by changing poms and then do maven update
project) are a lot slower than without it. Re-building the whole workspace can easily take
up to 20 minutes for me.
Hard to give more general purpose details, I did a quick screencast to give an impression
how slow things are for me.
[^cdi-builder.ogv]
--
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: