May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22278) Explorer: should be made visible when a new Connection is created

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22278?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22278: ------------------------------------- Labels: connection_wizard explorer openshift_v3 (was: ) > Explorer: should be made visible when a new Connection is created > ----------------------------------------------------------------- > > Key: JBIDE-22278 > URL: https://issues.jboss.org/browse/JBIDE-22278 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Fred Bricon > Labels: connection_wizard, explorer, openshift_v3 > Fix For: 4.4.x > > > OpenShift Explorer should be made visible when a new Connection is created. This is particularly useful when the CDK Server creates an OpenShift Connection and the OpenShift Explorer is not visible. > Could be done through a connection listener in the UI activator -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3849) Store downloaded requirements for bundled installer between builds

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3849?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3849. ----------------------------- Closing as finished. > Store downloaded requirements for bundled installer between builds > ------------------------------------------------------------------ > > Key: JBDS-3849 > URL: https://issues.jboss.org/browse/JBDS-3849 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha1 > > Attachments: jbds-jar-0-length-in-7zip.png, works-but-too-small.png > > > Now build downloads all bundled binaries in every build, because the got wiped out by clean task. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3854) Installer: Gulp dist task doesn't report subtasks in correct order

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3854?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3854. ----------------------------- Verified with latest master (equivalent of B141) > Installer: Gulp dist task doesn't report subtasks in correct order > ------------------------------------------------------------------ > > Key: JBDS-3854 > URL: https://issues.jboss.org/browse/JBDS-3854 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Pitonak > Assignee: Pavol Pitonak > Labels: Havoc > Fix For: 10.0.0.Alpha1 > > > Gulp task _dist_ log is in wrong order, e.g. dist should finish after clean is finished (caused by mixed usage of runSequence and native Gulp dependent tasks) > {code} > [11:40:03] Using gulpfile ~/workspace/developer-platform-install/gulpfile.js > [11:40:03] Starting 'check-requirements'... > [11:40:05] Finished 'check-requirements' after 1.74 s > [11:40:05] Starting 'dist'... > [11:40:05] Starting 'clean'... > [11:40:05] Finished 'dist' after 3.05 ms > [11:40:05] Finished 'clean' after 4.52 ms > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3593) Enable continuous delivery

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3593?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3593: -------------------------------------- {quote}So right now, the job you created is just a wrapper for jbosstools-install-grinder.install-tests.matrix_master. Could you add more jobs to it?{quote} That's the goal. This is meant to run any automated test we have to decide when something is good to stage or release. The verifications for "ready to stage into prod" are those performed by QE (there are probably some we can automate). The verifications for "ready to stage snapshots" are still unclear to me. Actually, identifying and automating the necessary verifications is the whole purpose of this Jira. > Enable continuous delivery > -------------------------- > > Key: JBDS-3593 > URL: https://issues.jboss.org/browse/JBDS-3593 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Enhancement > Components: build > Affects Versions: 10.0.0.Alpha1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.x > > > A continuous delivery build is about setting up the necessary checks to make sure that a "snapshot" is in a good enough state to be released (from a releng perspective). > If we have this, then it means that planning can be changed to whatever strategy; without requiring any specific effort to adapt. > I bootstrapped a CI job to start "hosting" all those quality checks: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3593) Enable continuous delivery

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3593?page=com.atlassian.jira.plugin.... ] Mickael Istria updated JBDS-3593: --------------------------------- Priority: Major (was: Blocker) > Enable continuous delivery > -------------------------- > > Key: JBDS-3593 > URL: https://issues.jboss.org/browse/JBDS-3593 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Enhancement > Components: build > Affects Versions: 10.0.0.Alpha1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.x > > > A continuous delivery build is about setting up the necessary checks to make sure that a "snapshot" is in a good enough state to be released (from a releng perspective). > If we have this, then it means that planning can be changed to whatever strategy; without requiring any specific effort to adapt. > I bootstrapped a CI job to start "hosting" all those quality checks: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22291) Deploy Docker Wizard: Add connection info

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-22291: ------------------------------------- Summary: Deploy Docker Wizard: Add connection info Key: JBIDE-22291 URL: https://issues.jboss.org/browse/JBIDE-22291 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.4.0.Alpha1 Reporter: Marián Labuda When deploying from a context menu of a docker image from Docker Explorer and an OpenShift 3 connection/project is preselected, wizard use this connection and allow to set a specific project for deployment. Problem is that I don't see a connection where I am deploying. It is nice to know that it is selected connection/project from OpenShift explorer but it would be nice to have a combo box with preselected connection there or connection info in some way to be fully aware of what I am doing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22291) Deploy Docker Wizard: Add connection info

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22291?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22291: ---------------------------------- Labels: docker openshift_v3 (was: ) > Deploy Docker Wizard: Add connection info > ----------------------------------------- > > Key: JBIDE-22291 > URL: https://issues.jboss.org/browse/JBIDE-22291 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: docker, openshift_v3 > > When deploying from a context menu of a docker image from Docker Explorer and an OpenShift 3 connection/project is preselected, wizard use this connection and allow to set a specific project for deployment. Problem is that I don't see a connection where I am deploying. It is nice to know that it is selected connection/project from OpenShift explorer but it would be nice to have a combo box with preselected connection there or connection info in some way to be fully aware of what I am doing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22224) Prompt to confirm credentials is shown every time I want to deploy a docker image from Docker Explorer

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22224?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22224. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > Prompt to confirm credentials is shown every time I want to deploy a docker image from Docker Explorer > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-22224 > URL: https://issues.jboss.org/browse/JBIDE-22224 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: docker, openshift_v3, ux > Fix For: 4.4.0.Alpha1 > > > When I am trying to deploy a docker image via context menu of a docker image in Docker Explorer, I am prompted every time to confirm Connection dialog, although I have an established connection in OpenShift Explorer view. It's pretty annoying. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22288) VPE crashes studio with JRE fatal error on Fedora 23

by Wayne McDermott (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22288?page=com.atlassian.jira.plugi... ] Wayne McDermott commented on JBIDE-22288: ----------------------------------------- I had not originally performed step 2 in the new VM. I have just done that (dnf install webkitgtk) but the behavior is the same. After being given the option of changing to JSF studio crashes. > VPE crashes studio with JRE fatal error on Fedora 23 > ---------------------------------------------------- > > Key: JBIDE-22288 > URL: https://issues.jboss.org/browse/JBIDE-22288 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.3.1.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: hs_err_pid2276.log.zip > > > Using VPE on Fedora ends up Studio crash > Works fine on Windows 10, Ubuntu 16.04 > More details can be found here - https://developer.jboss.org/message/955490 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22232) New OpenShift Application wizard: Make selection of an OS project in application wizard consistent

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22232?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22232. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > New OpenShift Application wizard: Make selection of an OS project in application wizard consistent > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-22232 > URL: https://issues.jboss.org/browse/JBIDE-22232 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: application_wizard > Fix For: 4.4.0.Alpha1 > > > When opening a New OpenShift Application wizard from context menu of a connection or via central or via shell menu File - New - OpenShift Application, the selected OpenShift project in the wizard is random (e.g. having several project aaa, bbb, ccc, ddd, eee1, eee2, eee3 the order of projects was following eee1 aaa bbb bbb bbb ccc eee1 aaa bbb). We could preselect a first project to have it consistent. > steps to reproduce: > # ASSERT: make sure that you have several OpenShift projects > # EXEC: launch application wizard > Result: > The project that is pre-selected in the wizard is not consistent. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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