February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21593) Application wizard: Opening wizard and creating required project (clean connection) makes wizard unusable

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21593?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21593: ------------------------------------- Can't reproduce either. Since it appears randomly and there's an easy workaround, I've changed the fixVersion to 4.4.x > Application wizard: Opening wizard and creating required project (clean connection) makes wizard unusable > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21593 > URL: https://issues.jboss.org/browse/JBIDE-21593 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: Fedora 22, GTK 3. > Reporter: Marián Labuda > Labels: application_wizard, explorer, openshift_v3 > Fix For: 4.4.x > > Attachments: empty_project.png > > > When I am opening a new OpenShift application wizard on OpenShift 3 connection where are no projects yet, at first project dialog to create a new project is opened. Upon creation of a new project, dialog is closed and I am "redirected" back to application wizard, where newly created project should be preselected. Problem is the new project is shown as empty tree item in OpenShift explorer (this happens also if new project dialog is opened directly from the context menu of a clean connection) what makes new OpenShift application wizard unusable, because there are no projects in combo, no matter what. See following screenshot > !empty_project.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21593) Application wizard: Opening wizard and creating required project (clean connection) makes wizard unusable

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21593?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21593: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.1.CR1) > Application wizard: Opening wizard and creating required project (clean connection) makes wizard unusable > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21593 > URL: https://issues.jboss.org/browse/JBIDE-21593 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: Fedora 22, GTK 3. > Reporter: Marián Labuda > Labels: application_wizard, explorer, openshift_v3 > Fix For: 4.4.x > > Attachments: empty_project.png > > > When I am opening a new OpenShift application wizard on OpenShift 3 connection where are no projects yet, at first project dialog to create a new project is opened. Upon creation of a new project, dialog is closed and I am "redirected" back to application wizard, where newly created project should be preselected. Problem is the new project is shown as empty tree item in OpenShift explorer (this happens also if new project dialog is opened directly from the context menu of a clean connection) what makes new OpenShift application wizard unusable, because there are no projects in combo, no matter what. See following screenshot > !empty_project.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3552) Developer - be able to incrementally deploy changes to docker containers

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3552?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3552: --------------------------------- Component/s: openshift > Developer - be able to incrementally deploy changes to docker containers > ------------------------------------------------------------------------- > > Key: JBDS-3552 > URL: https://issues.jboss.org/browse/JBDS-3552 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: docker, openshift > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Critical > Fix For: 9.1.0.CR1, 10.0.0.Alpha1 > > > User Story: > As a Developer I want to be able to incrementally deploy changes to my running application without building from scratch so I can see changes quickly. > Acceptance Criteria: > * Once the initial application is deployed changes made in the IDE should be deployed over to the containers filesystem/deployment. > * Changes that the runtime support to pickup dynamically (i.e. html/js for JavaEE) should take effect immediatly and be seen in a browser refresh. > * Changes that the the runtime requires a restart for (i.e. class files) should take effect when restarting the application (which should not require a rebuild from source) > * Same workflow should work for docker and openshift applications (but each might implement it differently using oc sync or docker rsync or volume mounts etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3552) Developer - be able to incrementally deploy changes to docker containers

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3552?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3552: -------------------------------------- This one mentions both a pure docker and OS3 applications. Do we have a separate issue for the OS3 JavaEE stuff which we still need to implement/fix? > Developer - be able to incrementally deploy changes to docker containers > ------------------------------------------------------------------------- > > Key: JBDS-3552 > URL: https://issues.jboss.org/browse/JBDS-3552 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: docker > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Critical > Fix For: 9.1.0.CR1, 10.0.0.Alpha1 > > > User Story: > As a Developer I want to be able to incrementally deploy changes to my running application without building from scratch so I can see changes quickly. > Acceptance Criteria: > * Once the initial application is deployed changes made in the IDE should be deployed over to the containers filesystem/deployment. > * Changes that the runtime support to pickup dynamically (i.e. html/js for JavaEE) should take effect immediatly and be seen in a browser refresh. > * Changes that the the runtime requires a restart for (i.e. class files) should take effect when restarting the application (which should not require a rebuild from source) > * Same workflow should work for docker and openshift applications (but each might implement it differently using oc sync or docker rsync or volume mounts etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21758) Change "Learn about JBoss" link?

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21758?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-21758. --------------------------------- Assignee: Fred Bricon Resolution: Done Done. Update reopen Central in the latest CR1 build to see the change. > Change "Learn about JBoss" link? > -------------------------------- > > Key: JBIDE-21758 > URL: https://issues.jboss.org/browse/JBIDE-21758 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.3.1.CR1 > > > Central has a "Learn about JBoss" link (http://screencast.com/t/rnUDVvKW3Zsq @ 0'11") that opens http://www.jboss.org/get-started/. Does it need to point to something else? If yes then what? > cc [~crobson], [~maxandersen], [~rayploski-launch] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3552) Developer - be able to incrementally deploy changes to docker containers

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3552?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3552: --------------------------------- Priority: Critical (was: Major) > Developer - be able to incrementally deploy changes to docker containers > ------------------------------------------------------------------------- > > Key: JBDS-3552 > URL: https://issues.jboss.org/browse/JBDS-3552 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: docker > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Critical > Fix For: 9.1.0.CR1, 10.0.0.Alpha1 > > > User Story: > As a Developer I want to be able to incrementally deploy changes to my running application without building from scratch so I can see changes quickly. > Acceptance Criteria: > * Once the initial application is deployed changes made in the IDE should be deployed over to the containers filesystem/deployment. > * Changes that the runtime support to pickup dynamically (i.e. html/js for JavaEE) should take effect immediatly and be seen in a browser refresh. > * Changes that the the runtime requires a restart for (i.e. class files) should take effect when restarting the application (which should not require a rebuild from source) > * Same workflow should work for docker and openshift applications (but each might implement it differently using oc sync or docker rsync or volume mounts etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21757) Rename JBoss Central into Red Hat Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21757?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-21757. --------------------------------- Resolution: Done [~crobson] said Shadowman is fine, so I guess the change is complete now. The new page is available for CR1 builds already. Updated logos and labels should be available in the next CI build. > Rename JBoss Central into Red Hat Central > ----------------------------------------- > > Key: JBIDE-21757 > URL: https://issues.jboss.org/browse/JBIDE-21757 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.3.1.CR1 > > > Need to rename JBoss Central into Red Hat Central > - change all text references of Central in plugins > - change all text references of Central in webpage > - use Red Hat icon for Central tab in Eclipse > - make Eclipse point to new version of webpage in ide-config.properties -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21463) Port Forwarding: No error message pop up when attempt to port-forward to a port in use

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21463?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21463: ----------------------------------- Assignee: Viacheslav Kabanovich Resolution: Done PR applied in master / 4.3.x. Thanks [~scabanovich] > Port Forwarding: No error message pop up when attempt to port-forward to a port in use > -------------------------------------------------------------------------------------- > > Key: JBIDE-21463 > URL: https://issues.jboss.org/browse/JBIDE-21463 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: OpenShift 3 Tools: 3.1.0.Beta2-v20160114-1935-B149 > OS: Fedora 17 & MAC OS 10 > Reporter: Xia Zhao > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.3.1.CR1 > > > No error message pop up when attempt to port-forward to a port in use in Jboss Developer Studio. This issue does not repro in Eclipse on Mac OS. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21759) Rename JBoss Perspective into Red Hat perspective?

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21759?page=com.atlassian.jira.plugi... ] Fred Bricon closed JBIDE-21759. ------------------------------- Resolution: Rejected > Rename JBoss Perspective into Red Hat perspective? > -------------------------------------------------- > > Key: JBIDE-21759 > URL: https://issues.jboss.org/browse/JBIDE-21759 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Fix For: 4.4.0.Alpha1 > > > Given that we're supposed to use the JBoss brand to reference products only, I believe the JBoss Perspective just then be renamed to Red Hat Perspective. Amirite? > cc: [~maxandersen], [~crobson] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21716) Don't re-prompt for password

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21716?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21716: ----------------------------------- Priority: Blocker (was: Critical) > Don't re-prompt for password > ---------------------------- > > Key: JBIDE-21716 > URL: https://issues.jboss.org/browse/JBIDE-21716 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Reporter: Pete Muir > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > Having installed JBDS and CDK from the installer, and entered your password there, you get re-prompted for your password for the customer portal. This is a poor user experience. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 February 2016