July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17988) JAX-RS Explorer doesn't show endpoint URI for fresh project in new workspace

by Radoslav Rábara (JIRA)

Radoslav Rábara created JBIDE-17988: --------------------------------------- Summary: JAX-RS Explorer doesn't show endpoint URI for fresh project in new workspace Key: JBIDE-17988 URL: https://issues.jboss.org/browse/JBIDE-17988 Project: Tools (JBoss Tools) Issue Type: Bug Components: webservices Affects Versions: 4.2.0.Beta3 Environment: Java 7, WildFly 8.1, Ubuntu 12.04 Reporter: Radoslav Rábara Fix For: 4.2.0.CR1 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-290) enable jboss tools usage tracking for plugins installed directly

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBTIS-290: ----------------------------------------- Summary: enable jboss tools usage tracking for plugins installed directly Key: JBTIS-290 URL: https://issues.jboss.org/browse/JBTIS-290 Project: JBoss Tools Integration Stack Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Max Rydahl Andersen Priority: Critical I think it is time we get integration stack components stats to show up more consistently in stats (right now we only collect switchyard - we should do more) There are two parts to it. 1) add a line to https://github.com/jbosstools/jbosstools-base/blob/master/usage/plugins/o... for the key feature we want to count as "one install" 2) add an *optional* dependency to your plugins to org.jboss.tools.usage - this ensures the statistics gathering happens no matter how the feature gets installed. The following line should be added to plugins manifest.mf: {code} org.jboss.tools.usage;resolution:=optional;x-installation:=greedy {code} Example: https://github.com/jbosstools/jbosstools-server/blob/master/archives/plug... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17983) track installations of JBoss Fuse Tooling

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17983?page=com.atlassian.jira.plugi... ] Lars Heinemann edited comment on JBIDE-17983 at 7/29/14 7:03 AM: ----------------------------------------------------------------- FUSE("org.fusesource.ide.camel.editor.feature") would be the current naming. Thats the camel editor feature and I guess most will install it. Later on we could use a "core" feature shared by all the other features...see etherpad about reorg fuse tooling. was (Author: lhein): FUSE("org.fusesource.ide.camel.editor.feature") would be the current naming. > track installations of JBoss Fuse Tooling > ----------------------------------------- > > Key: JBIDE-17983 > URL: https://issues.jboss.org/browse/JBIDE-17983 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: usage > Affects Versions: 4.2.0.Beta3 > Reporter: Lars Heinemann > Assignee: Max Rydahl Andersen > > We should track installations of JBoss Fuse Tooling. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17983) track installations of JBoss Fuse Tooling

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17983?page=com.atlassian.jira.plugi... ] Lars Heinemann commented on JBIDE-17983: ---------------------------------------- FUSE("org.fusesource.ide.camel.editor.feature") would be the current naming. > track installations of JBoss Fuse Tooling > ----------------------------------------- > > Key: JBIDE-17983 > URL: https://issues.jboss.org/browse/JBIDE-17983 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: usage > Affects Versions: 4.2.0.Beta3 > Reporter: Lars Heinemann > Assignee: Max Rydahl Andersen > > We should track installations of JBoss Fuse Tooling. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17983) track installations of JBoss Fuse Tooling

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17983?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17983: --------------------------------------------- basically what needs doing is this class: https://github.com/jbosstools/jbosstools-base/blob/master/usage/plugins/o... needs to have additional mappings added. [~lhein] do you have a feature name we can look for in Luna ? should be the feature "most" defining fuse. i.e. FUSE("org.fusetools.feature") ? > track installations of JBoss Fuse Tooling > ----------------------------------------- > > Key: JBIDE-17983 > URL: https://issues.jboss.org/browse/JBIDE-17983 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: usage > Affects Versions: 4.2.0.Beta3 > Reporter: Lars Heinemann > Assignee: Max Rydahl Andersen > > We should track installations of JBoss Fuse Tooling. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17973) Obscure database password

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17973?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17973: --------------------------------------------- Agree with Burr - hence why we punted this to next 4.3. > Obscure database password > ------------------------- > > Key: JBIDE-17973 > URL: https://issues.jboss.org/browse/JBIDE-17973 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.Beta2 > Reporter: Catherine Robson > Assignee: Max Rydahl Andersen > Priority: Minor > Labels: uxtest > Fix For: 4.3.x > > > When creating an OpenShift application with a database cartridge, the database password is shown in clear text. This password should be obscured. > It was noted that OpenShift does show clear text passwords in some locations, the difference here is that the user did not prompt for this information meaning we are displaying a password in clear text at a potential point where the user is not aware they need to be in a 'secure' environment. > Reproduce steps: > 1. Open new OpenShift Application wizard > 2. Sign in & proceed to next screen > 3. Choose application cartridge (JBoss EAP 6 for instance) & proceed to next screen > 4. Add embedded cartridge for database (mySQL 5.5 for instance) & proceed to next screen > 5. Click next on set up project screen > 6. Click finish on next screen > 7 -> ISSUE HERE. Once app is created, pop-up is shown with mySQL database password shown in clear text. Screenshot: https://www.evernote.com/shard/s230/sh/cd8123fb-a400-4699-ad08-bcbc06f7b5... > Expected: Password on this pop-up should be obscured. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17913) Users don't notice the software update tab - can we make it more visibile on the front page ?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17913?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17913: --------------------------------------------- adding Camel wont fix it for teiid, FSW and others. We are adding stats to central but that will just record for luna so it will take a while before we can use those data. > Users don't notice the software update tab - can we make it more visibile on the front page ? > --------------------------------------------------------------------------------------------- > > Key: JBIDE-17913 > URL: https://issues.jboss.org/browse/JBIDE-17913 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Reporter: Max Rydahl Andersen > Assignee: Burr Sutter > Fix For: 4.2.0.CR1 > > > We are getting complaints users does not notice that they can install things like integration stack from software update page. > Could we make this more clear onthe front page ? > Maybe remove the ticketmonster example image and put "highlights" from central on this page instead ? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17968) Application wizard: take less less screen height

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17968?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17968: ------------------------------------- Attachment: app-config-wizard-page.png > Application wizard: take less less screen height > ------------------------------------------------ > > Key: JBIDE-17968 > URL: https://issues.jboss.org/browse/JBIDE-17968 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Beta2 > Environment: Fedora, 1440x900 resolution screen > Reporter: Catherine Robson > Assignee: Max Rydahl Andersen > Labels: application_wizard, uxtest > Fix For: 4.2.0.CR1 > > Attachments: app-config-wizard-page.png, wizard-too-tall.png > > > For users with small screen sizes, the OpenShift create application wizard is very tall and might overflow their screen real-estate. Many of the dialogs in this wizard have lots of wasted space, so we should see if we can reduce the size of these dialogs as much as possible. > The height of the dialog is ~870px high. The most common resolution people run these days is 1366x768 - meaning we're already too high for people's viewable screen. > !wizard-too-tall.png! > ---------------- > Screen by screen analysis > ---------------- > Sign in dialog - ~550px wasted height: https://www.evernote.com/shard/s230/sh/baf765b4-cee1-470c-88a0-1afd237868... > Existing or new application dialog - ~145px wasted height: https://www.evernote.com/shard/s230/sh/d76f10b6-fb40-455d-bef6-d1b1ea44b0... > Name, domain, and embedded cartridges dialog - ~200px wasted height: https://www.evernote.com/shard/s230/sh/04381c6a-e9d7-4c6a-bd47-15b5b83a8e... > Configure project dialog - ~550px wasted height: https://www.evernote.com/shard/s230/sh/4932fd92-12b3-456f-8f9c-a25548f4f6... > Clone settings, processing dialog - ~480px wasted height: https://www.evernote.com/shard/s230/sh/0d921581-6d12-4ba0-8c99-dc4c904e90... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17968) Application wizard: take less less screen height

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17968?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-17968: ------------------------------------------ [~maxandersen] [~crobson] I also believe that the 2nd wizard page is the one that forces the whole wizard to get too tall (as said before, all the pages are kept to a consistent height that fits the needs of the tallest among them): !app-config-wizard-page.png! Nevertheless it's important to repeat that what's labeled as "wasted space" isnt wasted space. It's the space that the wizard reserves for the progress area. That's how wizard page are laid out in Eclipse when there's a progress bar: the space required for it is reserved, the progress bar is just hidden when not displaying some progress. > Application wizard: take less less screen height > ------------------------------------------------ > > Key: JBIDE-17968 > URL: https://issues.jboss.org/browse/JBIDE-17968 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Beta2 > Environment: Fedora, 1440x900 resolution screen > Reporter: Catherine Robson > Assignee: Max Rydahl Andersen > Labels: application_wizard, uxtest > Fix For: 4.2.0.CR1 > > Attachments: wizard-too-tall.png > > > For users with small screen sizes, the OpenShift create application wizard is very tall and might overflow their screen real-estate. Many of the dialogs in this wizard have lots of wasted space, so we should see if we can reduce the size of these dialogs as much as possible. > The height of the dialog is ~870px high. The most common resolution people run these days is 1366x768 - meaning we're already too high for people's viewable screen. > !wizard-too-tall.png! > ---------------- > Screen by screen analysis > ---------------- > Sign in dialog - ~550px wasted height: https://www.evernote.com/shard/s230/sh/baf765b4-cee1-470c-88a0-1afd237868... > Existing or new application dialog - ~145px wasted height: https://www.evernote.com/shard/s230/sh/d76f10b6-fb40-455d-bef6-d1b1ea44b0... > Name, domain, and embedded cartridges dialog - ~200px wasted height: https://www.evernote.com/shard/s230/sh/04381c6a-e9d7-4c6a-bd47-15b5b83a8e... > Configure project dialog - ~550px wasted height: https://www.evernote.com/shard/s230/sh/4932fd92-12b3-456f-8f9c-a25548f4f6... > Clone settings, processing dialog - ~480px wasted height: https://www.evernote.com/shard/s230/sh/0d921581-6d12-4ba0-8c99-dc4c904e90... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17676) Angular Code Assist doesn't work for angular phonecat app

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17676?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-17676: ------------------------------------- QE and users will appreciate it thanks > Angular Code Assist doesn't work for angular phonecat app > --------------------------------------------------------- > > Key: JBIDE-17676 > URL: https://issues.jboss.org/browse/JBIDE-17676 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.Beta2 > Environment: JBT 4.2.0.Beta2, Linux, AngulaJS for Eclipse installed from JBoss Central Early access > Reporter: Vlado Pakan > Assignee: Victor Rubezhny > Fix For: 4.2.0.CR1 > > Attachments: angular.png, angularjs-ca-in-attributes.png, angularjs-ca-in-expressions.png, angularjs-highlighting.png, angularjs-hyperlink.png, jbt-html-ca-in-attributes.png, jbt-html-hyperlink.png, phonecatControllers.png > > > 1. Follow steps from JBIDE-16544 to import angular phonecat project > 2. Open controllers.js in Java Script editor > ERROR: There is no code assist for angular.| or phonecatControllers.| > 3. Open phone-detail.html > ERROR: There is no code assist for {{|}} or {{phone.|}} > Is it not supported scenario? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2014