[
https://issues.jboss.org/browse/JBIDE-16286?page=com.atlassian.jira.plugi...
]
Alexey Kazakov edited comment on JBIDE-16286 at 12/13/13 8:28 PM:
------------------------------------------------------------------
I can't reproduce the issue on my laptop :(
I used JBT plugins from master branch + 4.40.x target platform (without
org.eclipse.birt.jetty.overlay plug-in which prevents Eclipse from starting becuase of
OutOfMemory).
Ubuntu amd64. OpenJDK 1.7.0_45-b18.
Here is my vm arguments: -Xmx2048M -Xms256M -XX:PermSize=512M -XX:MaxPermSize=1024M
What I did:
1. git clone git@github.com:wildfly/wildfly.git
2. Imported the wildfly root folder as an existing maven project. So I got 148 mavenized
projects in my workspace
3. Changed some depenedncies in /wildfly-parent/pom.xml
4. Save the changed pom.xml
5. The build took 3 minutes.
!updatingPom.png|thumbnail!
was (Author: akazakov):
I can't reproduce the issue on my laptop :(
I used JBT plugins from master branch + 4.40.x target platform.
Ubuntu amd64. OpenJDK 1.7.0_45-b18.
Here is my vm arguments: -Xmx2048M -Xms256M -XX:PermSize=512M -XX:MaxPermSize=1024M
What I did:
1. git clone git@github.com:wildfly/wildfly.git
2. Imported the wildfly root folder as an existing maven project. So I got 148 mavenized
projects in my workspace
3. Changed some depenedncies in /wildfly-parent/pom.xml
4. Save the changed pom.xml
5. The build took 3 minutes.
!updatingPom.png|thumbnail!
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
Affects Versions: 4.1.1.Final
Reporter: Andre Dietisheim
Assignee: Viacheslav Kabanovich
Priority: Critical
Fix For: 4.1.2.Final, 4.2.0.Alpha2
Attachments: cdi-builder.ogv, cleanBuild.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:
http://www.atlassian.com/software/jira