July 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-376) Delete old OpenShift Tools doc

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-376?page=com.atlassian.jira.plug... ] Andre Dietisheim commented on TOOLSDOC-376: ------------------------------------------- I pushed to master and jbosstools-4.1.x > Delete old OpenShift Tools doc > ------------------------------ > > Key: TOOLSDOC-376 > URL: https://issues.jboss.org/browse/TOOLSDOC-376 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: General documentation issues, User Guide - OpenShift Tools > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Andre Dietisheim > Fix For: 4.1.0 > > > OpenShift Tools has a chapter in the new 4.1.x user guide. > The old OpenShift Tools reference document needs to be deleted from the jbosstools-openshift repository (https://github.com/jbosstools/jbosstools-openshift). > Specifically, the *docs/* directory must be deleted from *master* and *4.1.x* branches. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-376) Delete old OpenShift Tools doc

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-376?page=com.atlassian.jira.plug... ] Andre Dietisheim resolved TOOLSDOC-376. --------------------------------------- Resolution: Done > Delete old OpenShift Tools doc > ------------------------------ > > Key: TOOLSDOC-376 > URL: https://issues.jboss.org/browse/TOOLSDOC-376 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: General documentation issues, User Guide - OpenShift Tools > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Andre Dietisheim > Fix For: 4.1.0 > > > OpenShift Tools has a chapter in the new 4.1.x user guide. > The old OpenShift Tools reference document needs to be deleted from the jbosstools-openshift repository (https://github.com/jbosstools/jbosstools-openshift). > Specifically, the *docs/* directory must be deleted from *master* and *4.1.x* branches. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-376) Delete old OpenShift Tools doc

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-376?page=com.atlassian.jira.plug... ] Andre Dietisheim updated TOOLSDOC-376: -------------------------------------- Fix Version/s: 4.2.0 > Delete old OpenShift Tools doc > ------------------------------ > > Key: TOOLSDOC-376 > URL: https://issues.jboss.org/browse/TOOLSDOC-376 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: General documentation issues, User Guide - OpenShift Tools > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Andre Dietisheim > Fix For: 4.1.0, 4.2.0 > > > OpenShift Tools has a chapter in the new 4.1.x user guide. > The old OpenShift Tools reference document needs to be deleted from the jbosstools-openshift repository (https://github.com/jbosstools/jbosstools-openshift). > Specifically, the *docs/* directory must be deleted from *master* and *4.1.x* branches. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10939) OpenShift Express Console: Should have "Edit Connection" in the context menu

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10939?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-10939: --------------------------------------- Ok, I understand ! Still, the work provided in this JIRA is alreay a nice UI improvement ;-) thanks ! > OpenShift Express Console: Should have "Edit Connection" in the context menu > ---------------------------------------------------------------------------- > > Key: JBIDE-10939 > URL: https://issues.jboss.org/browse/JBIDE-10939 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.0.Alpha1 > > Attachments: edit-connection.png, new-connection.png, Screen Shot 2013-07-29 at 11.35.23 AM.png > > > it's not obvious how one would edit the user entries in the OpenShift Express console. The most user friendly and obvious way would be to offer *Edit Connection* in the context menu to an entry in the *OpenShift Express Console* -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15158) if I create a scalable application I get a non-useful dialog about HAProxy (watcher)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15158?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-15158: ------------------------------------------------- Andre Dietisheim <adietish(a)redhat.com> made a comment on [bug 982615|https://bugzilla.redhat.com/show_bug.cgi?id=982615] @Meng Bo: I apparently cannot set this status (ON_QA). The only choices I have in status are assigned or closed. What do I miss? > if I create a scalable application I get a non-useful dialog about HAProxy (watcher) > ------------------------------------------------------------------------------------ > > Key: JBIDE-15158 > URL: https://issues.jboss.org/browse/JBIDE-15158 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.1.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.x > > Attachments: ha-proxy-started.png > > > How to reproduce: > # ASSERT: make sure that you dont have any scalable application in your domain > # EXEC: launch OpenShift application wizard and provide some name, type and check *enable Scaling* > Result: > You get a dialog which informs you that the HAProxy was started: > !ha-proxy-started.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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10939) OpenShift Express Console: Should have "Edit Connection" in the context menu

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10939?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-10939: ------------------------------------------ Sure the hyperlink in the view when no connection exists is the ultimate enhancement. I focussed on having the context menu entries here and can further enhance and provide the hyperlink if needed. > OpenShift Express Console: Should have "Edit Connection" in the context menu > ---------------------------------------------------------------------------- > > Key: JBIDE-10939 > URL: https://issues.jboss.org/browse/JBIDE-10939 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.0.Alpha1 > > Attachments: edit-connection.png, new-connection.png, Screen Shot 2013-07-29 at 11.35.23 AM.png > > > it's not obvious how one would edit the user entries in the OpenShift Express console. The most user friendly and obvious way would be to offer *Edit Connection* in the context menu to an entry in the *OpenShift Express Console* -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15286) Increment service version of jbosstools-base/usage submodule

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15286?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-15286: ---------------------------------------- Assignee: Andre Dietisheim > Increment service version of jbosstools-base/usage submodule > ------------------------------------------------------------ > > Key: JBIDE-15286 > URL: https://issues.jboss.org/browse/JBIDE-15286 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: usage > Affects Versions: 4.2.0.Alpha1 > Reporter: Denis Golovin > Assignee: Andre Dietisheim > Fix For: 4.2.0.Alpha1 > > > Internal classes only were changed since creating 4.1.x branch. Service version should be changed from 1.2.1 to 1.2.200 according http://wiki.eclipse.org/Version_Numbering. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15158) if I create a scalable application I get a non-useful dialog about HAProxy (watcher)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15158?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-15158: ------------------------------------------------- Meng Bo <bmeng(a)redhat.com> made a comment on [bug 982615|https://bugzilla.redhat.com/show_bug.cgi?id=982615] According to comment#9, please move the bug back to ON_QA, and QE will verify it. > if I create a scalable application I get a non-useful dialog about HAProxy (watcher) > ------------------------------------------------------------------------------------ > > Key: JBIDE-15158 > URL: https://issues.jboss.org/browse/JBIDE-15158 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.1.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.x > > Attachments: ha-proxy-started.png > > > How to reproduce: > # ASSERT: make sure that you dont have any scalable application in your domain > # EXEC: launch OpenShift application wizard and provide some name, type and check *enable Scaling* > Result: > You get a dialog which informs you that the HAProxy was started: > !ha-proxy-started.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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15158) if I create a scalable application I get a non-useful dialog about HAProxy (watcher)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15158?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-15158: ------------------------------------------------- Andre Dietisheim <adietish(a)redhat.com> made a comment on [bug 982615|https://bugzilla.redhat.com/show_bug.cgi?id=982615] @Meng Bo: As soon as severity/field are not RESULT we wont show it in the Eclipse tooling which is what a user is imho expecting. We have a generic logic in the tooling where we only show messages that are either RESULT in severity or in field. I cant say if DEBUG or WARNING are the right severities for you guys though. > if I create a scalable application I get a non-useful dialog about HAProxy (watcher) > ------------------------------------------------------------------------------------ > > Key: JBIDE-15158 > URL: https://issues.jboss.org/browse/JBIDE-15158 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.1.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.x > > Attachments: ha-proxy-started.png > > > How to reproduce: > # ASSERT: make sure that you dont have any scalable application in your domain > # EXEC: launch OpenShift application wizard and provide some name, type and check *enable Scaling* > Result: > You get a dialog which informs you that the HAProxy was started: > !ha-proxy-started.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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15261) Cannot create wordpress example

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15261?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-15261: ------------------------------------------ [~corehello] we set fixVersion to 4.2.0.Alpha1 and did not solve this for 4.1.0.Final since this requires a major change in the client library. > Cannot create wordpress example > ------------------------------- > > Key: JBIDE-15261 > URL: https://issues.jboss.org/browse/JBIDE-15261 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Beta2 > Reporter: nan wei > Assignee: Andre Dietisheim > Fix For: 4.2.0.Alpha1 > > Attachments: create-wordpress-example.png, initial-build-failed.png > > > Version: > JBoss Deverloper Studio 7 Beta > OpenShift Plugin: 2.5.0.Beta2-v20130621-1052-B65 > OpenShift Enterprise 1.2/2013-07-18.4 > How reproducible: > always > Steps to Reproduce: > 1. Create an app in the JBoss Deverloper Studio. > Name: mysqltest > Type: PHP 5.3(php-5.3) > Embeddable Cartridges: MySQL Database 5.1(mysql-5.1) > 2. Click Advanced > Add Source Code:https://github.com/openshift/wordpress-example > !create-wordpress-example.png! > Actual results: > When creating an app, check mysql cartridge and add source code together, it will fail, and return the following error: > !initial-build-failed.png! > {code} > Could not create application "a3" > Could not request https://broker.ose0717.com/broker/rest/domains/nwei/applications: The initial build for the application failed. Last 10 kB of build output: > httpd (no pid file) not running > Could not find mysql database. Please run: > rhc cartridge add -a a3 -c mysql-5.1 > then make a sample commit (add whitespace somewhere) and re-push > An error occurred executing 'gear postreceive' > For more details about the problem, try running the command again with the '--trace' option. > {code} > But if use rhc client, there is no such problem, it is created successfully. > # rhc app create mysqltest1 php-5.3 mysql-5.1 --from-code=https://github.com/openshift/wordpress-example -- 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, 8 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 July 2013