December 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-16214) Code Coverage jobs needs to have locally available measured plugins

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16214?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16214: ---------------------------------------- [~vpakan]: can you please details the command you use, from which branch and other useful information to easily reproduce this behaviour? > Code Coverage jobs needs to have locally available measured plugins > ------------------------------------------------------------------- > > Key: JBIDE-16214 > URL: https://issues.jboss.org/browse/JBIDE-16214 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.1.1.CR1 > Reporter: Vlado Pakan > Assignee: Mickael Istria > Fix For: 4.1.x > > > Code Coverage calculating via maven build returns 0% coverage because it's using source code and binary plugins installed from update site. > When these are built locally prior to build calculating code coverage it returns correct results. > Unfortunately sometimes maven build used plugins installed from update site instead of those which are locally build. > We need to find way how to fix this. > It's already reported here https://bugs.eclipse.org/bugs/show_bug.cgi?id=352560 -- 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

1
0
0 / 0

[JBoss JIRA] (JBDS-2866) CordovaSim Debugger

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBDS-2866?page=com.atlassian.jira.plugin.... ] Ilya Buziuk commented on JBDS-2866: ----------------------------------- [~burrsutter] Well, a & b are tightly coupled (because of the automatic closing of the FireBug, there is no way to get console.log on deviceready). I will investigate it more properly but, as [~kmarmaliykov] said, we will probably can't find a solution. However, I do have good news. This week I was struggling with the DevTools migration to the BrowserSim / CordovaSim and here is the result: http://www.youtube.com/watch?v=hF0EJFWgcZg&feature=youtu.be . There is plenty stuff to implement yet (WebEngine switching - SWT.WebKit or JavaFx WebView / menu and preferences, etc.), but nevertheless we can see the light at the end of the tunnel now :-) > CordovaSim Debugger > ------------------- > > Key: JBDS-2866 > URL: https://issues.jboss.org/browse/JBDS-2866 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: browsersim, requirements > Reporter: Burr Sutter > Assignee: Ilya Buziuk > > The current FireBug Lite in CordovaSim has the following limitations: > 1) When using LiveReload, the window closes with every reload > 2) Various "page load" events with console.log statements are not visible in FireBug Lite console, like having console.log() in your deviceready > http://screencast.com/t/RRGhV9PV > Note: I forgot to add the Console Cordova plugin, not sure if that is necessary but the window closes, so not sure how I would see the message -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-16302) Make jobs suffix = stream (eg 4.2.luna instead of 42)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16302?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-16302. ------------------------------------ Resolution: Done [~nickboldt] I renamed CI jobs on 4.2.luna branch, and the composite file was changed too. For the moment, it doesn't bring much, but it's one less variable to keep/convention to remember. > Make jobs suffix = stream (eg 4.2.luna instead of 42) > ----------------------------------------------------- > > Key: JBIDE-16302 > URL: https://issues.jboss.org/browse/JBIDE-16302 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Alpha1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.0.Alpha2 > > > In order to reduce the amount of conventions and allow better factorization, we should get rid of the current convention (jobname_42) on job/nightly-build/staging names and replace it by the same convention as _composite_ and aggregate site (4.2.luna). > For example: > * jbosstools-central_42 => jbosstools-central_4.2.luna > * as a consequence download.jboss.org/jbosstools/builds/staging/jbosstools-central_42/ => download.jboss.org/jbosstools/builds/staging/jbosstools-central_4.2.luna/ > And > * devstudio.product_80 => devstudio.product_8.0.luna -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-16302) Make jobs suffix = stream (eg 4.2.luna instead of 42)

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-16302: -------------------------------------- Summary: Make jobs suffix = stream (eg 4.2.luna instead of 42) Key: JBIDE-16302 URL: https://issues.jboss.org/browse/JBIDE-16302 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: build Affects Versions: 4.2.0.Alpha1 Reporter: Mickael Istria Assignee: Mickael Istria Fix For: 4.2.0.Alpha2 In order to reduce the amount of conventions and allow better factorization, we should get rid of the current convention (jobname_42) on job/nightly-build/staging names and replace it by the same convention as _composite_ and aggregate site (4.2.luna). For example: * jbosstools-central_42 => jbosstools-central_4.2.luna * as a consequence download.jboss.org/jbosstools/builds/staging/jbosstools-central_42/ => download.jboss.org/jbosstools/builds/staging/jbosstools-central_4.2.luna/ And * devstudio.product_80 => devstudio.product_8.0.luna -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-16290) Bugs using SWT over GTK3

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16290?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16290: ---------------------------------------- [~snjeza] Your patch for jbosstools-central works like a charm! It was used in order to build https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... which is blue, +1 for merging it. 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). > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16301) No combo to select Target Runtime in examples dilaog

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16301?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-16301: ------------------------------------- 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 Zipped quickstarts do not generate content dynamically, so there's no need to select the runtime at that point. 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? > 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 > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-16290) Bugs using SWT over GTK3

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16290?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-16290 at 12/13/13 2:59 AM: ------------------------------------------------------------------ -Can you please copy your comment related to JBIDE-16280 on the ticket there? I agree that this issue is probably top-priority and that your suggestion (building against GTK3) seems to be the best thing to do.- Just noticed it was already done. The fix you found for jbosstools-central seems great! was (Author: mickael_istria): Can you please copy your comment related to JBIDE-16280 on the ticket there? I agree that this issue is probably top-priority and that your suggestion (building against GTK3) seems to be the best thing to do. The fix you found for jbosstools-central seems great! > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16290) Bugs using SWT over GTK3

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16290?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16290: ---------------------------------------- Can you please copy your comment related to JBIDE-16280 on the ticket there? I agree that this issue is probably top-priority and that your suggestion (building against GTK3) seems to be the best thing to do. The fix you found for jbosstools-central seems great! > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16301) No combo to select Target Runtime in examples dilaog

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-16301: ------------------------------------- Summary: 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 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

1
0
0 / 0

[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 updated JBIDE-16301: ---------------------------------- Attachment: Selection_025.png > 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 > 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

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