[JBoss JIRA] (JBIDE-16308) Cannot start JBT 4.2.0.Alpha1 on Fedora 19
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16308?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-16308:
----------------------------------------
This could be fixed in M5. Can you give a try with the most recent Eclipse build: http://download.eclipse.org/eclipse/downloads/drops4/S-4.4M4-201312121600/
> Cannot start JBT 4.2.0.Alpha1 on Fedora 19
> ------------------------------------------
>
> Key: JBIDE-16308
> URL: https://issues.jboss.org/browse/JBIDE-16308
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha1
> Environment: JBT 4.2.Alpha1, L64, Fedora 19, 64-bit, Open JDK 1.7
> Reporter: Jiri Peterka
> Priority: Blocker
> Fix For: 4.2.0.Alpha1
>
>
> Installing JBT on Eclipse -4.4.M4- 4.4.M3 JEE package (linux_64), after JBT installation update site and restart I have:
> {code}
> !ENTRY org.eclipse.osgi 4 0 2013-12-16 15:35:03.535
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> at java.util.ArrayList.iterator(ArrayList.java:814)
> at org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:962)
> at org.apache.felix.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:787)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:252)
> at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:652)
> at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:75)
> at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:454)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:412)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:402)
> at org.eclipse.osgi.container.Module.start(Module.java:406)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1530)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1510)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1481)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1424)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> {code}
> Even if I raise a memory for JVM, Eclipse doesn't start but not error message is written
--
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-16308) Cannot start JBT 4.2.0.Alpha1 on Fedora 19
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16308?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-16308:
-------------------------------
Description:
Installing JBT on Eclipse -4.4.M4- 4.4.M3 JEE package (linux_64), after JBT installation update site and restart I have:
{code}
!ENTRY org.eclipse.osgi 4 0 2013-12-16 15:35:03.535
!MESSAGE FrameworkEvent ERROR
!STACK 0
java.lang.OutOfMemoryError: GC overhead limit exceeded
at java.util.ArrayList.iterator(ArrayList.java:814)
at org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:962)
at org.apache.felix.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:787)
at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:252)
at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:652)
at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:75)
at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:454)
at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:412)
at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:402)
at org.eclipse.osgi.container.Module.start(Module.java:406)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1530)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1510)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1481)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1424)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
{code}
Even if I raise a memory for JVM, Eclipse doesn't start but not error message is written
was:
Installing JBT on Eclipse 4.4.M4 JEE package (linux_64), after JBT installation update site and restart I have:
{code}
!ENTRY org.eclipse.osgi 4 0 2013-12-16 15:35:03.535
!MESSAGE FrameworkEvent ERROR
!STACK 0
java.lang.OutOfMemoryError: GC overhead limit exceeded
at java.util.ArrayList.iterator(ArrayList.java:814)
at org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:962)
at org.apache.felix.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:787)
at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:252)
at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:652)
at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:75)
at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:454)
at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:412)
at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:402)
at org.eclipse.osgi.container.Module.start(Module.java:406)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1530)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1510)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1481)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1424)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
{code}
Even if I raise a memory for JVM, Eclipse doesn't start but not error message is written
> Cannot start JBT 4.2.0.Alpha1 on Fedora 19
> ------------------------------------------
>
> Key: JBIDE-16308
> URL: https://issues.jboss.org/browse/JBIDE-16308
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha1
> Environment: JBT 4.2.Alpha1, L64, Fedora 19, 64-bit, Open JDK 1.7
> Reporter: Jiri Peterka
> Priority: Blocker
> Fix For: 4.2.0.Alpha1
>
>
> Installing JBT on Eclipse -4.4.M4- 4.4.M3 JEE package (linux_64), after JBT installation update site and restart I have:
> {code}
> !ENTRY org.eclipse.osgi 4 0 2013-12-16 15:35:03.535
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> at java.util.ArrayList.iterator(ArrayList.java:814)
> at org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:962)
> at org.apache.felix.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:787)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:252)
> at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:652)
> at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:75)
> at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:454)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:412)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:402)
> at org.eclipse.osgi.container.Module.start(Module.java:406)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1530)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1510)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1481)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1424)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> {code}
> Even if I raise a memory for JVM, Eclipse doesn't start but not error message is written
--
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-14522) Arquillian Cruiser content view should link back to source view
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14522?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-14522:
----------------------------------
Fix Version/s: 4.2.0.Alpha2
(was: 4.1.x)
> Arquillian Cruiser content view should link back to source view
> ---------------------------------------------------------------
>
> Key: JBIDE-14522
> URL: https://issues.jboss.org/browse/JBIDE-14522
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: testing-tools
> Reporter: Aslak Knutsen
> Assignee: Snjezana Peco
> Fix For: 4.2.0.Alpha2
>
>
> {code}
> @RunWith(Arquillian.class)
> class MangerTest {
> @Deployment
> public Archive<?> create() {
> return ShrinkWrap.create(JavaArchive.class).addClass(MyClass.class);
> }
> }
> {code}
> Given this code snippet, the Arquillian Cruiser deployment Archive overview will show a similar structure to:
> {code}
> ManagerTest
> - create
> org
> my
> MyClass.class
> {code}
> The MyClass.class line in the overview should link back to the source view of MyClass.java.
--
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-16308) Cannot start JBT 4.2.0.Alpha1 on Fedora 19
by Jiri Peterka (JIRA)
Jiri Peterka created JBIDE-16308:
------------------------------------
Summary: Cannot start JBT 4.2.0.Alpha1 on Fedora 19
Key: JBIDE-16308
URL: https://issues.jboss.org/browse/JBIDE-16308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.2.0.Alpha1
Environment: JBT 4.2.Alpha1, L64, Fedora 19, 64-bit, Open JDK 1.7
Reporter: Jiri Peterka
Priority: Blocker
Fix For: 4.2.0.Alpha1
Installing JBT on Eclipse 4.4.M4 JEE package (linux_64), after JBT installation update site and restart I have:
{code}
!ENTRY org.eclipse.osgi 4 0 2013-12-16 15:35:03.535
!MESSAGE FrameworkEvent ERROR
!STACK 0
java.lang.OutOfMemoryError: GC overhead limit exceeded
at java.util.ArrayList.iterator(ArrayList.java:814)
at org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:962)
at org.apache.felix.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:787)
at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:252)
at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:652)
at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:75)
at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:454)
at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:412)
at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:402)
at org.eclipse.osgi.container.Module.start(Module.java:406)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1530)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1510)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1481)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1424)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
{code}
Even if I raise a memory for JVM, Eclipse doesn't start but not error message is written
--
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-2745) Support installation of Early Access / Experimental / Incubating plugins
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2745?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2745:
----------------------------------
It's been said many times that Central should not include Beta content. The current JBDS-IS content is post-Beta. It's CR1 [1] (with a CR2 version of its target platform).
[1] https://devstudio.jboss.com/updates/7.0-staging/integration-stack/
So I would be happy to include it in Central if we labelled all the connectors with "Technology Preview" (not "Experimental").
Then in a month when JBDS IS 7.0.0 goes GA, we can roll out an update to the JBDS IS Central Discovery plugin, removing the "Technology Preview" labels in favour of "Supported", and provide updated versions of those connectors.
[~pleacu] [~maxandersen] [~mmusaji] [~rcernich] WDYT? Vote early, vote often!
> Support installation of Early Access / Experimental / Incubating plugins
> ------------------------------------------------------------------------
>
> Key: JBDS-2745
> URL: https://issues.jboss.org/browse/JBDS-2745
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: central, requirements
> Affects Versions: 7.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Burr Sutter
>
> It's been suggested that it would be nice to have Central available to install non-GA content. How might this appear?
> [~burrsutter], [~maxandersen], are we talking about:
> * an additional dialog warning users about untested content? (that might be ignored / blindclicked)
> * an additional tab in Central for this type of content (what label would you use?)
> * relabelling the content's feature descriptions / titles / copyright / license terms to be clear it's unstable content? (might be ignored)
> * some other workflow?
> See also JBDS-2068.
--
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-16195) For JBIDE 4.1.1.Final: Prepare for Final/GA release
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16195?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-16195:
------------------------------------
[~maxandersen] [~fbricon]:
Two questions about the JBDS 7.1 announcement blog [1] ...
a) shouldn't we link to Kepler SR1, instead of Kepler R?
b) should the topic in this channel be updated to point to the JBDS 7.1 blog instead of the 7.0 one?
[1] https://community.jboss.org/en/tools/blog/2013/12/16/jboss-tool-411-and-j...
> For JBIDE 4.1.1.Final: Prepare for Final/GA release
> ---------------------------------------------------
>
> Key: JBIDE-16195
> URL: https://issues.jboss.org/browse/JBIDE-16195
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.1.1.Final
>
>
> For JBIDE 4.1.1.Final: Please perform the following tasks:
> 0. If nothing has changed in your component since JBT 4.1.0.Final or JBDS 7.0.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise, for all other projects:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Final or 7.1.0.GA
> [Unresolved JIRAs with fixVersion = 4.1.1.CR1, 4.1.1.Final, 7.1.0.CR1, 7.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
> 1. In the *{color:blue}4.1.1.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.1.1.Final-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.1.1.Final-SNAPSHOT</version>
> </parent>
> {code}
> 2. In the *{color:orange}4.1.x{color}* branch, update your root pom to use parent pom version *{color:orange}4.1.2.Alpha1-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.1.2.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform versions
> {code}
> mvn clean verify -Dtpc.version=4.30.6.Final
> mvn clean verify -Dtpc.version=4.31.1.Final
> {code}
> 4. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> See also: JBDS-2846
--
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-16195) For JBIDE 4.1.1.Final: Prepare for Final/GA release
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16195?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen resolved JBIDE-16195.
-----------------------------------------
Resolution: Done
all subtasks done. resolving
> For JBIDE 4.1.1.Final: Prepare for Final/GA release
> ---------------------------------------------------
>
> Key: JBIDE-16195
> URL: https://issues.jboss.org/browse/JBIDE-16195
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.1.1.Final
>
>
> For JBIDE 4.1.1.Final: Please perform the following tasks:
> 0. If nothing has changed in your component since JBT 4.1.0.Final or JBDS 7.0.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise, for all other projects:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Final or 7.1.0.GA
> [Unresolved JIRAs with fixVersion = 4.1.1.CR1, 4.1.1.Final, 7.1.0.CR1, 7.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
> 1. In the *{color:blue}4.1.1.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.1.1.Final-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.1.1.Final-SNAPSHOT</version>
> </parent>
> {code}
> 2. In the *{color:orange}4.1.x{color}* branch, update your root pom to use parent pom version *{color:orange}4.1.2.Alpha1-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.1.2.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform versions
> {code}
> mvn clean verify -Dtpc.version=4.30.6.Final
> mvn clean verify -Dtpc.version=4.31.1.Final
> {code}
> 4. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> See also: JBDS-2846
--
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 Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16286?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-16286:
------------------------------------------
I updated them but did not notice any difference, a complete re-build still takes up to 20 minutes:
{code}
1031 ACTIVE org.jboss.tools.cdi.core_1.6.0.Alpha1-v20131214-0017-B524
1032 ACTIVE org.jboss.tools.cdi.xml_1.6.0.Alpha1-v20131214-0017-B524
1050 ACTIVE org.jboss.tools.maven.cdi_1.6.0.Alpha1-v20131215-1032-B431
{code}
> 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, 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, 4 months