June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20103) Do not show Loading tree item in explorer while loading v3 connection.

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20103?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-20103: ---------------------------------- Labels: explorer (was: ) > Do not show Loading tree item in explorer while loading v3 connection. > ---------------------------------------------------------------------- > > Key: JBIDE-20103 > URL: https://issues.jboss.org/browse/JBIDE-20103 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Priority: Minor > Labels: explorer > Attachments: connection_loading.png > > > After double click or choosing Refresh in context menu of a v3 connection there is shown tree item Loading right under the connect !connection_loading.png! > If connection does not contain any project, the item is removed and only connection item is shown again. But in mean time (during the loading), the item is shown. It acts, at least for me, not pretty (a bit distracting, if I am running OpenShift locally, it pretty fast expand and collapse, really not nice). We should just show running loading resources job and right after job is done, the items under the specific connection should be updated (if there is any project, show it, if there is nothing, do not show anything). For v2 connection we do not show any similar tree item, we just load domain(s) if there is any. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20103) Do not show Loading tree item in explorer while loading v3 connection.

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-20103: ------------------------------------- Summary: Do not show Loading tree item in explorer while loading v3 connection. Key: JBIDE-20103 URL: https://issues.jboss.org/browse/JBIDE-20103 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.3.0.Beta1 Reporter: Marián Labuda Priority: Minor Attachments: connection_loading.png After double click or choosing Refresh in context menu of a v3 connection there is shown tree item Loading right under the connect !connection_loading.png! If connection does not contain any project, the item is removed and only connection item is shown again. But in mean time (during the loading), the item is shown. It acts, at least for me, not pretty (a bit distracting, if I am running OpenShift locally, it pretty fast expand and collapse, really not nice). We should just show running loading resources job and right after job is done, the items under the specific connection should be updated (if there is any project, show it, if there is nothing, do not show anything). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20103) Do not show Loading tree item in explorer while loading v3 connection.

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20103?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-20103: ---------------------------------- Attachment: connection_loading.png > Do not show Loading tree item in explorer while loading v3 connection. > ---------------------------------------------------------------------- > > Key: JBIDE-20103 > URL: https://issues.jboss.org/browse/JBIDE-20103 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Priority: Minor > Attachments: connection_loading.png > > > After double click or choosing Refresh in context menu of a v3 connection there is shown tree item Loading right under the connect !connection_loading.png! > If connection does not contain any project, the item is removed and only connection item is shown again. But in mean time (during the loading), the item is shown. It acts, at least for me, not pretty (a bit distracting, if I am running OpenShift locally, it pretty fast expand and collapse, really not nice). We should just show running loading resources job and right after job is done, the items under the specific connection should be updated (if there is any project, show it, if there is nothing, do not show anything). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3463) Headless installer should at least warn when running on Java 7

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3463?page=com.atlassian.jira.plugin.... ] Jan Richter commented on JBDS-3463: ----------------------------------- Just like this: {noformat} java -jar jboss-devstudio-9.0.0.Beta1-v20150614-0409-B50-installer-standalone.jar InstallConfigRecord.xml {noformat} Where I'm using Java 7 and the install config is taken from a previous JBDS 9.0.0.Beta1 installation but again with Java 7 set as the target JVM. > Headless installer should at least warn when running on Java 7 > -------------------------------------------------------------- > > Key: JBDS-3463 > URL: https://issues.jboss.org/browse/JBDS-3463 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Affects Versions: 9.0.0.Beta1 > Reporter: Jan Richter > > While the GUI installer won't let you complete the installation without choosing Java 8 or higher, the headless installer doesn't care. > If you give it a config with path to Java 7, it will install everything and set Java 7 as -vm in jbdevstudio.ini. I think it should behave consistently with the GUI or at least warn that the Java I'm installing with is not supported anymore. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20096) creating eap-simple from templates and show in browser tries to open 'eap.local'

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20096?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-20096: --------------------------------------- eap6-basic.sti.json specify parameter APPLICATION_HOSTNAME with value "eap-app.local". That is probably root of this issue, because in routing it references to this variable. But it is possible to change routing, while creating an application, you can modify the APPLICATION_HOSTNAME field (but it has to suit RFC 952, otherwise routing is not created). > creating eap-simple from templates and show in browser tries to open 'eap.local' > -------------------------------------------------------------------------------- > > Key: JBIDE-20096 > URL: https://issues.jboss.org/browse/JBIDE-20096 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Priority: Critical > > not sure what is to "blame" here but creating app from https://github.com/jboss-openshift/application-templates/blob/master/eap/... (v3beta1) results in app getting created but show in browser wants me to go to "eap.local" which pretty sure that is not something that exist from the outside. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20100) how to make users aware of fuse and other tooling only being available from earlyaccess?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20100?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-20100: ---------------------------------------- We could imagine changing the checkbox name "Enable Early-Access" to "Enable Early-Access and discover 12 new plugins". It will encourage people to try it a bit more. > how to make users aware of fuse and other tooling only being available from earlyaccess? > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20100 > URL: https://issues.jboss.org/browse/JBIDE-20100 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > > [~jtyrrell] find it confusing when he cannot see Fuse and other earlyaccess features immediately on the install page. > Some comments: > "I install JBDS 8.1 and click on the JBoss Integration and SOA Development, but where is the Fuse tooling in that list." > "<without earlyaccess> why doesn’t my screen shot tell me to use an older version of JBDS or something." > Suggestion: > "when I picked the Integration Stack a greyed out Fuse IDE thingy in the list of choices, and something like (Select early Access) to enable this feature." > I'm fine exploring options to show early access features more prominently but would prefer we would not need to treat Fuse "special" so maybe we should have a "Early Access" section at the bottom instead of filtered in between everything else ? > and for any connectors that has additional/different features just add a "Extra features available in Early access " comment ? > But what to do when Fuse or others dont even have an earlyaccess out yet ? (like is currently the state for devstudio 9) > [~crobson], [~aileenc] and [~lhein] got any suggestions ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-657) JBDS 9 Beta1 Release Notes Intro Content

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-657?page=com.atlassian.jira.plug... ] Martin Malina reassigned TOOLSDOC-657: -------------------------------------- Assignee: Misha Ali (was: Martin Malina) Reassigning to Misha as I think we need more content. > JBDS 9 Beta1 Release Notes Intro Content > ---------------------------------------- > > Key: TOOLSDOC-657 > URL: https://issues.jboss.org/browse/TOOLSDOC-657 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Reporter: Misha Ali > Assignee: Misha Ali > > Hi Martin, > I haven't included the release note issues yet, but I wanted to get some review on the introductory text (i.e. everything but the known and resolved issue pages) here: > http://docbuilder.usersys.redhat.com/23108/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3463) Headless installer should at least warn when running on Java 7

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3463?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3463: ------------------------------------------- just to be sure we are testing the same thing - how exactly are you running the installer headless. > Headless installer should at least warn when running on Java 7 > -------------------------------------------------------------- > > Key: JBDS-3463 > URL: https://issues.jboss.org/browse/JBDS-3463 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Affects Versions: 9.0.0.Beta1 > Reporter: Jan Richter > > While the GUI installer won't let you complete the installation without choosing Java 8 or higher, the headless installer doesn't care. > If you give it a config with path to Java 7, it will install everything and set Java 7 as -vm in jbdevstudio.ini. I think it should behave consistently with the GUI or at least warn that the Java I'm installing with is not supported anymore. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3463) Headless installer should at least warn when running on Java 7

by Jan Richter (JIRA)

Jan Richter created JBDS-3463: --------------------------------- Summary: Headless installer should at least warn when running on Java 7 Key: JBDS-3463 URL: https://issues.jboss.org/browse/JBDS-3463 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: installer Affects Versions: 9.0.0.Beta1 Reporter: Jan Richter While the GUI installer won't let you complete the installation without choosing Java 8 or higher, the headless installer doesn't care. If you give it a config with path to Java 7, it will install everything and set Java 7 as -vm in jbdevstudio.ini. I think it should behave consistently with the GUI or at least warn that the Java I'm installing with is not supported anymore. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20033) Standalone browsersim build produces two zip archives

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20033?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-20033: ------------------------------------------------ Sorry, I update the description with correct filenames. Yes, we should just ignore org.jboss.tools.browsersim-standalone-3.7.0-SNAPSHOT.zip, but it is interesting why this file actually appears > Standalone browsersim build produces two zip archives > ----------------------------------------------------- > > Key: JBIDE-20033 > URL: https://issues.jboss.org/browse/JBIDE-20033 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.3.0.Beta1 > Reporter: Konstantin Marmalyukov > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.3.0.CR1 > > > After local build of standalone browsersim I have jbosstools-4.3.0.Beta2-browsersim.zip and org.jboss.tools.browsersim-standalone-3.7.0-SNAPSHOT.zip. Both files has equal content. We don't need zip archive without standalone. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 June 2015