[JBoss JIRA] (JBIDE-16286) CDI builder (not import, workspace rebuild) is very slow in wildfly
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16286?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16286:
-------------------------------------
Attachment: full-bundle-listing.txt
> 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
> 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: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-16286) CDI builder (not import, workspace rebuild) is very slow in wildfly
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16286?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-16286 at 12/18/13 4:42 PM:
--------------------------------------------------------------------
In my initial Eclipse, the build is still very slow. It's configuration is:
* Kepler Service Release 1, Build id: 20130919-0819
* m2e: org.eclipse.m2e.core_1.5.0.20131218-1213
* cdi: org.jboss.tools.cdi.core_1.6.0.Alpha1-v20131214-0017-B524
Even after switching to new workspace this Eclipse is very slow in building.
I attached it's full plugin-listing
was (Author: adietish):
In my initial Eclipse, the build is still very slow. It's configuration is:
* Kepler Service Release 1, Build id: 20130919-0819
* m2e: org.eclipse.m2e.core_1.5.0.20131218-1213
* cdi: org.jboss.tools.cdi.core_1.6.0.Alpha1-v20131214-0017-B524
> 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
> Labels: performance
> Fix For: 4.1.2.Final, 4.2.0.Alpha2
>
> Attachments: cdi-builder.ogv, cleanBuild.png, 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: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-16286) CDI builder (not import, workspace rebuild) is very slow in wildfly
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16286?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-16286:
------------------------------------------
In my initial Eclipse, the build is still very slow. It's configuration is:
* Kepler Service Release 1, Build id: 20130919-0819
* m2e: org.eclipse.m2e.core_1.5.0.20131218-1213
* cdi: org.jboss.tools.cdi.core_1.6.0.Alpha1-v20131214-0017-B524
> 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
> Labels: performance
> Fix For: 4.1.2.Final, 4.2.0.Alpha2
>
> Attachments: cdi-builder.ogv, cleanBuild.png, 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: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-16286) CDI builder (not import, workspace rebuild) is very slow in wildfly
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16286?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-16286:
------------------------------------------
I switched back to the older openjdk 1.7u9 and build is still equally fast. I suggest we close this as CANNOT_REPRODUCE
> 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
> Labels: performance
> Fix For: 4.1.2.Final, 4.2.0.Alpha2
>
> Attachments: cdi-builder.ogv, cleanBuild.png, 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: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-16286) CDI builder (not import, workspace rebuild) is very slow in wildfly
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16286?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-16286:
------------------------------------------
so here are my build times:
* Eclipse: Kepler Service Release 1, Build id: 20130919-0819
* sun jdk 1.7u45
* m2e: org.eclipse.m2e.core_1.5.0.20131218-1213
* cdi: org.jboss.tools.cdi.core_1.6.0.Alpha1-v20131214-0017-B524
* undertow and wildfly both present in my workspace.
* Change <version.io.undertow> (in wildfly-parent/pom.xml) from 1.0.0.Beta26 to 1.0.0.Beta29:
* only m2e, without CDI:
** start:21:22:46 CET
** stop 21:27:52 CET
* m2e + CDI:
** start: 21:39:48
** stop: 21:46:13
weird, looks like I cannot reproduce this in a new and fresh Eclipse with sun-jdk 1.7u45 where I only have added m2e and cdi.
> 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
> Labels: performance
> Fix For: 4.1.2.Final, 4.2.0.Alpha2
>
> Attachments: cdi-builder.ogv, cleanBuild.png, 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: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-16280) VPE/XulRunner crashes workbench
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16280?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-16280:
-------------------------------
Attachment: install-locally-built-vpe-from-4-sites.png
1. Build JST locally so that VPE can see it
2. Build VPE using https://github.com/jbosstools/jbosstools-vpe/pull/200 which removes all deps on xulrunner for linux.
3. Add multiple sites to Eclipse's list of avail sites.
!install-locally-built-vpe-from-4-sites.png!
4. Install from local VPE site
Result is that I was able to install this locally built feature w/o crashing Eclipse:
{code}
org.jboss.tools.vpe.feature_3.5.100.Alpha1-v20131218-1700
{code}
and these xulrunner plugins were installed (no linux fragments):
{code}
org.jboss.tools.vpe.xulrunner_3.5.100.Alpha1-v20131218-1700.jar
org.jboss.tools.xulrunner.initializer_3.5.100.Alpha1-v20131218-1700.jar
{code}
> VPE/XulRunner crashes workbench
> -------------------------------
>
> Key: JBIDE-16280
> URL: https://issues.jboss.org/browse/JBIDE-16280
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: xulrunner
> Affects Versions: 4.2.0.Alpha1
> Reporter: Mickael Istria
> Priority: Critical
> Fix For: 4.2.0.Alpha2
>
> Attachments: hs_err_pid20688.log, install-locally-built-vpe-from-4-sites.png
>
>
> After an install of JBDS 8.0.0.Alpha1 from installer (built locally with fixes from JBDS-2861), the application crashes a few seconds after startup.
> JVM creates me a thread dump, that you can find attached. Here is the header:
> {code}
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x00007fdea49f3255, pid=18578, tid=140596949411584
> #
> # JRE version: 7.0_25-b30
> # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops)
> # Problematic frame:
> # C [libxul.so+0xc81255] JSD_DebuggerOnForUser+0x978a2
> #
> {code}
> I'm running on Ubuntu 12.04.
--
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, 3 months
[JBoss JIRA] (JBIDE-13438) jboss-packaging-maven-plugin jboss-esb + m2e
by Manosh C (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13438?page=com.atlassian.jira.plugi... ]
Manosh C commented on JBIDE-13438:
----------------------------------
Sorry forgot to mention the Source and test data attachment names
Source - jboss-tools-m2e-esb-sar-sources.zip
test data - test-m2e-esb-sar.zip
> jboss-packaging-maven-plugin jboss-esb + m2e
> --------------------------------------------
>
> Key: JBIDE-13438
> URL: https://issues.jboss.org/browse/JBIDE-13438
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: esb, integration-platform, maven
> Reporter: Manosh C
> Assignee: Brian Fitzpatrick
> Fix For: 4.2.x
>
> Attachments: jboss-tools-m2e-esb-sar-sources.zip, test-m2e-esb-sar.zip, testparent.zip
>
>
> Hi,
>
> Does jboss-packaging-maven-plugin m2e connector work for jboss-esb? When I import a maven jboss-esb project into eclipse (m2e installed), it does not covert it into an Eclipse JBoss ESB (facet is not enabled and dependecies are not set) project. I tried almost all versions of eclipse, m2e, jboss tools and jboss soa tools, to make it work, but no use. This is my work around for now
>
> 1. Turn on facet nature and enable JBOSS ESB nature.
> 2. Then it get recognized as a deployable artifact on JBoss server.
> 3. Manually add all dependencies in "Deployment and Assembly section".
>
> What I was expecting was all steps should have been done by m2e jboss esb (jboss-packaging-maven-plugin) connector. I could not find a relevant post or article related to it. Does this feature ever supported?
>
> Thank you in advance.
> Manosh
--
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, 3 months
[JBoss JIRA] (JBIDE-13438) jboss-packaging-maven-plugin jboss-esb + m2e
by Manosh C (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13438?page=com.atlassian.jira.plugi... ]
Manosh C commented on JBIDE-13438:
----------------------------------
I implemented the m2e connector for JBoss ESB. This is my first JBoss tools eclipse plugin, it may not be perfect, please give it a shot and let me know.
Here are the changes
org.jboss.tools.esb.project.core -
Patched only one class file, org.jboss.tools.esb.project.core\src\org\jboss\tools\esb\core\facet\JBossESBFacetInstallationDelegate.java, for not to throw an exception if esb related folders exist in the project structure (an utility method is taken from JBossSARFacetInstallationDelegate). I did not find an easy way to package it up, so I copied the whole plugin, patched it and created a feature patch to test on my local.
org.jboss.tools.esb.feature.patch - JBoss ESB tools feature patch (Patch is for the feature org.jboss.tools.esb.feature and version 1.5.302.Final-v20131205-1828-B1209)
org.jboss.tools.maven.jbosspackaging -
Refactored into 2 plugins, one is core(org.jboss.tools.maven.jbosspackaging is nothing but the core plugin) and another one is SAR (see below). Core is used in ESB plugin as well.
MavenSarConstants has been renamed to MavenJBossArchivesConstants to avoid confusion and has been used it in all jboss packaging plugins.
Reusable things in SarProjectConfigurator have been moved to AbstractJBossArchiveProjectConfigurator, so that AbstractJBossArchiveProjectConfigurator be used for ESB plugin as well.
SarLifeCycleMapping has been moved to SAR plugin
SarArchiverConfigurator has been moved to SAR plugin
SarProjectConfigurator (extends AbstractJBossArchiveProjectConfigurator) has also been moved to SAR plugin
org.jboss.tools.maven.jbosspackaging.feature.patch - Patch for core jboss packaging plugin (Patching the feature org.jboss.tools.maven.jbosspackaging.feature and version 1.5.4.Final-v20131204-2329-B126).
org.jboss.tools.maven.jbosspackaging.sar - M2e Connector for SAR
org.jboss.tools.maven.jbosspackaging.sar.feature - M2e Connector feature for SAR
org.jboss.tools.maven.jbosspackaging.esb - M2e Connector for ESB
org.jboss.tools.maven.jbosspackaging.esb.feature - M2e Connector feature for ESB
Note1: Patches only work with a specific version of the existing installed feature. If it needs to be tested with a different version, patch version and plugins included in the patch version have to be changed.
Note2: I have included pom.xml in all projects, unfortunately I could not find a maven repository that contains jboss esb plugins. I could not test tycho build process.
Can someone from JBoss tools team, please review the plugins. If changes look reasonable, can you please merge them back to jboss tools and integration stack.
Attaching the sources and test projects.
Please let me know if you need any further information.
> jboss-packaging-maven-plugin jboss-esb + m2e
> --------------------------------------------
>
> Key: JBIDE-13438
> URL: https://issues.jboss.org/browse/JBIDE-13438
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: esb, integration-platform, maven
> Reporter: Manosh C
> Assignee: Brian Fitzpatrick
> Fix For: 4.2.x
>
> Attachments: jboss-tools-m2e-esb-sar-sources.zip, test-m2e-esb-sar.zip, testparent.zip
>
>
> Hi,
>
> Does jboss-packaging-maven-plugin m2e connector work for jboss-esb? When I import a maven jboss-esb project into eclipse (m2e installed), it does not covert it into an Eclipse JBoss ESB (facet is not enabled and dependecies are not set) project. I tried almost all versions of eclipse, m2e, jboss tools and jboss soa tools, to make it work, but no use. This is my work around for now
>
> 1. Turn on facet nature and enable JBOSS ESB nature.
> 2. Then it get recognized as a deployable artifact on JBoss server.
> 3. Manually add all dependencies in "Deployment and Assembly section".
>
> What I was expecting was all steps should have been done by m2e jboss esb (jboss-packaging-maven-plugin) connector. I could not find a relevant post or article related to it. Does this feature ever supported?
>
> Thank you in advance.
> Manosh
--
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, 3 months