June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19335) org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeLicenseFragment fails with SWTError without browser available

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19335?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19335: ------------------------------------- > new inconsistent property introduced I commented that the property does not seem inconsistent. All it does is suppress browser creation. I don't see how it's "inconsistent" in any way. Inconsistent with what? It seems to me to be a clearly internal detail / sysprop used for testing. > mixed in license text with generic browser packages. Looking at the BrowserUtility in master, and in fact all files in org.jboss.tools.foundation.ui.util, I do not see any reference to license at all. Not in BrowserUtility, not in BrowserUtilityMessages.java, or .properties. I don't know what you mean by this. > no tests I'm honestly really not sure how to go about testing this API. Who are our experts at testing UI API? I'm really not familiar with it at all. Should I be opening new shells and custom dialog boxes in my test case? > org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeLicenseFragment fails with SWTError without browser available > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19335 > URL: https://issues.jboss.org/browse/JBIDE-19335 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core, runtime-detection > Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1 > Environment: Linux > Reporter: Denis Golovin > Assignee: Rob Stryker > Fix For: 4.3.0.Beta2 > > > DownloadRuntimeLicenseFragment should work even without browser widget available and show html or text without html tags with <p> and <br> elements replaced with '\n'. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20054) Connection wizard: Cannot remove secure storage of v3 connection token

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20054?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-20054: ---------------------------------- Priority: Minor (was: Critical) > Connection wizard: Cannot remove secure storage of v3 connection token > ---------------------------------------------------------------------- > > Key: JBIDE-20054 > URL: https://issues.jboss.org/browse/JBIDE-20054 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Minor > Labels: openshift_v3 > Fix For: 4.3.0.Beta2 > > > If I create a new v3 connection with OAuth authentization method and choose to store token in secure storage (or I edit the existing one connection with token and check the checkbox to store the token in secure storage), token is stored. But if I decide later to prevent it to being stored by unchecking the checkbox in Edit connection dialog, it does not work. If I uncheck the checbox and hit the Finish button and come back to edit connection dialog, the checkbox is still checked. This is related only to OAuth authentization method (basic authentization method works as expected). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11436) we should use license features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11436?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-11436 at 6/29/15 11:28 AM: -------------------------------------------------------------- Here's an example PR showing how we could adopt the license feature into a project like Freemarker: https://github.com/jbosstools/jbosstools-freemarker/pull/36 (cc: [~snjeza] do not apply this yet!!!) Need to also see if we can remove the license.html and license details from feature.properties. But at least this PR builds OK after building https://github.com/jbosstools/jbosstools-base/pull/420 locally. was (Author: nickboldt): Here's an example PR showing how we could adopt the license feature into a project like Freemarker: https://github.com/jbosstools/jbosstools-freemarker/pull/36 (cc: [~snjeza] do not apply this yet!!!) Need to also see if we can remove the license.html and license details from feature.properties. But at least this PR builds OK. > we should use license features > ------------------------------ > > Key: JBIDE-11436 > URL: https://issues.jboss.org/browse/JBIDE-11436 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Beta2 > > > See http://relengofthenerds.blogspot.fr/2011/01/implementing-shared-licenses-... for explanation -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20162) Rename FeedHenry references to RHMAP

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20162?page=com.atlassian.jira.plugi... ] Gorkem Ercan edited comment on JBIDE-20162 at 6/29/15 11:26 AM: ---------------------------------------------------------------- Perhaps at a later release because for JBDS 9, feedhenry open source is just a web site. was (Author: gercan): Perhaps at a later release because for JBDS 9 feedhenry open source is just a web site. > Rename FeedHenry references to RHMAP > ------------------------------------ > > Key: JBIDE-20162 > URL: https://issues.jboss.org/browse/JBIDE-20162 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > > Feedhenry is now called Red Hat Mobile Application Platform adjust branding accordingly -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20162) Rename FeedHenry references to RHMAP

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20162?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-20162: -------------------------------------- Perhaps at a later release because for JBDS 9 feedhenry open source is just a web site. > Rename FeedHenry references to RHMAP > ------------------------------------ > > Key: JBIDE-20162 > URL: https://issues.jboss.org/browse/JBIDE-20162 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > > Feedhenry is now called Red Hat Mobile Application Platform adjust branding accordingly -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20141) Define which vanity URLs to use for publishing JBT/JBDS nightlies & dev sites

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20141?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20141: --------------------------------------------- no, /updates/snapshots works too. I'm arguing that we in just a week seen cases of where having the *public* urls be separate from the internal schemas are helpful. i.e. it shields us from any changes from branch to master moves and allow to have browsable directory content for the internal ones, but keep nice simple html page for the public ones. > Define which vanity URLs to use for publishing JBT/JBDS nightlies & dev sites > ----------------------------------------------------------------------------- > > Key: JBIDE-20141 > URL: https://issues.jboss.org/browse/JBIDE-20141 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta2 > > > Today, we produce a lot of artifacts w/ every CI (snapshot), staging, development, & stable build. > But sometimes, finding these artifacts can be a daunting task. > Below are some URLs where things can be found. > *CI builds / SNAPSHOTS / nightlies* > * http://download.jboss.org/jbosstools/updates/nightly/master/ -> ../../mars/snapshots/builds/jbosstools-discovery.central_master/latest/all/repo/ (composite of Core + Central, *OLD URL PATTERN*) > * http://download.jboss.org/jbosstools/updates/nightly/mars -> ../../mars/snapshots/builds/jbosstools-discovery.central_master/latest/all/repo/ (composite of Core + Central, *OLD URL PATTERN*) > * http://download.jboss.org/jbosstools/mars/nightly/updates/ -> ../../mars/snapshots/builds/jbosstools-discovery.central_master/latest/all/repo/ (composite of Core + Central) > * http://download.jboss.org/jbosstools/mars/snapshots/updates/ (individual projects' update sites) > ** http://download.jboss.org/jbosstools/mars/snapshots/updates/core/master/ > ** http://download.jboss.org/jbosstools/mars/snapshots/updates/core/4.3.mars/ > ** http://download.jboss.org/jbosstools/mars/snapshots/updates/webtools/master/ > ** http://download.jboss.org/jbosstools/mars/snapshots/updates/webtools/4.3.... > ** .. > * http://download.jboss.org/jbosstools/mars/snapshots/builds/ (individual timestamped CI builds) > *Staging Sites* > * http://download.jboss.org/jbosstools/mars/staging/builds/ > * http://download.jboss.org/jbosstools/mars/staging/updates/ > *Development Milestones* > * http://download.jboss.org/jbosstools/updates/development/mars/ -> ../../mars/development/updates/ (*OLD URL PATTERN*) > * http://download.jboss.org/jbosstools/mars/development/updates/ (composites & content that isn't *static*) > * http://download.jboss.org/jbosstools/static/mars/development/updates/ (actual update sites, moved here for Akamai performance) > ---- > For JBDS, we follow the same pattern as above but use https://devstudio.redhat.com/9.0/ instead of http://download.jboss.org/jbosstools/mars/ ... but we also have a /builds/installer/ folder because the public JBDS site now includes the standalone installer: > * https://devstudio.redhat.com/9.0/development/builds/installer/ > Also, for JBDS we don't have to differentiate between /static/ and non-static content, since Akamai set up the entire server to be mirrored to their servers. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-3427) Undo (Ctrl+Z) doesn't work correctly for comments

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3427?page=com.atlassian.jira.plugin... ] Konstantin Marmalyukov resolved JBIDE-3427. ------------------------------------------- Resolution: Done upstreams are fixed > Undo (Ctrl+Z) doesn't work correctly for comments > ------------------------------------------------- > > Key: JBIDE-3427 > URL: https://issues.jboss.org/browse/JBIDE-3427 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 3.0.0.cr1 > Reporter: Yura Zhishko > Assignee: Konstantin Marmalyukov > Fix For: LATER > > > 1) Choose any tag or text > 2) Choose Source -> Toggle Comment (or press Ctrl+Shift+C) > ASSERT: Line is commented > 3) Make Undo (Ctrl+Z) > ASSERT: This action delete only the end of tag (-->) > 4) Make Undo (Ctrl+Z) again > ASSERT: Delete start tag ( appeared around existed comments -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11436) we should use license features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11436?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-11436: ------------------------------------ Here's an example PR showing how we could adopt the license feature into a project like Freemarker: https://github.com/jbosstools/jbosstools-freemarker/pull/36 (cc: [~snjeza] do not apply this yet!!!) Need to also see if we can remove the license.html and license details from feature.properties. But at least this PR builds OK. > we should use license features > ------------------------------ > > Key: JBIDE-11436 > URL: https://issues.jboss.org/browse/JBIDE-11436 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Beta2 > > > See http://relengofthenerds.blogspot.fr/2011/01/implementing-shared-licenses-... for explanation -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20162) Rename FeedHenry references to RHMAP

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20162?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20162: --------------------------------------------- okey, so it is still feedhenry the tool support, and Red Hat Mobile Application Platform is a specific instance of this. > Rename FeedHenry references to RHMAP > ------------------------------------ > > Key: JBIDE-20162 > URL: https://issues.jboss.org/browse/JBIDE-20162 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > > Feedhenry is now called Red Hat Mobile Application Platform adjust branding accordingly -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3470) Toolbars + Icons unusable on high resolution screens

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/JBDS-3470?page=com.atlassian.jira.plugin.... ] Mustafa Musaji commented on JBDS-3470: -------------------------------------- Ideally 4k which I believe is the highest on the market now? > Toolbars + Icons unusable on high resolution screens > ---------------------------------------------------- > > Key: JBDS-3470 > URL: https://issues.jboss.org/browse/JBDS-3470 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: ui/branding > Affects Versions: 9.0.0.Beta1 > Environment: Windows + UHD screens > Reporter: Mustafa Musaji > > When using JBDS on UHD screen the toolbar is unusable due to it not being resized and too small to use properly. > Upstream: https://bugs.eclipse.org/bugs/show_bug.cgi?id=382972 > I'm raising this for QE to ensure we test this in the next release as it was fixed upstream. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

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