January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16355) replace release_notes*.html files posted to sourceforge w/ link directly to JIRA query

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16355?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16355: ---------------------------------------- Do people really use this sourceforge location? Both our website and marketplace link to download.jboss.org, so I believe this sourceforge location should simply be abandonned. [~maxandersen] What do you think? Should we drop sourceforge? > replace release_notes*.html files posted to sourceforge w/ link directly to JIRA query > -------------------------------------------------------------------------------------- > > Key: JBIDE-16355 > URL: https://issues.jboss.org/browse/JBIDE-16355 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Alpha2 > Reporter: Nick Boldt > Assignee: Mickael Istria > > Re: files like: > http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools4.2.0.x/... > {quote} > (2014-01-14 13:55:54) nickboldt: desire to produce the file is clearly no longer urgent, so I could open a JIRA asking to trash it from the rel guide requirement for JBT 4.2 and see who disagrees > (2014-01-14 13:56:04) maxandersen: yeah - and I keep saying: please dont use mixed camelcases but they keep occuring ;) > (2014-01-14 13:56:25) maxandersen: yeah I would just post a jira query IMO for these. > (2014-01-14 13:56:56) maxandersen: dont use mixed camelcases for artifacts urls I mean. > (2014-01-14 13:57:58) maxandersen: interesting - *1* hit on google for jbide zz_release_notes ;) > (2014-01-14 13:58:34) maxandersen: so yeah, jira query ftw for this. > {quote} > Instead of producing a snapshot from JIRA as a canned HTML page, we should for JBT 4.2 / JBDS 8 simply link to a query. > That way too we can have a query for "just this milestone" and "all changes in the 4.2.x stream (alpha1, alpha2, beta1, cr1, final). > We can also produce a query for both JBT and JBDS. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16290) Fixing SWT issues in Luna

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16290?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-16290: ---------------------------------------- Summary: Fixing SWT issues in Luna (was: Bugs using SWT over GTK3) > Fixing SWT issues in Luna > ------------------------- > > 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. > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127 > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16290) Fixing SWT issues in Luna

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16290?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16290: --------------------------------------------- renaming this bug to match the others about fixing stuff in luna. Lets keep this one to issues related to SWT/GTK3 and https://issues.jboss.org/browse/JBIDE-16360 for the browser integration issues (here we are trying to get rid of xulrunner and using webkit but webkit itself have issues too) > Fixing SWT issues in Luna > ------------------------- > > 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. > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127 > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2866) CordovaSim Debugger

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2866?page=com.atlassian.jira.plugin.... ] Michelle Murray updated JBDS-2866: ---------------------------------- Affects: Documentation (Ref Guide, User Guide, etc.) > 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 > Attachments: DevToolsMenu.png > > > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16360) Fix Browser engine Integration in Luna

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16360?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-16360: ---------------------------------------- Fix Version/s: 4.2.0.Beta1 > Fix Browser engine Integration in Luna > -------------------------------------- > > Key: JBIDE-16360 > URL: https://issues.jboss.org/browse/JBIDE-16360 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Reporter: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.2.0.Beta1 > > > The browser integration in eclipse is important for our tools. This jira is to track issues we are working on or there are important for us to get fixed related to browser integration in eclipse which relate to our browsersim and to the visual page editor -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16361) Fix SWT on Linux in Luna

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16361?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen closed JBIDE-16361. --------------------------------------- Resolution: Duplicate Issue > Fix SWT on Linux in Luna > ------------------------ > > Key: JBIDE-16361 > URL: https://issues.jboss.org/browse/JBIDE-16361 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Reporter: Max Rydahl Andersen > Priority: Blocker > > SWT on Linux is important for our tools. This jira is to track issues we are working on or there are important for us to get fixed related to SWT on Linux -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16361) Fix SWT on Linux in Luna

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-16361: ------------------------------------------- Summary: Fix SWT on Linux in Luna Key: JBIDE-16361 URL: https://issues.jboss.org/browse/JBIDE-16361 Project: Tools (JBoss Tools) Issue Type: Bug Components: upstream Reporter: Max Rydahl Andersen Priority: Blocker SWT on Linux is important for our tools. This jira is to track issues we are working on or there are important for us to get fixed related to SWT on Linux -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16360) Fix Browser engine Integration in Luna

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-16360: ------------------------------------------- Summary: Fix Browser engine Integration in Luna Key: JBIDE-16360 URL: https://issues.jboss.org/browse/JBIDE-16360 Project: Tools (JBoss Tools) Issue Type: Bug Components: upstream Reporter: Max Rydahl Andersen Priority: Blocker The browser integration in eclipse is important for our tools. This jira is to track issues we are working on or there are important for us to get fixed related to browser integration in eclipse which relate to our browsersim and to the visual page editor -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16359) Fix JSDT in Luna

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-16359: ------------------------------------------- Summary: Fix JSDT in Luna Key: JBIDE-16359 URL: https://issues.jboss.org/browse/JBIDE-16359 Project: Tools (JBoss Tools) Issue Type: Bug Components: upstream Reporter: Victor Rubezhny Priority: Blocker Fix For: 4.2.0.Beta1 JSDT is important for our tools. This jira is to track issues we are working on or there are important for us to get fixed related to JSDT in eclipse. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2852) Database/source/connection Usability

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2852?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-2852: --------------------------------------- Docs Q: Can we be more specific about what exact changes need to occur? For example, wizard X should be changed to do action Y or ask user for information Z. Database actions and Hibernate Tools aren't yet document in the new JBDS/JBT User Guide but the plan is to get them documented for 8.0. If changes are to occur to existing workflows, wizards, etc. these need to be clearly identified so that they aren't documented one way only to find they change before release. > Database/source/connection Usability > ------------------------------------ > > Key: JBDS-2852 > URL: https://issues.jboss.org/browse/JBDS-2852 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: integration, requirements > Reporter: Burr Sutter > > Connecting to a database from within JBDS/Eclipse is a multi-step, multi-screen, potentially error-prone challenge. > Forge is involved as it can generate entities from schema > Datasources are needed in/on AS/Wildfly/EAP in order for the project deploy > Persistence.xml may needed to be tweaked for the datasource > End-user would like to navigate the schema in the DTP/Hibernate Tools, interactively review the data and there was once a feature for viewing an ORM diagram that I seem to have forgotten how it is displayed. > What happens when a project that needs a database connection is imported into the IDE? > This was partially addressed with > https://issues.jboss.org/browse/JBIDE-15263 > Let's see if we can continue to improve the workflow by reducing steps, making it more obvious what steps are required (e.g. hey developer, get the mysql driver .jar), auto generating the -ds.xml, with a decent explanation for the end-user to follow. -- 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, 2 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 January 2014