September 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-20544) For OpenShift v3, since a default server does not exist, we should remove the default server check box

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20544?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-20544: --------------------------------- Attachment: OSE3.png > For OpenShift v3, since a default server does not exist, we should remove the default server check box > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20544 > URL: https://issues.jboss.org/browse/JBIDE-20544 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Len DiMaggio > Priority: Minor > Attachments: OSE3.png > > > See attached screenshot. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20543) Show pod status instead of labels

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-20543: ------------------------------------- Summary: Show pod status instead of labels Key: JBIDE-20543 URL: https://issues.jboss.org/browse/JBIDE-20543 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.3.0.CR1 Reporter: Jeff Cantrill the pod status is more interesting to a user then labels, which are viewable as properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20542) Allow a user to add environment variables in deploy image wizard

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-20542: ------------------------------------- Summary: Allow a user to add environment variables in deploy image wizard Key: JBIDE-20542 URL: https://issues.jboss.org/browse/JBIDE-20542 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.3.0.CR1 Reporter: Jeff Cantrill -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 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 Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20100?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20100: --------------------------------------------- [~ldimaggio] I don't think such rules can be made. But Feel free to open another jira or mail thread on it is separate from this issue IMO. > 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 > Assignee: Mickael Istria > Fix For: 4.3.0.CR1 > > Attachments: JBIDE-20100-2.png > > > [~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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20195) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Aerogear]

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20195?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov resolved JBIDE-20195. -------------------------------------------- Resolution: Done > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Aerogear] > ------------------------------------------------------------------------------------ > > Key: JBIDE-20195 > URL: https://issues.jboss.org/browse/JBIDE-20195 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid, cordovasim > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta2 > > > For JBIDE 4.3.0.CR1 [Aerogear]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 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 Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20100?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-20100: -------------------------------------- Can we summarize the "rules" that we will impose/follow in a form suitable to show to users? If an EA runtime is installed, only EA versions of connectors will be visible, etc. > 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 > Assignee: Mickael Istria > Fix For: 4.3.0.CR1 > > Attachments: JBIDE-20100-2.png > > > [~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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19948) Reimplement Eclipse Download plugin to allow dynamic work flow

by David Hladky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19948?page=com.atlassian.jira.plugi... ] David Hladky commented on JBIDE-19948: -------------------------------------- I do not think it is "complex". The workflow is usually select one value from drop down or check a check box and click next. I would say such behaviour is far from complex. We wanted the user to have a nice experience. Opening a web browser, forcing the user to login in it in order to check one checkbox, then login in Eclipse again is bad user experience IMO. > Reimplement Eclipse Download plugin to allow dynamic work flow > -------------------------------------------------------------- > > Key: JBIDE-19948 > URL: https://issues.jboss.org/browse/JBIDE-19948 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection, server > Affects Versions: 4.3.0.Alpha2 > Reporter: David Hladky > Assignee: Rob Stryker > Fix For: 4.3.0.CR1 > > > We need to reimplement the plugin to accept new terms and conditions models as well as follow the workflow changes in case of changes to the current ones. > Under this issue I will create the tasks we need to achieve this goal. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20209) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [BrowserSim]

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20209?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov resolved JBIDE-20209. -------------------------------------------- Resolution: Done > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [BrowserSim] > -------------------------------------------------------------------------------------- > > Key: JBIDE-20209 > URL: https://issues.jboss.org/browse/JBIDE-20209 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: browsersim > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta2 > > > For JBIDE 4.3.0.CR1 [BrowserSim]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for BrowserSim task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20524) Opening xhtml with VPE ends up with the eclipse crash (Mars 4.5.0)

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20524?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-20524: ------------------------------------- PR was sent - https://github.com/jbosstools/jbosstools-vpe/pull/323 I believe PR for FAQ can be closed, cause now this issue will not be reproducible > Opening xhtml with VPE ends up with the eclipse crash (Mars 4.5.0) > ------------------------------------------------------------------ > > Key: JBIDE-20524 > URL: https://issues.jboss.org/browse/JBIDE-20524 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream, visual-page-editor-core, xulrunner > Affects Versions: 4.3.0.Beta2 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Blocker > Labels: upstream > Fix For: 4.3.0.CR1 > > > Upstream regression Mars 4.5.0 XULRunner [Bug 472956|https://bugs.eclipse.org/bugs/show_bug.cgi?id=472956] > Basically, XULRunner crashes when profile path does not exist. The workaround is to create profile folder `C:\Users\<USER_NAME>\AppData\Roaming\Mozilla\eclipse` manually. More details can be found in the reply to the original upstream issue and in the related developer.jboss.org discussion - https://developer.jboss.org/message/938755 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19948) Reimplement Eclipse Download plugin to allow dynamic work flow

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19948?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-19948: -------------------------------------- +1 to Max's comment - what is forcing this to be so complex? > Reimplement Eclipse Download plugin to allow dynamic work flow > -------------------------------------------------------------- > > Key: JBIDE-19948 > URL: https://issues.jboss.org/browse/JBIDE-19948 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection, server > Affects Versions: 4.3.0.Alpha2 > Reporter: David Hladky > Assignee: Rob Stryker > Fix For: 4.3.0.CR1 > > > We need to reimplement the plugin to accept new terms and conditions models as well as follow the workflow changes in case of changes to the current ones. > Under this issue I will create the tasks we need to achieve this goal. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

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