December 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15969) Investigate removing some m2e extensions for TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15969?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-15969: ---------------------------------------- [~fbricon] Do you know whether these ius are necessary to build/install JBT? If not, we can move them to Central as well. {code} <unit id="org.eclipse.m2e.wtp.jaxrs.feature.feature.group" version="1.1.0.20130821-1331"/> <unit id="org.eclipse.m2e.wtp.jpa.feature.feature.group" version="1.1.0.e43-20130821-1332"/> <unit id="org.eclipse.m2e.wtp.jsf.feature.feature.group" version="1.1.0.20130821-1331"/ {code} > Investigate removing some m2e extensions for TP > ----------------------------------------------- > > Key: JBIDE-15969 > URL: https://issues.jboss.org/browse/JBIDE-15969 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Affects Versions: 4.1.1.CR1, 4.2.0.Alpha1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.2.0.Alpha2 > > > It looks like m2e-wro4j is not used at all in JBoss Tools (only referenced in Central). > It also appears that other m2e extensions (maven.apt and m2e.jdt) are not necessary to build JBT, and are only made available by default in JBDS installer and on Central. > So I suggest the following changes: > * Remove the 3 maven extensions (m2e.wro4j, maven.apt, m2e.jdt) from the JBT target-platform, and keep them only in Central > * Remove m2e.wro4j from JBDS TP (as it's not part of installer) -- 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-16307) Update Mylyn tests to run on both Luna and Kepler

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-16307: ------------------------------------ Summary: Update Mylyn tests to run on both Luna and Kepler Key: JBIDE-16307 URL: https://issues.jboss.org/browse/JBIDE-16307 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: qa Affects Versions: 4.1.x Reporter: Len DiMaggio Assignee: Len DiMaggio Fix For: 4.1.x -- 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-16269) Parameterize URL from which to install SWTBot with install-grinder is setting up

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16269?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16269: ------------------------------- Fix Version/s: 4.1.1.Final > Parameterize URL from which to install SWTBot with install-grinder is setting up > -------------------------------------------------------------------------------- > > Key: JBIDE-16269 > URL: https://issues.jboss.org/browse/JBIDE-16269 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, testing-tools > Affects Versions: 4.1.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.1.Final > > > Install grinder tends to crap out when installing from download.eclipse.org, so we should have a way to override that URL and instead use a jboss.org URL where we've already mirrored the update site. > {code:title=https://github.com/jbosstools/jbosstools-install-grinder/blob/master/scripts/src/main/groovy/testInstall.groovy#L201} > proc.setArgs("-application org.eclipse.equinox.p2.director " + > "-repository http://download.eclipse.org/technology/swtbot/releases/latest/," + > {code} > Latest stable release of SWTBot is mirrored here: > http://download.jboss.org/jbosstools/updates/requirements/swtbot/2.1.1.20... -- 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-16290) Bugs using SWT over GTK3

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16290?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-16290: --------------------------------------- {quote} If you have any hint about what could cause this issue on the SWT side, make sure you add a comment to an existing Bugzilla or create a new one (and add me ass CC please). {quote} The issue happens because a control can be painted before it is realized. I am not sure if it is a GTK3 or an SWT issue. Will try to create a simple test and create a bug against Eclipse SWT. > Bugs using SWT over GTK3 > ------------------------ > > Key: JBIDE-16290 > URL: https://issues.jboss.org/browse/JBIDE-16290 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Reporter: Mickael Istria > Assignee: Snjezana Peco > Fix For: 4.2.x > > > This ticket is meant to list the bugs related to GTK3 affecting JBDS: > * JBIDE-16280 VPE/XulRunner crashes workbench > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=420581 > * Central tests uses SWT_GTK3=0 in its pom. > We should make sure all SWT issues we met are reported upstream and that we provide the necessary assistance to SWT developers to make sure everything will be stable for Luna/GA. > On Linux, most issues can be "hidden" by setting SWT_GTK3=0, but that's definitely not something we want to rely on for JBDS, as SWT over GTK2 will not be maintained in future. -- 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-16306) Dialog Wizard: jQuery Mobile Palette

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16306?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-16306: ------------------------------------- Version: 7.1.0.GA Build id: GA-v20131208-0703-B592 Build date: 20131208-0703 > Dialog Wizard: jQuery Mobile Palette > ------------------------------------ > > Key: JBIDE-16306 > URL: https://issues.jboss.org/browse/JBIDE-16306 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Reporter: Burr Sutter > Assignee: Viacheslav Kabanovich > Fix For: 4.2.0.Alpha2 > > > The Dialog preview seems to churn and if you are typing to quickly, using the backspace too often, clearing the field and overstriking, it loses focus. > http://screencast.com/t/7m6u7K9tqTw -- 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-16306) Dialog Wizard: jQuery Mobile Palette

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16306?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-16306: ---------------------------------------- [~burrsutter] what JBT/JBDS build are you using? 4.1.1.Final? > Dialog Wizard: jQuery Mobile Palette > ------------------------------------ > > Key: JBIDE-16306 > URL: https://issues.jboss.org/browse/JBIDE-16306 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Reporter: Burr Sutter > Assignee: Viacheslav Kabanovich > Fix For: 4.2.0.Alpha2 > > > The Dialog preview seems to churn and if you are typing to quickly, using the backspace too often, clearing the field and overstriking, it loses focus. > http://screencast.com/t/7m6u7K9tqTw -- 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-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 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

12 years, 7 months

1
0
0 / 0

[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 8:24 PM: ------------------------------------------------------------------ I also tried clean/build for the whole workspace. It took 5 minutes 30 seconds: !cleanBuild.png|thumbnail! {quote} The whole sluggishness is felt during incremental build {quote} Changing classpath causes a full build for projects. It's not a pure incremantal build actually. If the project's claspath has been changed we have to rebuild this project and its dependencies. And BTW Watching progress view I didn't see that CDI builder took a lot of the building time. The most time was spent on Maven Project Build then Compilation. For clean-rebuild XML validation also took noticeable time. CDI builder was pretty fast. It means I difinatly have not reproduced the problem. [~adietish] could you please provide the exact steps to reproduce this issue? was (Author: akazakov): I also tried clean/build for the whole workspace. It took 5 minutes 30 seconds: !cleanBuild.png|thumbnail! {quote} The whole sluggishness is felt during incremental build {quote} Changing classpath causes a full build for projects. It's not a pure incremantal build actually. If the project's claspath has been changed we have to rebuild this project and its dependencies. [~adietish] could you please provide the exact steps to reproduce this issue? > 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

12 years, 7 months

1
0
0 / 0

[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 also tried clean/build for the whole workspace. It took 5 minutes 30 seconds: !cleanBuild.png|thumbnail! {quote} The whole sluggishness is felt during incremental build {quote} Changing classpath causes a full build for projects. It's not a pure incremantal build actually. If the project's claspath has been changed we have to rebuild this project and its dependencies. [~adietish] could you please provide the exact steps to reproduce this issue? > 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

12 years, 7 months

1
0
0 / 0

[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: cleanBuild.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, 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

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 December 2013