June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3460) Line numbers should be shown in text editors by default

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3460?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-3460. --------------------------------- Resolution: Done released to master. > Line numbers should be shown in text editors by default > ------------------------------------------------------- > > Key: JBDS-3460 > URL: https://issues.jboss.org/browse/JBDS-3460 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: build, installer > Affects Versions: 9.0.0.Beta1 > Reporter: Marián Labuda > Assignee: Denis Golovin > Fix For: 9.0.0.Beta2 > > > Eclipse use by default shown line numbers for text editors (e.g. Java classes). But our developer studio has line numbers hidden by default. I remember there was some questionnarie some time ago but unfortunately I do not remember results from it. -- 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 Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBDS-3470?page=com.atlassian.jira.plugin.... ] Jiri Peterka commented on JBDS-3470: ------------------------------------ It's reproducible with scaling on Windows 8.1, see the screenshot with remote desktop. Icons, toolbars and other images don't scale. > 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

[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: jbds-after-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 > > > 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-20168) create buildinfo.json files for old project builds which predate buildinfo.json generator

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20168?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20168: ------------------------------------ I have created two buildinfo.json files: http://download.jboss.org/jbosstools/updates/stable/luna/core/portlet/bui... http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2... https://github.com/jbosstools/jbosstools-download.jboss.org/commit/4fecba... https://github.com/jbosstools/jbosstools-download.jboss.org/commit/b907df... Rebuilding: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... >=10215 > create buildinfo.json files for old project builds which predate buildinfo.json generator > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20168 > URL: https://issues.jboss.org/browse/JBIDE-20168 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta2 > > > Max asked: > {quote} > i'm asking what shah's was used in the build for these components. > No sure if you are trolling me by us keeping having these conversations everytime we need to tag :) > Checking jbosstools-portlet the latest 4.3.0 tags are same as master but the link above you are pointing to Luna so that can't be right. > and jbosstools-xulrunner seem to have very little tags at all - so again; which tag/sha1 of these was put into our release so we can actually know what source is actually included ? > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19817) Application wizard: v3 application wizard needs to be able to react to changing connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19817?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-19817: ---------------------------------------- Assignee: Andre Dietisheim (was: Jeff Cantrill) > Application wizard: v3 application wizard needs to be able to react to changing connections > ------------------------------------------------------------------------------------------- > > Key: JBIDE-19817 > URL: https://issues.jboss.org/browse/JBIDE-19817 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Labels: openshift_v3 > Fix For: 4.3.0.Beta2 > > > The current application wizard for OpenShift v3 takes a project in the constructor. It was designed to be launched from the explorer where a v3 connection/project is selected before the wizard is launched. The wizard is not able to react to changing connections. In order for the wizard to be able to get launched from File->New->OpenShift we need the wizard to be able to react to chaning connections. -- 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 edited comment on JBIDE-20148 at 6/30/15 12:11 PM: ------------------------------------------------------------------ Log says {quote}[INFO] jbosstools-releng-publish-4.3.0.Beta2-SNAPSHOT.zip already unpacked.{quote} So I believe we have to put a "-DoverWrite=true" flag to the command fetching the zip. Also, the "unpack" Maven command is using the common m2 repo, not the private one for the job, which can drives to some confusion. was (Author: mickael_istria): Log says {quote}[INFO] jbosstools-releng-publish-4.3.0.Beta2-SNAPSHOT.zip already unpacked.{quote} So I believe we have to put a "-DoverWrite=true" flag to the command fetching the zip. > 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-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: ---------------------------------------- Log says {quote}[INFO] jbosstools-releng-publish-4.3.0.Beta2-SNAPSHOT.zip already unpacked.{quote} So I believe we have to put a "-DoverWrite=true" flag to the command fetching the zip. > 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-20163) Application wizard: Resource summary after create new app not displaying errors correctly

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20163?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20163: ------------------------------------- Labels: application_wizard openshift_v3 (was: ) > Application wizard: Resource summary after create new app not displaying errors correctly > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20163 > URL: https://issues.jboss.org/browse/JBIDE-20163 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.3.0.Beta2 > > > Create a new application. > Delete a resource > Create the same application > Note: The error icon and text info displays as green(success) with an improper label -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20163) Application wizard: Resource summary after create new app not displaying errors correctly

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20163?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20163: ------------------------------------- Description: Steps: # Create a new application. # Delete a resource # Create the same application Result: The error icon and text info displays as green(success) with an improper label was: Create a new application. Delete a resource Create the same application Note: The error icon and text info displays as green(success) with an improper label > Application wizard: Resource summary after create new app not displaying errors correctly > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20163 > URL: https://issues.jboss.org/browse/JBIDE-20163 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.3.0.Beta2 > > > Steps: > # Create a new application. > # Delete a resource > # Create the same application > Result: > The error icon and text info displays as green(success) with an improper label -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20163) Resource summary after create new app not displaying errors correctly

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20163?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20163: ------------------------------------------ easy simple fix, +1, have a go. Thanks! > Resource summary after create new app not displaying errors correctly > --------------------------------------------------------------------- > > Key: JBIDE-20163 > URL: https://issues.jboss.org/browse/JBIDE-20163 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Minor > Fix For: 4.3.0.Beta2 > > > Create a new application. > Delete a resource > Create the same application > Note: The error icon and text info displays as green(success) with an improper label -- 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