June 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2411) Update JBoss Server Manager Red Guide to include updated info for as7.1 tooling

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-2411?page=com.atlassian.jira.plugin.... ] Martin Malina updated JBDS-2411: -------------------------------- Fix Version/s: 7.0.0.GA (was: 7.0.x) > Update JBoss Server Manager Red Guide to include updated info for as7.1 tooling > ------------------------------------------------------------------------------- > > Key: JBDS-2411 > URL: https://issues.jboss.org/browse/JBDS-2411 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: documentation > Affects Versions: 6.0.x > Reporter: Martin Malina > Assignee: Michelle Murray > Fix For: 7.0.0.GA > > Attachments: new-eap6.png > > > The information at https://access.redhat.com/knowledge/docs/en-US/JBoss_Developer_Studio/5.0... is not up2date. When you create an AS7 server (7.0.2+) you can check if you want to expose the management port. Also, for most servers you can check if the server is to be bound to all interfaces. > Note that for a local server you don't really need to expose the management port - it is bound to localhost by default. But for remote servers you need to use it if you want to make a jmx connection to the server. > Also, if this option is checked, it will set the startup poller for that server to JBoss 7 Manager Service. For the startup poller and jmx connection to work you need to have a user created on the given remote server. > Please let me or Rob know if you need more info on this. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13483) Update as bot test for a new string in EAP 6.1

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13483?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-13483: ---------------------------------- Fix Version/s: 4.0.2.Final (was: 4.0.x) > Update as bot test for a new string in EAP 6.1 > ---------------------------------------------- > > Key: JBIDE-13483 > URL: https://issues.jboss.org/browse/JBIDE-13483 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: QA > Affects Versions: 4.0.2.Final, 4.1.0.Alpha1 > Reporter: Martin Malina > Assignee: Radim Hopp > Fix For: 4.0.2.Final, 4.1.0.Alpha1 > > > Some of the tests in https://github.com/jbosstools/jbosstools-integration-tests/tree/master/te... will need to be updated to accommodate a slight change in EAP 6.1. > When you deploy a project the log used to contain: > Registering web context: /jsp-project > But now in EAP 6.1.0.DR3 it says: > Register web context: /jsp-project > See the test failure here: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-JBDS... > The expected string is actually defined in org.jboss.ide.eclipse.as.ui.bot.test/src/org/jboss/ide/eclipse/as/ui/bot/test/eap6/DeployJSPProjectEAP6Server.java > and the fix would be trivial. But it's probably better to create a new template for 6.1 and have it separate from 6.0. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13483) Update as bot test for a new string in EAP 6.1

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13483?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-13483. --------------------------------- Resolution: Done > Update as bot test for a new string in EAP 6.1 > ---------------------------------------------- > > Key: JBIDE-13483 > URL: https://issues.jboss.org/browse/JBIDE-13483 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: QA > Affects Versions: 4.0.2.Final, 4.1.0.Alpha1 > Reporter: Martin Malina > Assignee: Radim Hopp > Fix For: 4.0.2.Final, 4.1.0.Alpha1 > > > Some of the tests in https://github.com/jbosstools/jbosstools-integration-tests/tree/master/te... will need to be updated to accommodate a slight change in EAP 6.1. > When you deploy a project the log used to contain: > Registering web context: /jsp-project > But now in EAP 6.1.0.DR3 it says: > Register web context: /jsp-project > See the test failure here: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-JBDS... > The expected string is actually defined in org.jboss.ide.eclipse.as.ui.bot.test/src/org/jboss/ide/eclipse/as/ui/bot/test/eap6/DeployJSPProjectEAP6Server.java > and the fix would be trivial. But it's probably better to create a new template for 6.1 and have it separate from 6.0. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12312) If domain creation fails because of name that's already used (or forbidden), no info is visible in wizard after you closed the error dialog

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12312?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12312: ------------------------------------- Summary: If domain creation fails because of name that's already used (or forbidden), no info is visible in wizard after you closed the error dialog (was: If domain creation fails because of name that's already used, no info is visible in wizard after you closed the error dialog) > If domain creation fails because of name that's already used (or forbidden), no info is visible in wizard after you closed the error dialog > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-12312 > URL: https://issues.jboss.org/browse/JBIDE-12312 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.x > > Attachments: domain-name-already-used.png, missing-user-guidance.png, no-error.png > > > If you create a new domain on OpenShift, you'll have to provide it's name. This name has to be unique across OpenShift (for all users). If you use a domain name that's already used, you'll get an error dialog that informs you about the name not being unique across OpenShift. > !domain-name-already-used.png! > Once you close this dialog, noting is showing this error any more. The name field is not decorated with an error marker. > steps to reproduce: > # ASSERT make sure you have an account without a domain > # EXEC launch the *OpenShift Application* wizard > # ASSERT you get to the *Domain creation* dialog > # EXEC supply a valid key and choose a domain name that is *already used* (ex. "domain") > # ASSERT You get an error dialog that tells you that the domain name is already used > # EXEC hit *OK* > Result: > The domain creation dialog has no information that would tell you what you have to correct. > !missing-user-guidance.png! > We should improved this: > * put an error decoration to the name text field > * put the cursor into the name text field (eventually select the whole name in it) > * eventually reach out to #libra to get a way to query the availability of the given name, so that we can validate while typing. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12312) If domain creation fails because of name that's already used, no info is visible in wizard after you closed the error dialog

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12312?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12312: ------------------------------------- Fix Version/s: 4.2.x (was: 4.1.x) > If domain creation fails because of name that's already used, no info is visible in wizard after you closed the error dialog > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-12312 > URL: https://issues.jboss.org/browse/JBIDE-12312 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.x > > Attachments: domain-name-already-used.png, missing-user-guidance.png, no-error.png > > > If you create a new domain on OpenShift, you'll have to provide it's name. This name has to be unique across OpenShift (for all users). If you use a domain name that's already used, you'll get an error dialog that informs you about the name not being unique across OpenShift. > !domain-name-already-used.png! > Once you close this dialog, noting is showing this error any more. The name field is not decorated with an error marker. > steps to reproduce: > # ASSERT make sure you have an account without a domain > # EXEC launch the *OpenShift Application* wizard > # ASSERT you get to the *Domain creation* dialog > # EXEC supply a valid key and choose a domain name that is *already used* (ex. "domain") > # ASSERT You get an error dialog that tells you that the domain name is already used > # EXEC hit *OK* > Result: > The domain creation dialog has no information that would tell you what you have to correct. > !missing-user-guidance.png! > We should improved this: > * put an error decoration to the name text field > * put the cursor into the name text field (eventually select the whole name in it) > * eventually reach out to #libra to get a way to query the availability of the given name, so that we can validate while typing. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12312) If domain creation fails because of name that's already used, no info is visible in wizard after you closed the error dialog

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12312?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-12312: ------------------------------------------ bumped to 4.2.x > If domain creation fails because of name that's already used, no info is visible in wizard after you closed the error dialog > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-12312 > URL: https://issues.jboss.org/browse/JBIDE-12312 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.x > > Attachments: domain-name-already-used.png, missing-user-guidance.png, no-error.png > > > If you create a new domain on OpenShift, you'll have to provide it's name. This name has to be unique across OpenShift (for all users). If you use a domain name that's already used, you'll get an error dialog that informs you about the name not being unique across OpenShift. > !domain-name-already-used.png! > Once you close this dialog, noting is showing this error any more. The name field is not decorated with an error marker. > steps to reproduce: > # ASSERT make sure you have an account without a domain > # EXEC launch the *OpenShift Application* wizard > # ASSERT you get to the *Domain creation* dialog > # EXEC supply a valid key and choose a domain name that is *already used* (ex. "domain") > # ASSERT You get an error dialog that tells you that the domain name is already used > # EXEC hit *OK* > Result: > The domain creation dialog has no information that would tell you what you have to correct. > !missing-user-guidance.png! > We should improved this: > * put an error decoration to the name text field > * put the cursor into the name text field (eventually select the whole name in it) > * eventually reach out to #libra to get a way to query the availability of the given name, so that we can validate while typing. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12171) Link to the OpenShift status page

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12171?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12171: ------------------------------------- Description: OpenShift has a nice status page that informs of ongoing issues on the PaaS. we should point the user to this page if we experience issues while working against the PaaS (ex. when getting 500-errors?). We could also display the current status in the OpenShift explorer. !openshift-status.png! was: OpenShift has a nice status page that informs of ongoing issues on the PaaS. we should point the user to this page if we experience issues while working against the PaaS (ex. when getting 500-errors?). !openshift-status.png! > Link to the OpenShift status page > --------------------------------- > > Key: JBIDE-12171 > URL: https://issues.jboss.org/browse/JBIDE-12171 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.x > > Attachments: openshift-status.png > > > OpenShift has a nice status page that informs of ongoing issues on the PaaS. we should point the user to this page if we experience issues while working against the PaaS (ex. when getting 500-errors?). > We could also display the current status in the OpenShift explorer. > !openshift-status.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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12171) Link to the OpenShift status page

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12171?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-12171: ------------------------------------------ bumped to 4.2.x > Link to the OpenShift status page > --------------------------------- > > Key: JBIDE-12171 > URL: https://issues.jboss.org/browse/JBIDE-12171 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.x > > Attachments: openshift-status.png > > > OpenShift has a nice status page that informs of ongoing issues on the PaaS. we should point the user to this page if we experience issues while working against the PaaS (ex. when getting 500-errors?). > We could also display the current status in the OpenShift explorer. > !openshift-status.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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12171) Link to the OpenShift status page

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12171?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12171: ------------------------------------- Summary: Link to the OpenShift status page (was: Add a link to the OpenShift status page in our errors) > Link to the OpenShift status page > --------------------------------- > > Key: JBIDE-12171 > URL: https://issues.jboss.org/browse/JBIDE-12171 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.x > > Attachments: openshift-status.png > > > OpenShift has a nice status page that informs of ongoing issues on the PaaS. we should point the user to this page if we experience issues while working against the PaaS (ex. when getting 500-errors?). > !openshift-status.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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12171) Add a link to the OpenShift status page in our errors

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12171?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12171: ------------------------------------- Fix Version/s: 4.2.x (was: 4.1.x) > Add a link to the OpenShift status page in our errors > ----------------------------------------------------- > > Key: JBIDE-12171 > URL: https://issues.jboss.org/browse/JBIDE-12171 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.x > > Attachments: openshift-status.png > > > OpenShift has a nice status page that informs of ongoing issues on the PaaS. we should point the user to this page if we experience issues while working against the PaaS (ex. when getting 500-errors?). > !openshift-status.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, 9 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 June 2013