July 2015 - jbosstools-issues - Jboss List Archives

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

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBDS-3470?page=com.atlassian.jira.plugin.... ] Jiri Peterka updated JBDS-3470: ------------------------------- Attachment: wordpad-scaling.png > 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 > Attachments: jbds-after-scaling.png, wordpad-scaling.png > > > 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

[JBoss JIRA] (JBIDE-19990) "See JBoss Tools Visual Editor FAQ" link is not working.

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19990?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-19990: ------------------------------------ [~mlabuda] tried it on his system (Gnome, Fedora 19 I guess). His default system browser is Firefox and everything worked as expected. > "See JBoss Tools Visual Editor FAQ" link is not working. > -------------------------------------------------------- > > Key: JBIDE-19990 > URL: https://issues.jboss.org/browse/JBIDE-19990 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, visual-page-editor-core > Affects Versions: 4.3.0.Beta1 > Reporter: Radim Hopp > Assignee: Radim Hopp > Fix For: 4.3.0.Beta2 > > > When the browser cannot be instantiated, error is shown and on the bottom of the editor is "See JBoss Tools Visual Editor FAQ" link (see here: http://i.imgur.com/F2l9Hgi.png). > This link is not working. Clicking on it just writes into console, from where JBDS/JBT was started, this: > _env: /home/rhopp/http:/tools.jboss.org/documentation/faq/visualeditor.html: Directory or file does not exist_ -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19990) "See JBoss Tools Visual Editor FAQ" link is not working.

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19990?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-19990: ------------------------------------ I don't know how KDE (Plasma 5) handles default browser. In KDE settings I configured google-chrome as my default browser. Today, I'll try to persuade somebody with GNOME (or at least something else than KDE) to try it. > "See JBoss Tools Visual Editor FAQ" link is not working. > -------------------------------------------------------- > > Key: JBIDE-19990 > URL: https://issues.jboss.org/browse/JBIDE-19990 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, visual-page-editor-core > Affects Versions: 4.3.0.Beta1 > Reporter: Radim Hopp > Assignee: Radim Hopp > Fix For: 4.3.0.Beta2 > > > When the browser cannot be instantiated, error is shown and on the bottom of the editor is "See JBoss Tools Visual Editor FAQ" link (see here: http://i.imgur.com/F2l9Hgi.png). > This link is not working. Clicking on it just writes into console, from where JBDS/JBT was started, this: > _env: /home/rhopp/http:/tools.jboss.org/documentation/faq/visualeditor.html: Directory or file does not exist_ -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20095) openshift template does not warn/errror on required values

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20095?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20095: --------------------------------------------- a) yes - so we go get buyin from the writers. lets propose something for them. b) the UI shows which things it is about to create - why can't it remember that and offer to delete them ? (I guess that is #3) Deleting by labels is for me useful but completely separate from the UI around openshift template creationn. > openshift template does not warn/errror on required values > ---------------------------------------------------------- > > Key: JBIDE-20095 > URL: https://issues.jboss.org/browse/JBIDE-20095 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Jeff Cantrill > Fix For: 4.3.x > > > using https://github.com/jboss-openshift/application-templates/blob/master/eap/... (v1beta3) a lot of variables are shown, click next/next and all is created except build configs stating "values are required" > 1) why am I not warned *Before* starting to create things ? > 2) why cannot undo/delete the things that was created but now useless since buildconfig not created ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19757) Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19757?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19757: --------------------------------------------- JBIDE-20170 disagrees with you on the subject of the url not needing testing. And this url is not going to point to the *same* url all the time thus it needs testing. > Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery > -------------------------------------------------------------------------------------------- > > Key: JBIDE-19757 > URL: https://issues.jboss.org/browse/JBIDE-19757 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, server > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Minor > Labels: releasework > Fix For: 4.3.0.Beta1 > > > With https://bugs.eclipse.org/bugs/show_bug.cgi?id=434185 , WTP Server Discovery mechanism was granted a new strategy which allows to rely on regular p2 metadata instead of a site.xml. > Support for this was already merged in server ( https://github.com/jbosstools/jbosstools-server/commit/2d3cc63a9b67753ad9... ) > In order to save an artifact to manage (the webtools p2 repository), we could use this mechanism and consider contributing directly the main JBT URL to webtools discovery. > However, server discovery also keeps older strategies and since we produce invalid site.xml files, this is currently failing > {code} > !ENTRY org.eclipse.equinox.p2.updatesite 2 0 2015-05-04 09:40:58.088 > !MESSAGE Error parsing feature stream. The unique identifier or the version is null or empty for the State: "Category": unique identifier="minimal-json" version="null". > {code} > because we are lines specifying bundle but no version in the site.xml. > [~nickboldt] What are those site.xml useful for? Could we get rid of them? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) get TCF and RSE terminals to coexist without bad UX of multiple terminals

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-17686: ---------------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.Beta1) > get TCF and RSE terminals to coexist without bad UX of multiple terminals > ------------------------------------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Minor > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta2 > > Attachments: eclipse-can-has-many-consoles.png, org.jboss.tools.as.management.itests.AS7IntegrationTestSuite.txt > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) get TCF and RSE terminals to coexist without bad UX of multiple terminals

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17686: --------------------------------------------- So the important part noone mentioned is that TP for our Beta1 release was apparently RC2 and not RC3 nor RC4 as I thought was what was discussed in time up to the release. Stating if a user manually install RC1 or RC2 I did not read as "if user install the version of Mars provided by JBoss Tools Beta1 platform". Check for updates would *not* get this fix unless you include eclipse Mars R release into our release - which it is not. So yes this is beta2. > get TCF and RSE terminals to coexist without bad UX of multiple terminals > ------------------------------------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Minor > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta1 > > Attachments: eclipse-can-has-many-consoles.png, org.jboss.tools.as.management.itests.AS7IntegrationTestSuite.txt > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20148) releng scripts is an outdated version; jobs are not seeing latest from Nexus

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20148?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-20148: ---------------------------------------- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... reads: {code}[INFO] rsync -arzq --protocol=28 --del /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/fullSite/all/repo/* tools@filemgmt.jboss.org:/downloads_htdocs/tools/mars/snapshots/updates/core/master/{code} Isn't it what's expected? I can see the --del. > releng scripts is an outdated version; jobs are not seeing latest from Nexus > ---------------------------------------------------------------------------- > > Key: JBIDE-20148 > URL: https://issues.jboss.org/browse/JBIDE-20148 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Mickael Istria > Labels: needinfo, nexus > Fix For: 4.3.0.Beta2 > > > I've made some commits in the 4.3.x branch [0] of the build-ci repo, which should echo more details into the log. > [0] https://github.com/jbosstools/jbosstools-build-ci/commits/jbosstools-4.3.x > And the latest commits ARE built and available in Nexus [1], [2]: > [1] https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... [2] https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > Yet, no such output appears when the job is run, which makes me think that the -d and --del flags are NOT being passed to the script. > Here's a snippet from https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... : > {code} > + /qa/tools/opt/apache-maven-3.2.5//bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=/mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/.repository -B -U -fae -e -P hudson,unified.target,pack200,fetch-source-zips -Djbosstools_site_stream=master > ... > [INFO] --- exec-maven-plugin:1.3.2:exec (deploy-snapshot-updatesite) @ org.jboss.tools.site.core --- > ... > rsync -arzq --protocol=28 /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/repository/* tools@filemgmt.jboss.org:/downloads_htdocs/tools/mars/snapshots/updates/core/master/ > {code} > Yet when I run THE SAME SCRIPT from the workspace via shell, I get what I want: > {code} > + . /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/publish/rsync.sh -s /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/fullSite/all/repo -t mars/snapshots/updates/core/master --del > ... > [DEBUG] RSYNCFLAGS = --del > ... > [INFO] rsync -arzq --protocol=28 --del /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/fullSite/all/repo/* tools@filemgmt.jboss.org:/downloads_htdocs/tools/mars/snapshots/updates/core/master/ > ++ rsync -arzq --protocol=28 --del ... tools@filemgmt.jboss.org:/downloads_htdocs/tools/mars/snapshots/updates/core/master/ > {code} > So... what am I doing wrong? Why isn't the mojo using the latest version of the rsync script, but it's IN the workspace [3] ? > [3] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19178) Explorer: Add "Pipeline" view to OpenShift v3 explorer

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19178: --------------------------------------------- The properties view can contain arbitrary complex UI, so why not put something like this in there ? Also we are not limited to a tree in main UI, but we are limited in the way that it does not make sense to use majority of the screen to show this in an IDE where this info is secondary not the primary thing. logical/pipeline view ? not sure what it would contain - but again the properties view can have tabs that shows different things for a selection ? > Explorer: Add "Pipeline" view to OpenShift v3 explorer > ------------------------------------------------------ > > Key: JBIDE-19178 > URL: https://issues.jboss.org/browse/JBIDE-19178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.0.CR1 > > Attachments: Console of 'App' with the pieces wired.png, Pipeline view mockup.bmml, Pipeline view mockup.png > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- 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 Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3470?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3470: ------------------------------------------- Are you saying other desktop bitmap icons scale in this situation ? Wouldn't expect that unless vector icons are used ? > 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 > Attachments: jbds-after-scaling.png > > > 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 July 2015