[JBoss JIRA] (JBIDE-16286) CDI builder (not import, workspace rebuild) is very slow in wildfly
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16286?page=com.atlassian.jira.plugi... ]
Alexey Kazakov edited comment on JBIDE-16286 at 12/13/13 7:52 PM:
------------------------------------------------------------------
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!
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!
> 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, 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
12 years, 4 months
[JBoss JIRA] (JBIDE-16286) CDI builder (not import, workspace rebuild) is very slow in wildfly
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16286?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-16286:
-------------------------------------
Alexey: how many projects updated in the updatePom screenshot?
The whole update project scenario, although concerning given the amount of memory consumed, is not necessarily the most pressing issue.
The whole sluggishness is felt during incremental build, as reported by Dr Dré.
> 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, 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
12 years, 4 months
[JBoss JIRA] (JBIDE-16286) CDI builder (not import, workspace rebuild) is very slow in wildfly
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16286?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-16286:
----------------------------------------
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!
> 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, 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
12 years, 4 months
[JBoss JIRA] (JBIDE-16286) CDI builder (not import, workspace rebuild) is very slow in wildfly
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16286?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-16286:
-----------------------------------
Attachment: updatingPom.png
> 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, 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
12 years, 4 months
[JBoss JIRA] (JBIDE-16301) No combo to select Target Runtime in examples dilaog
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16301?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-16301:
---------------------------------------
{quote}The reason why a runtime combo is available for archetype based wizard is because the archetype-generated project depends on that runtime in the sense the dependencies (or the archetype version itself) can change depending on whether you run on AS or EAP for instance. The selected runtime is not added to the project afterwards{quote}
So it is literarary a checkbox '[ ] Enterprise' ? I was always thinking about it as "Deploy to...'
{quote}Now we can discuss if adding a runtime combo here makes sense, i.e. we could decide to add it to the gen'd project, but then what about multi-module projects? How should we decide which project(s) to associate it to?{quote}
Why not associate verey project with selected server? Are there other scenarios?
It just confusing have Server as a dependency and then not being able to point out what server to use/deploy to.
> No combo to select Target Runtime in examples dilaog
> ----------------------------------------------------
>
> Key: JBIDE-16301
> URL: https://issues.jboss.org/browse/JBIDE-16301
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.1.1.Final
> Reporter: Denis Golovin
> Fix For: 4.2.x
>
> Attachments: Selection_025.png
>
>
> Target Runtime combo is not visible in Examples dialog
> !Selection_025.png!
--
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
12 years, 4 months
[JBoss JIRA] (JBDS-2862) During install, I should be able to create a new directory to install into
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2862?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-2862:
--------------------------------
Fix Version/s: 7.1.1.GA
8.0.0.Alpha2
> During install, I should be able to create a new directory to install into
> --------------------------------------------------------------------------
>
> Key: JBDS-2862
> URL: https://issues.jboss.org/browse/JBDS-2862
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.1.0.CR1
> Environment: Mac OS X
> Reporter: Jim Tyrrell
> Assignee: Denis Golovin
> Fix For: 7.1.1.GA, 8.0.0.Alpha2
>
> Attachments: Screen shot 2013-12-10 at 12.34.20 PM.png, Screen Shot 2013-12-10 at 3.11.08 PM.png, Select Target Folder_015.png
>
>
> See the attached screen shot, a create new folder button does not seem to exist anywhere to create a new folder/directory to install JBDS.
--
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
12 years, 4 months