September 2013 - jbosstools-issues

[JBoss JIRA] (JBTIS-178) In JBTIS 4.1.3.beta2 - The SOA5 category includes Drools6 which may be incompatible with BRMS5 and SOA5

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-178?page=com.atlassian.jira.plugin.... ] Kris Verlaenen updated JBTIS-178: --------------------------------- Assignee: Paul Leacu (was: Kris Verlaenen) > In JBTIS 4.1.3.beta2 - The SOA5 category includes Drools6 which may be incompatible with BRMS5 and SOA5 > ------------------------------------------------------------------------------------------------------- > > Key: JBTIS-178 > URL: https://issues.jboss.org/browse/JBTIS-178 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: drools/ jBPM5 > Reporter: Len DiMaggio > Assignee: Paul Leacu > Attachments: drools1.png > > > See the attached screenshot - how can JBTIS support both SOA5/BRMS5 and 6? -- 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, 7 months

1
0
0 / 0

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

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15398?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-15398: ----------------------------------------------- I run clean/build of wildly workspace on Eclipse with Maven 1.5.0 (link above). When run with 1Gb memory, build stuck at 83%, memory usage is shown in !MemoryUsedWithNewMaven.png! Maybe new Maven does not have memory leak now, and releases memory, but it uses it a lot while building. > 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.1.1.Alpha2, 4.2.0.Alpha1 > > Attachments: cdi-build-1.txt, cdi-build-2.txt, cdi-build-3.txt, MemoryUsedOnWildflyBuild.png, MemoryUsedWithNewMaven.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 bulk 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

12 years, 7 months

1
0
0 / 0

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

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15398?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-15398: ------------------------------------------ Attachment: MemoryUsedWithNewMaven.png > 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.1.1.Alpha2, 4.2.0.Alpha1 > > Attachments: cdi-build-1.txt, cdi-build-2.txt, cdi-build-3.txt, MemoryUsedOnWildflyBuild.png, MemoryUsedWithNewMaven.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 bulk 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

12 years, 7 months

1
0
0 / 0

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15398?page=com.atlassian.jira.plugi... ] Alexey Kazakov edited comment on JBIDE-15398 at 9/16/13 4:23 PM: ----------------------------------------------------------------- Building wildfly projects takes less than a minute in my environment with 1GB + Slava's fix and without m2e plugins at all (I disabled m2e 1.4 after importing the projects with 4GB of memory). We have not tried m2e 1.5 yet to make sure it leave enough memory for CDI (and JDT). was (Author: akazakov): Building wildfly projects takes less than a minute in my environment with 1GB + Slava's fix and without m2e plugins at all (I disabled m2e 1.4 after importing the projects with 4GB of memory). We have not try m2e 1.5 yet to make sure it leave enough memory for CDI (and JDT). > 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.1.1.Alpha2, 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 bulk 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

12 years, 7 months

1
0
0 / 0

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15398?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-15398: ---------------------------------------- Building wildfly projects takes less than a minute in my environment with 1GB + Slava's fix and without m2e plugins at all (I disabled m2e 1.4 after importing the projects with 4GB of memory). We have not try m2e 1.5 yet to make sure it leave enough memory for CDI (and JDT). > 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.1.1.Alpha2, 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 bulk 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

12 years, 7 months

1
0
0 / 0

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15398?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-15398: ---------------------------------------- [~fbricon], have you had a chance to check out the Slava's PR on your environment? > 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.1.1.Alpha2, 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 bulk 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2733) Make Cordova tooling and CordovaSim available from software/update tab

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-2733?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-2733: ----------------------------------- - Separate - 2 items. - Same in both JBT and JBDS > Make Cordova tooling and CordovaSim available from software/update tab > ----------------------------------------------------------------------- > > Key: JBDS-2733 > URL: https://issues.jboss.org/browse/JBDS-2733 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: aerogear-hybrid, requirements > Reporter: Burr Sutter > Assignee: Nick Boldt > > Cordova should be available from JBDS, but it is not fully supported tech yet thus should be included/marked as a Technology Preview -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2733) Make Cordova tooling and CordovaSim available from software/update tab

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2733?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2733: ---------------------------------- And you'd like them as SEPARATE connectors, not one bundled connector? Same set up on both JBT and JBDS Central? > Make Cordova tooling and CordovaSim available from software/update tab > ----------------------------------------------------------------------- > > Key: JBDS-2733 > URL: https://issues.jboss.org/browse/JBDS-2733 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: aerogear-hybrid, requirements > Reporter: Burr Sutter > Assignee: Nick Boldt > > Cordova should be available from JBDS, but it is not fully supported tech yet thus should be included/marked as a Technology Preview -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2733) Make Cordova tooling and CordovaSim available from software/update tab

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-2733?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-2733: ----------------------------------- The Cordova & CordovaSim should be in the Mobile category. > Make Cordova tooling and CordovaSim available from software/update tab > ----------------------------------------------------------------------- > > Key: JBDS-2733 > URL: https://issues.jboss.org/browse/JBDS-2733 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: aerogear-hybrid, requirements > Reporter: Burr Sutter > Assignee: Nick Boldt > > Cordova should be available from JBDS, but it is not fully supported tech yet thus should be included/marked as a Technology Preview -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2729) Add mobile web quickstarts for JBoss Central

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-2729?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-2729: ----------------------------------- [~fbricon] - Subset of quickstarts - ones we know work well in the context of Eclipse. Granted, we only have a few at this time - Community or enterprise - both - it is better to keep the JBoss Central experience as close to identical as possible. - For this iteration, I was thinking that the mobile quickstarts displayed on JBoss Central would be mobile web only, not yet Cordova as that will be "tech preview" for a while longer. > Add mobile web quickstarts for JBoss Central > -------------------------------------------- > > Key: JBDS-2729 > URL: https://issues.jboss.org/browse/JBDS-2729 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: aerogear-hybrid, central, requirements > Reporter: Burr Sutter > Assignee: Burr Sutter > > The mobile web quickstarts being proced on WFK2 side should be included in JBoss Central -- 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, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2013