December 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15941) Explorer: progress of deleting applications is not shown

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15941?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15941: ------------------------------------- Summary: Explorer: progress of deleting applications is not shown (was: Progress of deleting applications is not shown) > Explorer: progress of deleting applications is not shown > -------------------------------------------------------- > > Key: JBIDE-15941 > URL: https://issues.jboss.org/browse/JBIDE-15941 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.x > > Attachments: delete1.png, delete2.png > > > When deleting more applications at once (tried 2 and 3), there is a progress bar. For first application it shows correctly name. But for any other application (second, third...) there is missing text label and also missing percentage of progress. See attached images. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14848) Two "Open CSS Dialog..." actions on toolbar

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14848?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-14848: ---------------------------------- Attachment: OpenCSSDialog2.png OpenCSSDialog1.png > Two "Open CSS Dialog..." actions on toolbar > ------------------------------------------- > > Key: JBIDE-14848 > URL: https://issues.jboss.org/browse/JBIDE-14848 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing, upstream > Affects Versions: 4.1.0.Beta2 > Reporter: Alexey Kazakov > Assignee: Daniel Azarov > Fix For: 4.2.x > > Attachments: OpenCSSDialog1.png, OpenCSSDialog2.png, scr.png > > > JBoss Perspective. Open any *.css file. There are two "Open CSS Dialog..." actions: > !scr.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14848) Two "Open CSS Dialog..." actions on toolbar

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14848?page=com.atlassian.jira.plugi... ] Daniel Azarov commented on JBIDE-14848: --------------------------------------- Fixed. !OpenCSSDialog1.png! !OpenCSSDialog2.png! > Two "Open CSS Dialog..." actions on toolbar > ------------------------------------------- > > Key: JBIDE-14848 > URL: https://issues.jboss.org/browse/JBIDE-14848 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing, upstream > Affects Versions: 4.1.0.Beta2 > Reporter: Alexey Kazakov > Assignee: Daniel Azarov > Fix For: 4.2.x > > Attachments: OpenCSSDialog1.png, OpenCSSDialog2.png, scr.png > > > JBoss Perspective. Open any *.css file. There are two "Open CSS Dialog..." actions: > !scr.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9924) Cloning an app with invalid pom results no project imported to your workspace

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9924?page=com.atlassian.jira.plugin... ] Andre Dietisheim closed JBIDE-9924. ----------------------------------- Fix Version/s: 4.2.0.Alpha1 (was: 4.2.x) Resolution: Won't Fix resolving as WONT_FIX since maven cannot import fails with un > Cloning an app with invalid pom results no project imported to your workspace > ----------------------------------------------------------------------------- > > Key: JBIDE-9924 > URL: https://issues.jboss.org/browse/JBIDE-9924 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.M4 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.0.Alpha1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10017) openshift-java-client: Add OS in user agent when communicating with the OpenShift Express REST service

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10017?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-10017: ------------------------------------- Fix Version/s: LATER (was: 4.2.x) > openshift-java-client: Add OS in user agent when communicating with the OpenShift Express REST service > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-10017 > URL: https://issues.jboss.org/browse/JBIDE-10017 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.M4 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: LATER > > > We currently use a custom user agent string (in the OpenShift Express client) when communication with the OpenShift Express REST service. We should also report the OS and version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10017) openshift-java-client: Add OS in user agent when communicating with the OpenShift Express REST service

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10017?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-10017: ------------------------------------------ setting to LATER since it's unlikely that we'll implement this in the near future (unless explicitly required) > openshift-java-client: Add OS in user agent when communicating with the OpenShift Express REST service > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-10017 > URL: https://issues.jboss.org/browse/JBIDE-10017 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.M4 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: LATER > > > We currently use a custom user agent string (in the OpenShift Express client) when communication with the OpenShift Express REST service. We should also report the OS and version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13934) implement application ready-wait using dns_resolvable

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13934?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-13934. -------------------------------------- Resolution: Rejected > implement application ready-wait using dns_resolvable > ----------------------------------------------------- > > Key: JBIDE-13934 > URL: https://issues.jboss.org/browse/JBIDE-13934 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: LATER > > > When waiting for an app to become ready, we simply try to resolve it's hostname and report it ready as soon as we can resolve it. > Apparently there's a cache for DNS resolution that holds entries (successful/unsuccessful resolution) that prevents immediate feedback. The immediate feedback is provided by a RESTful resource on the broker: > {code} > GET https://host/broker/rest/domains/<id>/applications/<id>/dns_resolvable > {code} > Quote from rally > {quote} > 1. Who is it for? (e.g. all users, serious developers, paid tier) > All users > 2. What product does it apply to? (Online, Enterprise, Origin) > All > 3. What is it? What does it do? > A simple broker API check to see if DNS is created via an actual DNS nameserver lookup that is not subject to caching. > 4. How do you use it? What is the user impact? > Request: > GET https://host/broker/rest/domains/<id>/applications/<id>/dns_resolvable > Response: > ->If DNS is resolvable > HTTP status:200 > Body: {"supported_api_versions":[1.0,1.1,1.2],"data":true,"type":"boolean","status":"ok","messages":[],"version":"1.2"} > ->If DNS is not resolvable > HTTP status:404 > 5. Why is it important? > The problem is when a client tool checks to see if DNS is available or not, that value gets cached for a solid 30 seconds. To avoid the cache, queries can be run directly against DYN's DNS servers. > This broker API check to see if DNS is created by querying DNS servers directly. > 6. What version number of software, package, client tools, etc? > NA > 7. When is it available for GA? (OSE 1.2, Online Sprint #) > Spring 19 > 8. What tools / software does the docs team need to test it? (if applicable) > NA - already been tested by QE > 9. Are there any blog or wiki posts on the subject? (Provide links) > No > 10. Any other notes or details that users should know that will help the docs team? > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13934) implement application ready-wait using dns_resolvable

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13934?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-13934: ------------------------------------------ the current approach which tries DNS resolution is not hurting anoyne. Resolving this as not required. > implement application ready-wait using dns_resolvable > ----------------------------------------------------- > > Key: JBIDE-13934 > URL: https://issues.jboss.org/browse/JBIDE-13934 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: LATER > > > When waiting for an app to become ready, we simply try to resolve it's hostname and report it ready as soon as we can resolve it. > Apparently there's a cache for DNS resolution that holds entries (successful/unsuccessful resolution) that prevents immediate feedback. The immediate feedback is provided by a RESTful resource on the broker: > {code} > GET https://host/broker/rest/domains/<id>/applications/<id>/dns_resolvable > {code} > Quote from rally > {quote} > 1. Who is it for? (e.g. all users, serious developers, paid tier) > All users > 2. What product does it apply to? (Online, Enterprise, Origin) > All > 3. What is it? What does it do? > A simple broker API check to see if DNS is created via an actual DNS nameserver lookup that is not subject to caching. > 4. How do you use it? What is the user impact? > Request: > GET https://host/broker/rest/domains/<id>/applications/<id>/dns_resolvable > Response: > ->If DNS is resolvable > HTTP status:200 > Body: {"supported_api_versions":[1.0,1.1,1.2],"data":true,"type":"boolean","status":"ok","messages":[],"version":"1.2"} > ->If DNS is not resolvable > HTTP status:404 > 5. Why is it important? > The problem is when a client tool checks to see if DNS is available or not, that value gets cached for a solid 30 seconds. To avoid the cache, queries can be run directly against DYN's DNS servers. > This broker API check to see if DNS is created by querying DNS servers directly. > 6. What version number of software, package, client tools, etc? > NA > 7. When is it available for GA? (OSE 1.2, Online Sprint #) > Spring 19 > 8. What tools / software does the docs team need to test it? (if applicable) > NA - already been tested by QE > 9. Are there any blog or wiki posts on the subject? (Provide links) > No > 10. Any other notes or details that users should know that will help the docs team? > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13934) implement application ready-wait using dns_resolvable

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13934?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13934: ------------------------------------- Fix Version/s: LATER (was: 4.2.x) > implement application ready-wait using dns_resolvable > ----------------------------------------------------- > > Key: JBIDE-13934 > URL: https://issues.jboss.org/browse/JBIDE-13934 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: LATER > > > When waiting for an app to become ready, we simply try to resolve it's hostname and report it ready as soon as we can resolve it. > Apparently there's a cache for DNS resolution that holds entries (successful/unsuccessful resolution) that prevents immediate feedback. The immediate feedback is provided by a RESTful resource on the broker: > {code} > GET https://host/broker/rest/domains/<id>/applications/<id>/dns_resolvable > {code} > Quote from rally > {quote} > 1. Who is it for? (e.g. all users, serious developers, paid tier) > All users > 2. What product does it apply to? (Online, Enterprise, Origin) > All > 3. What is it? What does it do? > A simple broker API check to see if DNS is created via an actual DNS nameserver lookup that is not subject to caching. > 4. How do you use it? What is the user impact? > Request: > GET https://host/broker/rest/domains/<id>/applications/<id>/dns_resolvable > Response: > ->If DNS is resolvable > HTTP status:200 > Body: {"supported_api_versions":[1.0,1.1,1.2],"data":true,"type":"boolean","status":"ok","messages":[],"version":"1.2"} > ->If DNS is not resolvable > HTTP status:404 > 5. Why is it important? > The problem is when a client tool checks to see if DNS is available or not, that value gets cached for a solid 30 seconds. To avoid the cache, queries can be run directly against DYN's DNS servers. > This broker API check to see if DNS is created by querying DNS servers directly. > 6. What version number of software, package, client tools, etc? > NA > 7. When is it available for GA? (OSE 1.2, Online Sprint #) > Spring 19 > 8. What tools / software does the docs team need to test it? (if applicable) > NA - already been tested by QE > 9. Are there any blog or wiki posts on the subject? (Provide links) > No > 10. Any other notes or details that users should know that will help the docs team? > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13723) Application wizard: "uncommitted changes" when merging ticket-monster with OpenShift application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13723?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13723: ------------------------------------- Labels: application_wizard (was: ) > Application wizard: "uncommitted changes" when merging ticket-monster with OpenShift application > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-13723 > URL: https://issues.jboss.org/browse/JBIDE-13723 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.0.1.Final, 4.1.0.Alpha1 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Labels: application_wizard > Fix For: 4.2.x > > Attachments: out.ogv > > > OpenShift wizard shows an error dialog with "Could not import project to the workspace." message: > {code} > org.jboss.tools.openshift.express.internal.ui.UnCommittedChangesException: The project ticket-monster has uncommitted changes. Please commit those changes first. > at org.jboss.tools.openshift.express.internal.ui.wizard.application.importoperation.ConfigureGitSharedProject.execute(ConfigureGitSharedProject.java:101) > at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftExpressApplicationWizardModel.configureGitSharedProject(OpenShiftExpressApplicationWizardModel.java:158) > at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftExpressApplicationWizard$ImportJob.runInWorkspace(OpenShiftExpressApplicationWizard.java:319) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {code} > Although git status says there nothing to commit: > {code} > [sbunciak@dhcp-27-195 ticket-monster]$ git status > # On branch master > nothing to commit (working directory clean) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 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 December 2013