July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2949) Require Java 7 for the IDE

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2949?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2949: ------------------------------- Fix Version/s: 8.0.0.GA (was: 8.0.0.Beta3) > Require Java 7 for the IDE > -------------------------- > > Key: JBDS-2949 > URL: https://issues.jboss.org/browse/JBDS-2949 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: integration > Reporter: Max Rydahl Andersen > Assignee: Len DiMaggio > Fix For: 8.0.0.GA > > > Run the IDE with Java 7 (Java 6 no longer supported) (Users applications and servers can still use older and newer JDK’s like Java 1.4,5,6, 8 etc.) P1 > Java 6 is no longer supported by Oracle and by requiring Java 7 we can use better native IO and JavaFX (only on oracle) > Forge already requires Java 7. > Concerns: If we do not run with Java 6 we cannot support Xulrunner based VPE on OSX. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2949) Require Java 7 for the IDE

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2949?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2949: ------------------------------- Fix Version/s: 8.0.0.GA > Require Java 7 for the IDE > -------------------------- > > Key: JBDS-2949 > URL: https://issues.jboss.org/browse/JBDS-2949 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: integration > Reporter: Max Rydahl Andersen > Assignee: Len DiMaggio > Fix For: 8.0.0.GA > > > Run the IDE with Java 7 (Java 6 no longer supported) (Users applications and servers can still use older and newer JDK’s like Java 1.4,5,6, 8 etc.) P1 > Java 6 is no longer supported by Oracle and by requiring Java 7 we can use better native IO and JavaFX (only on oracle) > Forge already requires Java 7. > Concerns: If we do not run with Java 6 we cannot support Xulrunner based VPE on OSX. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17536) JBoss Tools Core Nightly update site fails to install if a new build is published during install

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17536?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17536: --------------------------------------------- nightly/luna should be made empty once mars happens and if we start up again point to the luna/ ngithly branch build. > JBoss Tools Core Nightly update site fails to install if a new build is published during install > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-17536 > URL: https://issues.jboss.org/browse/JBIDE-17536 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.2.0.CR1 > > > When you install JBT nightly from http://download.jboss.org/jbosstools/updates/nightly/core/master/ into Eclipse and during the build, a new nightly build replaces the old one, you can get a failure like this: > {code}http://download.jboss.org/jbosstools/updates/nightly/core/master/features/org.jboss.tools.wtp.runtimes.tomcat.feature_1.1.0.Beta3-v20140603-0027-B526.jar cannot be found{code} > This is because during your install, the old jars were replaced with the new jars, i.e. different filenames. > I'm not sure if it's something we really need to fix, it's open for discussion. But it happened to me yesterday and it wasn't the first time, so I'm throwing it on the table. > Nick offered this alternative: > install from a specific build folder instead of the "latest nightly" > http://download.jboss.org/jbosstools/builds/nightly/core/master/2014-06-0... > http://download.jboss.org/jbosstools/builds/nightly/core/master/2014-06-0... > But obviously that's just a workaround, not a real solution. > One way this could be achieved is this: plugins/ and features/ would contain jars from both the latest and previous builds. This way if you start installing (latest=build N) and in the middle of your installation there is a new build (N+1), there would still be jars for both N and N+1 builds. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17536) JBoss Tools Core Nightly update site fails to install if a new build is published during install

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17536?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17536: ------------------------------------ Only problem w/ using nightly/luna to point (either symlink or composite site) at http://download.jboss.org/jbosstools/builds/nightly/core/master/ is that it's only a "perfect fit" until the master branch contains bits for Mars... in which case this symlink will have to be changed. Since I don't want to move staging folders while QE is using them, I won't be moving the contents in /updates/staging/ until we start on CR1. Once that's done, we can generate composite metadata in /updates/staging/luna/ automatically. Details on how (and this pending TODO) will be added to the release guide: https://github.com/jbdevstudio/jbdevstudio-devdoc/pull/101 So, for now (Beta3c), here are the new URLs: http://download.jboss.org/jbosstools/updates/nightly/luna/ http://download.jboss.org/jbosstools/updates/staging/ For CR1, this will change to: http://download.jboss.org/jbosstools/updates/nightly/luna/ http://download.jboss.org/jbosstools/updates/staging/luna/ > JBoss Tools Core Nightly update site fails to install if a new build is published during install > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-17536 > URL: https://issues.jboss.org/browse/JBIDE-17536 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.2.0.CR1 > > > When you install JBT nightly from http://download.jboss.org/jbosstools/updates/nightly/core/master/ into Eclipse and during the build, a new nightly build replaces the old one, you can get a failure like this: > {code}http://download.jboss.org/jbosstools/updates/nightly/core/master/features/org.jboss.tools.wtp.runtimes.tomcat.feature_1.1.0.Beta3-v20140603-0027-B526.jar cannot be found{code} > This is because during your install, the old jars were replaced with the new jars, i.e. different filenames. > I'm not sure if it's something we really need to fix, it's open for discussion. But it happened to me yesterday and it wasn't the first time, so I'm throwing it on the table. > Nick offered this alternative: > install from a specific build folder instead of the "latest nightly" > http://download.jboss.org/jbosstools/builds/nightly/core/master/2014-06-0... > http://download.jboss.org/jbosstools/builds/nightly/core/master/2014-06-0... > But obviously that's just a workaround, not a real solution. > One way this could be achieved is this: plugins/ and features/ would contain jars from both the latest and previous builds. This way if you start installing (latest=build N) and in the middle of your installation there is a new build (N+1), there would still be jars for both N and N+1 builds. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3106) OpenShift create application wizard to take up less screen height

by Catherine Robson (JIRA)

[ https://issues.jboss.org/browse/JBDS-3106?page=com.atlassian.jira.plugin.... ] Catherine Robson updated JBDS-3106: ----------------------------------- Labels: uxtest (was: ) > OpenShift create application wizard to take up less screen height > ----------------------------------------------------------------- > > Key: JBDS-3106 > URL: https://issues.jboss.org/browse/JBDS-3106 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > 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: uxtest > > 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. > ---------------- > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3106) OpenShift create application wizard to take up less screen height

by Catherine Robson (JIRA)

Catherine Robson created JBDS-3106: -------------------------------------- Summary: OpenShift create application wizard to take up less screen height Key: JBDS-3106 URL: https://issues.jboss.org/browse/JBDS-3106 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request 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 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. ---------------- 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, 9 months

1
0
0 / 0

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

by Catherine Robson (JIRA)

Catherine Robson created JBDS-3105: -------------------------------------- Summary: 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: Feature Request Security Level: Public (Everyone can see) Components: openshift Affects Versions: 8.0.0.Beta2 Reporter: Catherine Robson Assignee: Max Rydahl Andersen 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3104) Add contextual help to OpenShift modals

by Catherine Robson (JIRA)

[ https://issues.jboss.org/browse/JBDS-3104?page=com.atlassian.jira.plugin.... ] Catherine Robson updated JBDS-3104: ----------------------------------- Labels: uxtest (was: ) > Add contextual help to OpenShift modals > --------------------------------------- > > Key: JBDS-3104 > URL: https://issues.jboss.org/browse/JBDS-3104 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: openshift > Affects Versions: 8.0.0.Beta2 > Reporter: Catherine Robson > Assignee: Max Rydahl Andersen > Labels: uxtest > > Many of the openshift modals do not provide contextual help that JBDS users expect throughout the application. > Create OpenShift Application modal: > Help button/Icon provided in bottom left of modal. Upon clicking, the help panel does not actually provide anything that helps the user understand what they need to do with the various screens throughout this wizard. > https://www.evernote.com/shard/s230/sh/3c712331-988c-4531-9b3b-b706973a9f... > The following OpenShift related dialogs do not provide a help icon/button at all and probably should: > - Configure OpenShift Markers (right click project -> OpenShift -> Configure Markers...) > - Domains (OpenShift Explorer pane -> right click OpenShift account -> Manage domains...) > - SSH Keys (OpenShift Explorer pane -> right click OpenShift account -> Manage SSH keys...) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3104) Add contextual help to OpenShift modals

by Catherine Robson (JIRA)

Catherine Robson created JBDS-3104: -------------------------------------- Summary: Add contextual help to OpenShift modals Key: JBDS-3104 URL: https://issues.jboss.org/browse/JBDS-3104 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: openshift Affects Versions: 8.0.0.Beta2 Reporter: Catherine Robson Assignee: Max Rydahl Andersen Many of the openshift modals do not provide contextual help that JBDS users expect throughout the application. Create OpenShift Application modal: Help button/Icon provided in bottom left of modal. Upon clicking, the help panel does not actually provide anything that helps the user understand what they need to do with the various screens throughout this wizard. https://www.evernote.com/shard/s230/sh/3c712331-988c-4531-9b3b-b706973a9f... The following OpenShift related dialogs do not provide a help icon/button at all and probably should: - Configure OpenShift Markers (right click project -> OpenShift -> Configure Markers...) - Domains (OpenShift Explorer pane -> right click OpenShift account -> Manage domains...) - SSH Keys (OpenShift Explorer pane -> right click OpenShift account -> Manage SSH keys...) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

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

by Catherine Robson (JIRA)

Catherine Robson created JBDS-3103: -------------------------------------- Summary: 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: Feature Request Security Level: Public (Everyone can see) Components: openshift Affects Versions: 8.0.0.Beta2 Reporter: Catherine Robson Assignee: Max Rydahl Andersen 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, 9 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