[jbosstools-issues] [JBoss JIRA] (JBIDE-15398) CDI Builder is sloooow

[Fred Bricon (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-15398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802175#comment-12802175 ] 

Fred Bricon commented on JBIDE-15398:
-------------------------------------

The Maven Import wizard in m2e <=1.4 has a memory leak that retains ~350MB of memory during and after importing the WildFly codebase. This leak is fixed in m2e 1.5.0 (snapshots at http://nexus.tesla.io:8081/nexus/content/sites/m2e.extras/m2e/1.5.0/N/LATEST/). This is the version I used to report this bug.
I'm currently refactoring the m2e import process to make it much faster. 
                
> CDI Builder is sloooow
> ----------------------
>
>                 Key: JBIDE-15398
>                 URL: https://issues.jboss.org/browse/JBIDE-15398
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cdi
>    Affects Versions: 4.1.0.Final
>         Environment: Thinkpad T510, Windows 7-64, default JBDS 7.0.0.GA settings, jdk1.7.0_25
>            Reporter: Fred Bricon
>            Assignee: Viacheslav Kabanovich
>            Priority: Critical
>             Fix For: 4.2.0.Alpha1
>
>         Attachments: cdi-build-1.txt, cdi-build-2.txt, cdi-build-3.txt, MemoryUsedOnWildflyBuild.png
>
>
> After cloning https://github.com/wildfly/wildfly, if you import all 130 projects as Maven projects, the CDI nature is automatically added via an m2e configurator.
> 52 minutes after the import, the workspace is currently building at 81% and counting. Random jstack calls show most of the time is spent in the CDI Builder, as shown on the progress bar.
> If I import the same projects in Luna (haven't tried on an clean KeplerEE distro yet) without CDI support (and admittedly the builk of JBT), import+build complete in ~12/13 min

--
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