July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17939) Move JMX Navigator location to bottom left

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17939?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-17939. --------------------------------- Resolution: Done pushed to cr1 > Move JMX Navigator location to bottom left > ------------------------------------------ > > Key: JBIDE-17939 > URL: https://issues.jboss.org/browse/JBIDE-17939 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jmx, server > Affects Versions: 4.2.0.Beta3 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR1 > > > I was quite confused by the UI of JMX Navigator and Properties view - when I was connected to more than 1 local processes, I was wondering which one I was viewing in the Properties view. > It turns out that all throughout Eclipse, the Properties view usually shows details for an item that is currently selected in another view. But this can be confusing, because by default, both JMX Navigator and Properties views use the same window/location. So you never see both of them at once. > Rob suggested that the JMX Navigator could have a default location of botton left - below Project Explorer. I like the idea. But right now we don't display anything in that area. So Rob needs to investigate if this will work. > We need it to work for both scenarios: > 1. Server -> Shown in JMX Navigator > 2. Open the JMX Navigator using Window -> Show view -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-83) JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-83?page=com.atlassian.jira.plugin.s... ] Brian Fitzpatrick commented on JBTIS-83: ---------------------------------------- It seems a bit strange to me that we can't simply register these examples files without including ide-config.properties updates. I guess that's the gate-keeper to make sure bad examples don't find their way into the product? > JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration > -------------------------------------------------------- > > Key: JBTIS-83 > URL: https://issues.jboss.org/browse/JBTIS-83 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ESB > Affects Versions: 4.0.0 > Reporter: Len DiMaggio > Assignee: Brian Fitzpatrick > Fix For: 4.0.0 > > Attachments: jbtis-project-examples-community-7.1.xml > > > JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration > Steps as defined by Nick (thanks Nick!): > a) the contents of the examples are in a former employee's SVN workspace > and haven't been updated since a couple of years. They don't really work > as well as they could. > b) the examples are all mostly duplicated in the quickstarts folder that > ships with SOA-P 5.3.1. See > https://bugzilla.redhat.com/show_bug.cgi?id=951677 and > https://issues.jboss.org/browse/JBTIS-62 > Basically, we need to: > * fix the quickstarts in SOA-P 6 so they ACTUALLY WORK as importable > eclipse projects (merge in contents from duplicate examples in Denny's > workspace). Could decide to backport to 5.3 if there's a 5.3.2 planned; > if not, no great need. > * copy the older examples that are not already in SOA-P 5.3 - the ones > that are *exclusively* in Denny's workspace - into SOA-P 6 so they'll be > available there. > * update the BPEL Examples guide as needed > * document the fact that these examples are no longer available as > importable zipped example projects contributed by a plugin, but rather > as already-unpacked projects nested within the SOA-P runtime zip -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3105) Application wizard: show type of cartridge in create application wizard for "Code Anything" cartridges

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-3105?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-3105: ----------------------------------- Description: During the application creation process, if the user chooses a custom cartridge we should display the name of the cartridge from the .yml file in following wizard steps rather than "code anything". Reproducable steps: # EXEC: New OpenShift application wizard # EXEC: Select "Code Anything" Downloadable Cartridge. # Paste in yml file (example used: http://www.accursoft.com/cartridges/snap.yml) Result: ISSUE: Next screen shows Cartridge type: "code anything". EXPECTED: cartridge type from yml file. https://www.evernote.com/shard/s230/sh/6e600e31-5527-4159-856a-3c8fdf2463... !code-anything-cartridge-type.png! was: During the application creation process, if the user chooses a custom cartridge we should display the name of the cartridge from the .yml file in following wizard steps rather than "code anything". Reproducable steps: - New OpenShift application wizard - Code Anything Downloadable Cartridge. Paste in yml file (example used: http://www.accursoft.com/cartridges/snap.yml) - ISSUE: Next screen shows Cartridge type: "code anything". EXPECTED: cartridge type from yml file. https://www.evernote.com/shard/s230/sh/6e600e31-5527-4159-856a-3c8fdf2463... > Application wizard: show type of cartridge in create application wizard for "Code Anything" cartridges > ------------------------------------------------------------------------------------------------------ > > Key: JBDS-3105 > URL: https://issues.jboss.org/browse/JBDS-3105 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: openshift > Affects Versions: 8.0.0.Beta2 > Reporter: Catherine Robson > Assignee: Max Rydahl Andersen > Labels: application_wizard, uxtest > Attachments: code-anything-cartridge-type.png > > > During the application creation process, if the user chooses a custom cartridge we should display the name of the cartridge from the .yml file in following wizard steps rather than "code anything". > Reproducable steps: > # EXEC: New OpenShift application wizard > # EXEC: Select "Code Anything" Downloadable Cartridge. > # Paste in yml file (example used: http://www.accursoft.com/cartridges/snap.yml) > Result: > ISSUE: Next screen shows Cartridge type: "code anything". EXPECTED: cartridge type from yml file. https://www.evernote.com/shard/s230/sh/6e600e31-5527-4159-856a-3c8fdf2463... > !code-anything-cartridge-type.png! -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3105) Application wizard: show type of cartridge in create application wizard for "Code Anything" cartridges

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-3105?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-3105: ----------------------------------- Attachment: code-anything-cartridge-type.png > Application wizard: show type of cartridge in create application wizard for "Code Anything" cartridges > ------------------------------------------------------------------------------------------------------ > > Key: JBDS-3105 > URL: https://issues.jboss.org/browse/JBDS-3105 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: openshift > Affects Versions: 8.0.0.Beta2 > Reporter: Catherine Robson > Assignee: Max Rydahl Andersen > Labels: application_wizard, uxtest > Attachments: code-anything-cartridge-type.png > > > During the application creation process, if the user chooses a custom cartridge we should display the name of the cartridge from the .yml file in following wizard steps rather than "code anything". > Reproducable steps: > # EXEC: New OpenShift application wizard > # EXEC: Select "Code Anything" Downloadable Cartridge. > # Paste in yml file (example used: http://www.accursoft.com/cartridges/snap.yml) > Result: > ISSUE: Next screen shows Cartridge type: "code anything". EXPECTED: cartridge type from yml file. https://www.evernote.com/shard/s230/sh/6e600e31-5527-4159-856a-3c8fdf2463... > !code-anything-cartridge-type.png! -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3105) Application wizard: show type of cartridge in create application wizard for custom cartridges

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-3105?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-3105: ----------------------------------- Summary: Application wizard: show type of cartridge in create application wizard for custom cartridges (was: Show type of cartridge in create application wizard for custom cartridges) > Application wizard: show type of cartridge in create application wizard for custom cartridges > --------------------------------------------------------------------------------------------- > > Key: JBDS-3105 > URL: https://issues.jboss.org/browse/JBDS-3105 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: openshift > Affects Versions: 8.0.0.Beta2 > Reporter: Catherine Robson > Assignee: Max Rydahl Andersen > Labels: application_wizard, uxtest > > During the application creation process, if the user chooses a custom cartridge we should display the name of the cartridge from the .yml file in following wizard steps rather than "code anything". > Reproducable steps: > - New OpenShift application wizard > - Code Anything Downloadable Cartridge. Paste in yml file (example used: http://www.accursoft.com/cartridges/snap.yml) > - ISSUE: Next screen shows Cartridge type: "code anything". EXPECTED: cartridge type from yml file. https://www.evernote.com/shard/s230/sh/6e600e31-5527-4159-856a-3c8fdf2463... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3105) Application wizard: show type of cartridge in create application wizard for "Code Anything" cartridges

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-3105?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-3105: ----------------------------------- Summary: Application wizard: show type of cartridge in create application wizard for "Code Anything" cartridges (was: Application wizard: show type of cartridge in create application wizard for custom cartridges) > Application wizard: show type of cartridge in create application wizard for "Code Anything" cartridges > ------------------------------------------------------------------------------------------------------ > > Key: JBDS-3105 > URL: https://issues.jboss.org/browse/JBDS-3105 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: openshift > Affects Versions: 8.0.0.Beta2 > Reporter: Catherine Robson > Assignee: Max Rydahl Andersen > Labels: application_wizard, uxtest > > During the application creation process, if the user chooses a custom cartridge we should display the name of the cartridge from the .yml file in following wizard steps rather than "code anything". > Reproducable steps: > - New OpenShift application wizard > - Code Anything Downloadable Cartridge. Paste in yml file (example used: http://www.accursoft.com/cartridges/snap.yml) > - ISSUE: Next screen shows Cartridge type: "code anything". EXPECTED: cartridge type from yml file. https://www.evernote.com/shard/s230/sh/6e600e31-5527-4159-856a-3c8fdf2463... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3105) Application wizard: show type of cartridge in create application wizard for "Code Anything" cartridges

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-3105?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-3105: ----------------------------------- Labels: application_wizard uxtest (was: uxtest) > Application wizard: show type of cartridge in create application wizard for "Code Anything" cartridges > ------------------------------------------------------------------------------------------------------ > > Key: JBDS-3105 > URL: https://issues.jboss.org/browse/JBDS-3105 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: openshift > Affects Versions: 8.0.0.Beta2 > Reporter: Catherine Robson > Assignee: Max Rydahl Andersen > Labels: application_wizard, uxtest > > During the application creation process, if the user chooses a custom cartridge we should display the name of the cartridge from the .yml file in following wizard steps rather than "code anything". > Reproducable steps: > - New OpenShift application wizard > - Code Anything Downloadable Cartridge. Paste in yml file (example used: http://www.accursoft.com/cartridges/snap.yml) > - ISSUE: Next screen shows Cartridge type: "code anything". EXPECTED: cartridge type from yml file. https://www.evernote.com/shard/s230/sh/6e600e31-5527-4159-856a-3c8fdf2463... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3106) Application wizard: take less less screen height

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-3106?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-3106: ----------------------------------- Fix Version/s: 8.0.0.CR1 > Application wizard: take less less screen height > ------------------------------------------------ > > Key: JBDS-3106 > URL: https://issues.jboss.org/browse/JBDS-3106 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: openshift > Affects Versions: 8.0.0.Beta2 > Environment: Fedora, 1440x900 resolution screen > Reporter: Catherine Robson > Assignee: Max Rydahl Andersen > Labels: application_wizard, uxtest > Fix For: 8.0.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)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3103) Application wizard: Provide more info during OpenShift application creation

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-3103?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-3103: ----------------------------------- Fix Version/s: 9.0.x > Application wizard: Provide more info during OpenShift application creation > --------------------------------------------------------------------------- > > Key: JBDS-3103 > URL: https://issues.jboss.org/browse/JBDS-3103 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: openshift > Affects Versions: 8.0.0.Beta2 > Reporter: Catherine Robson > Assignee: Max Rydahl Andersen > Labels: application_wizard, uxtest > Fix For: 9.0.x > > > During the project setup on OpenShift from the create new application wizard, the user is not provided much information about what is happening. This process does take a little while, and users would be more comfortable if they could see into what is happening for a better idea of if the process is failing or still working. A "more info" dropdown could be used on the modal to show log file information during this process. > https://www.evernote.com/shard/s230/sh/a750beed-4fc9-43d0-90a6-495573f09a... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-83) JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-83?page=com.atlassian.jira.plugin.s... ] Brian Fitzpatrick commented on JBTIS-83: ---------------------------------------- So it should be - http://github.com/jbosstools/jbosstools-esb/raw/master/quickstarts/jbtis-... Got it! > JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration > -------------------------------------------------------- > > Key: JBTIS-83 > URL: https://issues.jboss.org/browse/JBTIS-83 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ESB > Affects Versions: 4.0.0 > Reporter: Len DiMaggio > Assignee: Brian Fitzpatrick > Fix For: 4.0.0 > > Attachments: jbtis-project-examples-community-7.1.xml > > > JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration > Steps as defined by Nick (thanks Nick!): > a) the contents of the examples are in a former employee's SVN workspace > and haven't been updated since a couple of years. They don't really work > as well as they could. > b) the examples are all mostly duplicated in the quickstarts folder that > ships with SOA-P 5.3.1. See > https://bugzilla.redhat.com/show_bug.cgi?id=951677 and > https://issues.jboss.org/browse/JBTIS-62 > Basically, we need to: > * fix the quickstarts in SOA-P 6 so they ACTUALLY WORK as importable > eclipse projects (merge in contents from duplicate examples in Denny's > workspace). Could decide to backport to 5.3 if there's a 5.3.2 planned; > if not, no great need. > * copy the older examples that are not already in SOA-P 5.3 - the ones > that are *exclusively* in Denny's workspace - into SOA-P 6 so they'll be > available there. > * update the BPEL Examples guide as needed > * document the fact that these examples are no longer available as > importable zipped example projects contributed by a plugin, but rather > as already-unpacked projects nested within the SOA-P runtime zip -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 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 July 2014