September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-22994) Remove old Help->Report Problem dialog

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22994?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22994: ----------------------------------- Labels: (was: new_and_noteworthy) > Remove old Help->Report Problem dialog > -------------------------------------- > > Key: JBIDE-22994 > URL: https://issues.jboss.org/browse/JBIDE-22994 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aeri, common/jst/core, jsf, visual-page-editor-core > Reporter: Denis Golovin > Assignee: Dmitrii Bocharov > Priority: Blocker > Fix For: 4.4.2.AM1 > > Attachments: screenshot-1.png > > > Should we deprecate delete old Report Problem dialog with aeri enabled? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ERT-420) Open or ping failure for connection causes exception to be logged [EBZ#501522]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-420?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston reassigned ERT-420: --------------------------------- Assignee: Jeff Johnston > Open or ping failure for connection causes exception to be logged [EBZ#501522] > ------------------------------------------------------------------------------ > > Key: ERT-420 > URL: https://issues.jboss.org/browse/ERT-420 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: 5.2.0, Docker, bzira > Fix For: Neon.2 (4.6) > > > An open or ping failure for a closed/invalid connection causes an exception trace to be logged. This will cause an AERI bug filed and offers little information to an end-user. It is better to give an information message that the open or ping failed for the particular connection. The connection is shown as greyed and invalid. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ERT-420) Open or ping failure for connection causes exception to be logged [EBZ#501522]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-420?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston updated ERT-420: ------------------------------ Sprint: devex #120 September 2016 > Open or ping failure for connection causes exception to be logged [EBZ#501522] > ------------------------------------------------------------------------------ > > Key: ERT-420 > URL: https://issues.jboss.org/browse/ERT-420 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Labels: 5.2.0, Docker, bzira > Fix For: Neon.2 (4.6) > > > An open or ping failure for a closed/invalid connection causes an exception trace to be logged. This will cause an AERI bug filed and offers little information to an end-user. It is better to give an information message that the open or ping failed for the particular connection. The connection is shown as greyed and invalid. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23210) Application wizard: builder image application are created all the time for first project

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23210?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-23210: ----------------------------------------------- That is what happens here: NewApplicationWizard.init(workbench, selection) does two calls (1) setConnection(connection); (2) model.setProject(resource.getProject()); While the first call is performed, on event from the change of connection, method DeployImageWizardModel.initModel(connection, project, loadResources) is called with project = null, because the call (2) is not yet done. Method initModel starts job "Loading projects..." which is to set projects and select default project. Now, we have the race of job and main thread. Main usually wins, makes its call (2), after which job sets default project to DeployImageWizardModel which is not synchronized with project instance in NewApplicationWizardModel. So, user sees correctly selected project in combo, taken from NewApplicationWizardModel, while DeployImageWizardModel inconspicuously holds wrong default project. > Application wizard: builder image application are created all the time for first project > ---------------------------------------------------------------------------------------- > > Key: JBIDE-23210 > URL: https://issues.jboss.org/browse/JBIDE-23210 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Environment: # openshift version > openshift v3.2.1.15 > kubernetes v1.2.0-36-g4a3f9c5 > etcd 2.2.5 > Reporter: Peng Li > Labels: application_wizard, openshift_v3 > Attachments: Screenshot from 2016-09-22 15-58-02.png, Screenshot from 2016-09-22 16-00-12.png > > > Creation of an application based on builder image ignore preselected project and is created on first project all the time. This is happening only for builder images. Template based application are not affected by this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22305) automate process for fetching latest target platform mirrors

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22305?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22305: ------------------------------- Fix Version/s: 4.4.2.AM2 (was: 4.4.x) > automate process for fetching latest target platform mirrors > ------------------------------------------------------------ > > Key: JBIDE-22305 > URL: https://issues.jboss.org/browse/JBIDE-22305 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, updatesite, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.4.2.AM2 > > Attachments: git.diff.txt > > > Rather than manually pulling requirements, it would be hella sweet if there was a job config into which we could just list all the URLs to mirror and their matching project names. > Then this job would scrape the *.target files for the current list of URLs used, grep out the /requirements/<reqname>/<version>, fetch a new mirror for each new version*, and dump an updated copy of the .target file into the job's workspace. > Thus for webtools we might simply define: > webtools,S-3.8.0M7-20160503010110,http://download.eclipse.org/webtools/do... > and we'd end up with: > http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.8.... > * Since we already have a http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... job we can just pass parameters to that to invoke the mirroring steps. Would be even better if we could run multiple calls in parallel as neon and wtp can take >2hr > 1. matrix job. each config is a trio of reqname/version/URL which is passed to a process akin to that of the jbosstools-requirements job to perform the mirror; process is now scripted here: https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/p... > 2. when all children are done, a downstream job can runs TP update & validation against new .target files > * fetch http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf... > * parse that into a list of URLs > * each URL contains REQ_NAME/VERSION, which can then be matched up with similar lines in .target files > * run p2diff between old/new URLs in .target to generate list of changes and verify new site contains all the same IUs > * resulting edited .target files will remain in the workspace, and we can then run > * https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u... > * when done if success: > * ideally, generate a PR and attach link in email to jbosstools-dev@ > * if can't generate PR, then attach patch in email to nickboldt & mistria to apply locally in jbosstools-target-platforms to create a PR > * email should includes boilerplate text to send mail to list announcing new change for review -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23157) rename component "common/jst/core" to "base" or "foundation" or add new components

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23157?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23157: ------------------------------------ Could we fix this for AM2? As long as we agree on the plan, I can fix the scripts in build-ci and in jiralint, and the JIRA components. > rename component "common/jst/core" to "base" or "foundation" or add new components > ---------------------------------------------------------------------------------- > > Key: JBIDE-23157 > URL: https://issues.jboss.org/browse/JBIDE-23157 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, runtime-detection > Affects Versions: 4.4.2.AM1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.4.x > > > The closest thing to a "Base" component, or a "Foundation" component (eg., when reporting issues like JBIDE-23156) is "common/jst/core" which is nothing like "Base" or "Foundation". > We should either fix that component, or add new one(s). > This will impact *.py scripts in jbosstools-build-ci. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23157) rename component "common/jst/core" to "base" or "foundation" or add new components

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23157?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-23157: ----------------------------------- Fix Version/s: 4.4.x (was: 4.4.2.AM1) > rename component "common/jst/core" to "base" or "foundation" or add new components > ---------------------------------------------------------------------------------- > > Key: JBIDE-23157 > URL: https://issues.jboss.org/browse/JBIDE-23157 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, runtime-detection > Affects Versions: 4.4.2.AM1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.4.x > > > The closest thing to a "Base" component, or a "Foundation" component (eg., when reporting issues like JBIDE-23156) is "common/jst/core" which is nothing like "Base" or "Foundation". > We should either fix that component, or add new one(s). > This will impact *.py scripts in jbosstools-build-ci. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22768) [THYM] Can not retrieve plugin catalog

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22768?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-22768: -------------------------------------- Assignee: Gorkem Ercan > [THYM] Can not retrieve plugin catalog > -------------------------------------- > > Key: JBIDE-22768 > URL: https://issues.jboss.org/browse/JBIDE-22768 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, upstream > Affects Versions: 4.4.1.AM2 > Reporter: Pavol Srna > Assignee: Gorkem Ercan > Fix For: 4.4.x > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22768) [THYM] Can not retrieve plugin catalog

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22768?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22768: ----------------------------------- Fix Version/s: 4.4.x (was: 4.4.2.AM1) > [THYM] Can not retrieve plugin catalog > -------------------------------------- > > Key: JBIDE-22768 > URL: https://issues.jboss.org/browse/JBIDE-22768 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, upstream > Affects Versions: 4.4.1.AM2 > Reporter: Pavol Srna > Fix For: 4.4.x > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22699) BrowserUtilTest.testCreateBrowser failure

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22699?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22699: ----------------------------------- Fix Version/s: 4.4.x (was: 4.4.2.AM1) > BrowserUtilTest.testCreateBrowser failure > ----------------------------------------- > > Key: JBIDE-22699 > URL: https://issues.jboss.org/browse/JBIDE-22699 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.4.1.AM1 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.4.x > > > org.jboss.tools.foundation.ui.test.BrowserUtilTest.testCreateBrowser > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertNotNull(Assert.java:712) > at org.junit.Assert.assertNotNull(Assert.java:722) > at org.jboss.tools.foundation.ui.test.BrowserUtilTest.testCreateBrowser(BrowserUtilTest.java:32) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 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 2016