May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3873) DevStudio 10.0.0.Alpha1 points to 9.0 update site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3873?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3873: ----------------------------- > DevStudio 10.0.0.Alpha1 points to 9.0 update site > ------------------------------------------------- > > Key: JBDS-3873 > URL: https://issues.jboss.org/browse/JBDS-3873 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: build > Affects Versions: 10.0.0.Alpha1 > Reporter: Martin Malina > Assignee: Nick Boldt > > I'm not sure exactly where this jira belongs. But I'm sure Nick will know :) > I just installed DevStudio 10.0.0.Alpha1 B5251 and when I go to Help -> Install New Software, I can see that the only update site that is set up is: > https://devstudio.redhat.com/9.0/stable/updates/ > I know that there is probably nothing at /10.0/ yet, but at some point we will want to move to that URL. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22227) Hotcode replace fails on local wildfly if breakpoint is set

by Thomas Mäder (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22227?page=com.atlassian.jira.plugi... ] Thomas Mäder commented on JBIDE-22227: -------------------------------------- Installing a breakpoint in a class creates a hard reference to the class, it seems. In the end, it's the same issue as the the HCR: you can't tell a garbage class from a live one. Hopefully, someone from the Open JDK or jdt-debug world can shed some light. > Hotcode replace fails on local wildfly if breakpoint is set > ----------------------------------------------------------- > > Key: JBIDE-22227 > URL: https://issues.jboss.org/browse/JBIDE-22227 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > When debugging a local wildfly server with a deployed servlet, making a breaking change such as method name or signature will fail. > This will pop up a dialog asking to restart the module or the server, which is expected. However, after that, non-breaking changes will still also pop up the hotcode-failed dialog, when it shouldn't. > Workflow: > 1) Create a dynamic web project with simple servlet > 2) Start a wildfly 10 in debug mode and deploy the web project > 3) Run-on-server the servlet object and verify it shows expected output > 4) Set a breakpoint inside the doGet() method > 5) refresh browser (breakpoint gets hit), press play > 6) Make a non-breaking change (change text inside doGet()) > 7) refresh website, verify breakpoint is hit, website content is updated > 8) make a breaking change by adding a new method > 9) hotcode-replace dialog appears. Press 'restart module' > 10) refresh web browser, verify breakpoint is hit, output has changed as expected > 11) make a non-breaking change in output of doGet() > 12) ASSERT: hotcode replace dialog does NOT show - THIS STEP FAILS -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22289) Deploy Docker Wizard: Suggestion box of docker images is still visible on the next wizard page

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22289?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22289: ----------------------------------- Story Points: 1 Sprint: devex #113 April 2016 Priority: Minor (was: Critical) Assignee: Viacheslav Kabanovich > Deploy Docker Wizard: Suggestion box of docker images is still visible on the next wizard page > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-22289 > URL: https://issues.jboss.org/browse/JBIDE-22289 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Environment: Fedora 22, GTK 3. > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: docker, openshift_v3 > Fix For: 4.4.0.Alpha2 > > > If I start typing name of image in Deploy Image to OpenShift wizard in the Image Name: text widget, suggestions are provided (autocomplete). If I select an image in this suggestion box by hitting Enter key, and then click by mouse on Next button, the next wizard page (Deployment Configuration and Scalability) shows this suggestion box again and on top, even it disappeared in previous wizard page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22293) Deploy Docker Image: Next gets enabled after canceling Manage Projects

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22293?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22293: -------------------------------- Priority: Minor (was: Major) > Deploy Docker Image: Next gets enabled after canceling Manage Projects > ---------------------------------------------------------------------- > > Key: JBIDE-22293 > URL: https://issues.jboss.org/browse/JBIDE-22293 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.4.0.Alpha2 > > > Open wizard Deploy Docker Image on a connection with no Projects. Fill all fields, beside OpenShift Project. Next remains disabled. Call 'Manage Projects' wizard and cancel it. Next gets incorrectly enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22293) Deploy Docker Image: Next gets enabled after canceling Manage Projects

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22293?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22293: -------------------------------- Sprint: devex #113 April 2016 > Deploy Docker Image: Next gets enabled after canceling Manage Projects > ---------------------------------------------------------------------- > > Key: JBIDE-22293 > URL: https://issues.jboss.org/browse/JBIDE-22293 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.4.0.Alpha2 > > > Open wizard Deploy Docker Image on a connection with no Projects. Fill all fields, beside OpenShift Project. Next remains disabled. Call 'Manage Projects' wizard and cancel it. Next gets incorrectly enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-734) migrate docs from old URL to new one

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-734?page=com.atlassian.jira.plug... ] Nick Boldt commented on TOOLSDOC-734: ------------------------------------- It appears that the old doc links for JBoss_Developer_Studio, such as https://access.redhat.com/knowledge/docs/en-US/JBoss_Developer_Studio/6.0... , redirect to https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... (adding in the Red_Hat_ prefix) So I would expect we'd do the same for https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio/ (and all those listed above) links redirecting to the newly branded URL pattern, https://access.redhat.com/documentation/en/red-hat-developer-studio/ etc. > migrate docs from old URL to new one > ------------------------------------ > > Key: TOOLSDOC-734 > URL: https://issues.jboss.org/browse/TOOLSDOC-734 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: General documentation issues > Affects Versions: 9.0.0 > Reporter: Nick Boldt > Fix For: 10.0.0.GA > > > Currently, we host doc here [1],[2],[3] (which all redirect to [4]), but as part of the rebranding we should move the docs to a new URL [5] and set up a URL redirect so people with the old bookmark can find the new content. > [1] https://access.redhat.com/knowledge/docs/Red_Hat_JBoss_Developer_Studio/ > [2] https://access.redhat.com/site/documentation/Red_Hat_JBoss_Developer_Studio/ > [3] https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > [4] https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio/ > [5] https://access.redhat.com/documentation/en/red-hat-developer-studio/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22293) Deploy Docker Image: Next gets enabled after canceling Manage Projects

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22293?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22293: ----------------------------------------------- [~fbricon], please take a look at the pull request. > Deploy Docker Image: Next gets enabled after canceling Manage Projects > ---------------------------------------------------------------------- > > Key: JBIDE-22293 > URL: https://issues.jboss.org/browse/JBIDE-22293 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha2 > > > Open wizard Deploy Docker Image on a connection with no Projects. Fill all fields, beside OpenShift Project. Next remains disabled. Call 'Manage Projects' wizard and cancel it. Next gets incorrectly enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22293) Deploy Docker Image: Next gets enabled after canceling Manage Projects

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-22293: --------------------------------------------- Summary: Deploy Docker Image: Next gets enabled after canceling Manage Projects Key: JBIDE-22293 URL: https://issues.jboss.org/browse/JBIDE-22293 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.0.Alpha1 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 4.4.0.Alpha2 Open wizard Deploy Docker Image on a connection with no Projects. Fill all fields, beside OpenShift Project. Next remains disabled. Call 'Manage Projects' wizard and cancel it. Next gets incorrectly enabled. -- 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 Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22291?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich reassigned JBIDE-22291: --------------------------------------------- Assignee: Viacheslav Kabanovich > 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 > Assignee: Viacheslav Kabanovich > Labels: docker, openshift_v3 > Fix For: 4.4.0.Alpha2 > > > 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] (JBDS-3775) Missing maven.repository.redhat.com

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3775?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3775: -------------------------------- Component/s: installer (was: platform-installer) > Missing maven.repository.redhat.com > ----------------------------------- > > Key: JBDS-3775 > URL: https://issues.jboss.org/browse/JBDS-3775 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Burr Sutter > Priority: Critical > Labels: havoc > Fix For: 10.0.0.Alpha1 > > > After using the Installer, I select Red Hat Central, OpenShift Application, eap64-basic-sti which then imports the kitchensink project into my workspace, it immediately has compile errors > http://screencast.com/t/y1NFnvaMcJD -- 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