February 2014 - jbosstools-issues

[JBoss JIRA] (JBDS-2916) Installer should have the same application icon as JBoss Developer Studio and appropriate name

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2916?page=com.atlassian.jira.plugin.... ] Denis Golovin edited comment on JBDS-2916 at 2/19/14 6:09 PM: -------------------------------------------------------------- Proposed PR https://github.com/jbdevstudio/jbdevstudio-product/pull/140 !Tooltip_041.png! was (Author: dgolovin): Proposed PR https://github.com/jbdevstudio/jbdevstudio-product/pull/140 > Installer should have the same application icon as JBoss Developer Studio and appropriate name > ---------------------------------------------------------------------------------------------- > > Key: JBDS-2916 > URL: https://issues.jboss.org/browse/JBDS-2916 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer, upstream > Affects Versions: 8.0.0.Alpha2 > Reporter: Denis Golovin > Fix For: 8.0.0.Beta1 > > Attachments: Tooltip_040.png, Tooltip_041.png > > > Current installer has IzPack icon for main frame and for app switcher, but it should be JBoss Developer Studio icon. > Name is weird (see image below) > !Tooltip_040.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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2916) Installer should have the same application icon as JBoss Developer Studio and appropriate name

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2916?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-2916: ------------------------------------- Proposed PR https://github.com/jbdevstudio/jbdevstudio-product/pull/140 > Installer should have the same application icon as JBoss Developer Studio and appropriate name > ---------------------------------------------------------------------------------------------- > > Key: JBDS-2916 > URL: https://issues.jboss.org/browse/JBDS-2916 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer, upstream > Affects Versions: 8.0.0.Alpha2 > Reporter: Denis Golovin > Fix For: 8.0.0.Beta1 > > Attachments: Tooltip_040.png > > > Current installer has IzPack icon for main frame and for app switcher, but it should be JBoss Developer Studio icon. > Name is weird (see image below) > !Tooltip_040.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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2916) Installer should have the same application icon as JBoss Developer Studio and appropriate name

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2916?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-2916: -------------------------------- CDW devel_ack: + (was: ?) > Installer should have the same application icon as JBoss Developer Studio and appropriate name > ---------------------------------------------------------------------------------------------- > > Key: JBDS-2916 > URL: https://issues.jboss.org/browse/JBDS-2916 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer, upstream > Affects Versions: 8.0.0.Alpha2 > Reporter: Denis Golovin > Fix For: 8.0.0.Beta1 > > Attachments: Tooltip_040.png > > > Current installer has IzPack icon for main frame and for app switcher, but it should be JBoss Developer Studio icon. > Name is weird (see image below) > !Tooltip_040.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, 2 months

1
0
0 / 0

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

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/JBDS-2852?page=com.atlassian.jira.plugin.... ] Barry LaFond commented on JBDS-2852: ------------------------------------ Since Teiid Designer's artifacts are models and VDBs containing models, we inject connection data into source models, so when added to VDB for deployment we can insure that Data Sources are created/discovered on the server prior to deployment/execution. We have a manual step/action described here: http://docs.jboss.org/teiid/designer/8.3/user-guide/en-US/html/test-model... as well as here: http://docs.jboss.org/teiid/designer/8.3/user-guide/en-US/html/importers-... FYI.. we currently contribute 9 custom Connection Profiles through the Data Tools extension. > 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 > Labels: QE_JBDS80_needinfo > > 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

[JBoss JIRA] (JBDS-2848) Usage Stats for actual used features

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-2848?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-2848: ----------------------------------- One item that is very important to me, is anyone using our Forge tooling inside of JBDS? inside of JBT? It important we see the numbers between the two userbases and how often Forge is actually being used. > Usage Stats for actual used features > ------------------------------------ > > Key: JBDS-2848 > URL: https://issues.jboss.org/browse/JBDS-2848 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: requirements, usage > Reporter: Burr Sutter > Assignee: Alexey Kazakov > Priority: Critical > Labels: QE_JBDS80_needinfo > > We currently know that people are using JBDS/JBoss Tools but not specifically which features people are actively using. Our key base metric is "daily usage". > Areas worth tracking include (in priority order): > - Use of the OpenShift Wizard to successful completion vs error > - Use of the archetypes on JBoss Central (adding Hybrid/Cordova in JBDS 8) > - Successful installation of the features found on Software/Update tab of JBoss Central > - Use of the JSF/RichFaces Visual Page Editor > - Use of the Hibernate Tooling > - Use of the jQuery Mobile Palette > - Use of BrowserSim > - Use of CordovaSim > We will also need to update http://www.jboss.org/tools/usage and https://devstudio.jboss.com/usage/ > Ideally, we would be able to distinguish between a single "hit" (end-user opened the tool) vs active usage (end-user spent repeatedly using the tool) > Our metric gathering service should be "scalable" enough to allow for tracking of the individual SOA features such as Drools, jBPM, Switchyard, Camel, etc in the 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-2852) Database/source/connection Usability

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-2852?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-2852: ----------------------------------- [~blafond]Do you have a small screencast of what this looks like? It could be a big win. I think Max is one of the few people on the planet that know the arcane magic to make it all work in Eclipse-land :-) > 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 > Labels: QE_JBDS80_needinfo > > 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

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

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/JBDS-2852?page=com.atlassian.jira.plugin.... ] Barry LaFond commented on JBDS-2852: ------------------------------------ FYI Teiid Designer has streamlined it's process of utilizing Connection Profiles for basic data source definition, and transitioning that data through our Teiid runtime/API to manage the data sources (-ds.xml) including deploying drivers if need be. It's not a global solution, but we have some experience. > 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 > Labels: QE_JBDS80_needinfo > > 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

[JBoss JIRA] (JBDS-2849) Document Offline Usage

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-2849?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-2849: ----------------------------------- [~ldimaggio] "Other than OpenShift, do we know for certain which other tools/features will while the user is offline?" Our mission is to make EVERYTHING work offline - you could even deploy to your local Openshift Enterprise running on your private network. I would prefer to enumerate what does not work today > Document Offline Usage > ---------------------- > > Key: JBDS-2849 > URL: https://issues.jboss.org/browse/JBDS-2849 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: requirements > Reporter: Burr Sutter > Assignee: Michelle Murray > Labels: QE_JBDS80_needinfo > > Working with the Training team, document how JBDS is to be used in an offline state. -- 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-12355) JBoss tools website redesign

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12355?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-12355: -------------------------------------- Some quick comments on: http://tools-stg.jboss.org/ 1) I like the uncluttered look. It's good, I think, to keep the screens easier to navigate. Sometimes, too many choices on the same screen is worse than fewer choices. 2) It's good that the "download" button is so prominent on http://tools-stg.jboss.org/ - I'm betting that most new users just want to do a download and "kick the tires" - so making it easier for them to find the downloads is important. 3) The download page reached from http://tools-stg.jboss.org/ ---> http://tools-stg.jboss.org/downloads/ includes both JBDS and JBT - but the referencing page http://tools-stg.jboss.org/ does not display "JBDS" (it mentions JBT only). > JBoss tools website redesign > ---------------------------- > > Key: JBIDE-12355 > URL: https://issues.jboss.org/browse/JBIDE-12355 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: website > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 4.2.0.Alpha2 > > Attachments: downloads.bmml, downloads.bmml, downloads.bmml, downloads.png, download_archives.bmml, download_archives.bmml, download_archives.png, download_jbosstools_latest.bmml, download_jbosstools_latest.bmml, download_jbosstools_latest.png, features-page-mockup.bmml, features-page-mockup.png, mockupfromjbw.bmml, mockupfromjbw.png, specific-component-features.bmml, specific-component-features.png > > > jboss.org/tools have started to have issues scaling on several fronts. > 1) no clear path to what we want users to download (too many upfront choices) > 2) we are missing info about what jbosstools actually does > 3) updating it requires using magnolia (limited access, no option for easy review or experimenting without pushing fully live) > 4) the content is generally getting very stale > 5) it is not easy to blog via community.jboss.org - resulting in less content (#4) > etc. etc. > 6) update for releases are a lot of copy/paste and manual updating. if we want to reorg that content it is alot of manual labor. > We are looking into using awestruct as a way to solve a lot of the technical/practical issues. Other projects like wildfly.org, arquillian.org, aerogear.org, infinispan.org have used that and its improved their publishing process and the content. > https://github.com/xcoulon/jbosstools-website has a current experimental push of the progress. > http://tools-stg.jboss.org/ <-- current staged version -- 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-2916) Installer should have the same application icon as JBoss Developer Studio and appropriate name

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2916?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-2916: ------------------------------------- It is upstream issue in jvm for linux http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6528430 > Installer should have the same application icon as JBoss Developer Studio and appropriate name > ---------------------------------------------------------------------------------------------- > > Key: JBDS-2916 > URL: https://issues.jboss.org/browse/JBDS-2916 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer, upstream > Affects Versions: 8.0.0.Alpha2 > Reporter: Denis Golovin > Fix For: 8.0.0.Beta1 > > Attachments: Tooltip_040.png > > > Current installer has IzPack icon for main frame and for app switcher, but it should be JBoss Developer Studio icon. > Name is weird (see image below) > !Tooltip_040.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, 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 February 2014