May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14404) Failed to do port-forward for scalable app with embded db cartridges added

by jing zh (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14404?page=com.atlassian.jira.plugi... ] jing zh updated JBIDE-14404: ---------------------------- Attachment: JBT_port-forward.png UI for the error > Failed to do port-forward for scalable app with embded db cartridges added > -------------------------------------------------------------------------- > > Key: JBIDE-14404 > URL: https://issues.jboss.org/browse/JBIDE-14404 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Environment: JBoss Developer Studio (Branded Product) 7.0.0.Alpha2-v20130424-2146-B202 > JBoss OpenShift Tools 2.5.0.Alpha2-v20130405-1801-B39 > Reporter: jing zh > Fix For: 4.1.0.Final > > Attachments: JBT_port-forward.png, trace_port_forward.log > > > Met internal error when performing port-forwarding for scalable apps with embeded db cartridges. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14404) Failed to do port-forward for scalable app with embded db cartridges added

by jing zh (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14404?page=com.atlassian.jira.plugi... ] jing zh updated JBIDE-14404: ---------------------------- Attachment: trace_port_forward.log > Failed to do port-forward for scalable app with embded db cartridges added > -------------------------------------------------------------------------- > > Key: JBIDE-14404 > URL: https://issues.jboss.org/browse/JBIDE-14404 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Environment: JBoss Developer Studio (Branded Product) 7.0.0.Alpha2-v20130424-2146-B202 > JBoss OpenShift Tools 2.5.0.Alpha2-v20130405-1801-B39 > Reporter: jing zh > Fix For: 4.1.0.Final > > Attachments: JBT_port-forward.png, trace_port_forward.log > > > Met internal error when performing port-forwarding for scalable apps with embeded db cartridges. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14404) Failed to do port-forward for scalable app with embded db cartridges added

by jing zh (JIRA)

jing zh created JBIDE-14404: ------------------------------- Summary: Failed to do port-forward for scalable app with embded db cartridges added Key: JBIDE-14404 URL: https://issues.jboss.org/browse/JBIDE-14404 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.1.0.Alpha2 Environment: JBoss Developer Studio (Branded Product) 7.0.0.Alpha2-v20130424-2146-B202 JBoss OpenShift Tools 2.5.0.Alpha2-v20130405-1801-B39 Reporter: jing zh Fix For: 4.1.0.Final Met internal error when performing port-forwarding for scalable apps with embeded db cartridges. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-81) Update Teiid Designer to 8.1.0.Final

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-81?page=com.atlassian.jira.plugin.s... ] Andrej Podhradsky commented on JBTIS-81: ---------------------------------------- Now I'm looking at http://download.jboss.org/jbosstools/updates/integration/kepler/integrati... and I see that Teiid Designer (and also SwitchYeard) is missing. Paul, could you explain me why, please? > Update Teiid Designer to 8.1.0.Final > ------------------------------------ > > Key: JBTIS-81 > URL: https://issues.jboss.org/browse/JBTIS-81 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Andrej Podhradsky > > The update site > http://download.jboss.org/jbosstools/updates/integration/juno/integration... > now contains Teiid Designer 8.1.0.Alpha2 but there is already a final version. > Please update the designer to 8.1.0.Final. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-81) Update Teiid Designer to 8.1.0.Final

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-81?page=com.atlassian.jira.plugin.s... ] Andrej Podhradsky commented on JBTIS-81: ---------------------------------------- Hi Paul, does it mean that there will be no final JBTIS update site for Juno? By final I mean a version which can be turned into a product for JBDS. > Update Teiid Designer to 8.1.0.Final > ------------------------------------ > > Key: JBTIS-81 > URL: https://issues.jboss.org/browse/JBTIS-81 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Andrej Podhradsky > > The update site > http://download.jboss.org/jbosstools/updates/integration/juno/integration... > now contains Teiid Designer 8.1.0.Alpha2 but there is already a final version. > Please update the designer to 8.1.0.Final. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-321) NeedInfo: Why might users want to change the order of navigation rules?

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-321?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-321: ------------------------------------- Attachment: JSF_UpDownRules.png > NeedInfo: Why might users want to change the order of navigation rules? > ----------------------------------------------------------------------- > > Key: TOOLSDOC-321 > URL: https://issues.jboss.org/browse/TOOLSDOC-321 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: User Guide - JSF Tools > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Alexey Kazakov > Attachments: JSF_UpDownRules.png > > > Open a faces-config.xml file in the dedicated editor and select 'Tree' view. From the faces-config list, expand faces-config.xml and select 'Navigation Rules'. In the neighbouring pane, there is the 'from-view-id' list. Select a navigation rule and click 'Up' or 'Down' button. The navigation rules moves position in the list. Screen caption attached. > Why might a user need this function? When would they need to use it? -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-321) NeedInfo: Why might users want to change the order of navigation rules?

by Michelle Murray (JIRA)

Michelle Murray created TOOLSDOC-321: ---------------------------------------- Summary: NeedInfo: Why might users want to change the order of navigation rules? Key: TOOLSDOC-321 URL: https://issues.jboss.org/browse/TOOLSDOC-321 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Components: User Guide - JSF Tools Affects Versions: 4.1.0 Reporter: Michelle Murray Assignee: Alexey Kazakov Attachments: JSF_UpDownRules.png Open a faces-config.xml file in the dedicated editor and select 'Tree' view. From the faces-config list, expand faces-config.xml and select 'Navigation Rules'. In the neighbouring pane, there is the 'from-view-id' list. Select a navigation rule and click 'Up' or 'Down' button. The navigation rules moves position in the list. Screen caption attached. Why might a user need this function? When would they need to use it? -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14363) Creation of 'core' component in base

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14363?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-14363: ------------------------------------- The problem is that what's in common.core now is not necessarily all fit for a true core. THere's plenty of utilities that are, but also lots of classes that aren't. I honestly really like the idea of fresh starts with people consciously modifying classes for re-use and putting them somewhere new and shiny. All code must be 100% javadoc'd, api stable, a very very strong set of requirements... test cases for every single class. It's possible to do this within common, but, if we're going to do all that work, add test cases for every class, separate it into plugins based on deps, etc, why not just give it a new component name also? I think it will definitely help keep things separate. > Creation of 'core' component in base > ------------------------------------ > > Key: JBIDE-14363 > URL: https://issues.jboss.org/browse/JBIDE-14363 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.1.0.Beta1 > Reporter: Rob Stryker > Assignee: Max Rydahl Andersen > Fix For: 4.1.0.Beta1 > > > The creation of a 'core' with minimal dependencies, preferably ONLY platform, is required. The component will have the following requirements: > 1) Only code designed for re-use can live there > 2) Only fully and properly java-doc'd code can live there > 3) Only code for use by TWO OR MORE components can live there. > 4) Addition of dependencies for this component will be strictly regulated > 5) Code must be properly tested and have tests cases demonstrating it. > 6) Code relating to non-platform requirements (such as egit, maven, wtp) will receive additional bundles and features to keep these dependencies separate. FOr example: > {code} > org.jboss.tools.core.platform > org.jboss.tools.core.platform.ui > org.jboss.tools.core.wtp > org.jboss.tools.core.wtp.ui > {code} > Bundles such as these would require test bundles, as well as features that keep them separate. > {code} > org.jboss.tools.core.platform.feature > org.jboss.tools.core.wtp.feature > {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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14346) Palette - default to for HTML5 files

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14346?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-14346: -------------------------------------- Assignee: Viacheslav Kabanovich (was: Alexey Kazakov) > Palette - default to for HTML5 files > ------------------------------------ > > Key: JBIDE-14346 > URL: https://issues.jboss.org/browse/JBIDE-14346 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Burr Sutter > Assignee: Viacheslav Kabanovich > Fix For: 4.1.0.Beta1 > > Attachments: default_palette.png > > > Steps: > 1) Use the HTML5 archetype from JBoss Central > 2) Navigate to index.html > 3) double-click on index.html > 4) the file opens in the VPE but Outline is the defaulted view on the right-side > this means the average end-user will not even know that the jQuery Mobile palette is even there. > See attached screenshot. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14342) I dont get credentials reported when I create a jenkins

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14342?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-14342 at 5/8/13 4:39 PM: ------------------------------------------------------------------ With a timeout of 2 minutes, that the new client is now using (https://github.com/openshift/openshift-java-client/pull/48), creating jenkins does not timeout any more. was (Author: adietish): With a timeout of 2 minutes, that the new client is now using (https://github.com/openshift/openshift-java-client/pull/47), creating jenkins does not timeout any more. > I dont get credentials reported when I create a jenkins > ------------------------------------------------------- > > Key: JBIDE-14342 > URL: https://issues.jboss.org/browse/JBIDE-14342 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.1.0.Beta1 > > Attachments: correct-creation-log.png, no-information-from-openshift.png, null-creation-log.png, timouted-see-in-envvars.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, 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 2013