February 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-13513) OpenShift description in N&N

by Stefan Bunciak (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13513?page=com.atlassian.jira.plugi... ] Stefan Bunciak closed JBIDE-13513. ---------------------------------- Verified, N&N are available to preview at http://htmlpreview.github.com/?https://github.com/jbosstools/jbosstools-d... > OpenShift description in N&N > ---------------------------- > > Key: JBIDE-13513 > URL: https://issues.jboss.org/browse/JBIDE-13513 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Alexey Kazakov > Assignee: Max Rydahl Andersen > Fix For: 4.1.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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-11417) OpenShift Express: Embedded cartridge 10gen-mms-agent-0.1

by Stefan Bunciak (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11417?page=com.atlassian.jira.plugi... ] Stefan Bunciak closed JBIDE-11417. ---------------------------------- Verified in JBoss Developer Studio Version: 7.0.0.Alpha1 Build id: Alpha1-v20130225-0422-B62 Build date: 20130225-0422 > OpenShift Express: Embedded cartridge 10gen-mms-agent-0.1 > ---------------------------------------------------------- > > Key: JBIDE-11417 > URL: https://issues.jboss.org/browse/JBIDE-11417 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.Beta3 > Reporter: Attila Nagy > Assignee: Andre Dietisheim > Labels: new_and_noteworthy > Fix For: 4.1.0.Alpha1 > > Attachments: detailled-error-msg.png, mongodb-required-for-mms.png > > > There are more problems with the embedded cartridge 10gen-mms-agent > 1) It needs MongoDB and OpenShift application wizard in JBoss Tools doesn't resolve the dependency by default. > It means that the user is not warned in advance. The new application wizard will fail and user will be unable to make the initial git clone. > 2) Actually the user is unable to embed the cartridge, because in the first round the user has to commit and push the 10gen-mss configuration file. > The main problem is: the JBoss Tools wizard only reports that there was an error during the configuration, no details are provided. > Here is the error message from JBoss Tools: > Could not embed cartridges to application php10genmms2012032701 > Could not configure application "php10genmms2012032701" at "https://ec2-50-16-87-180.compute-1.amazonaws.com/broker/embed_cartridge" > And here is the error message from the command line: > Missing settings.py file: /var/lib/stickshift/9bd1f27bba0e40f2b77fdc4b22081991/myphp2with10genmms/.openshift/mms/settings.py > This file is part of the agent zip file: 10gen-mms-agent-<group-name>.zip > The zip file is available to download from https://mms.10gen.com/ after you register with their service. > It contains your 10gen MMS credentials and is required for running the agent. > You will need to add this file and then do a git commit and push before you can embed the 10gen-mms-agent-0.1 cartridge. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13345) Hide help button from examples and quickstarts wizard (or provide some content)

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13345?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-13345: ---------------------------------- Fix Version/s: 4.1.0.Alpha2 > Hide help button from examples and quickstarts wizard (or provide some content) > ------------------------------------------------------------------------------- > > Key: JBIDE-13345 > URL: https://issues.jboss.org/browse/JBIDE-13345 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: project-examples > Affects Versions: 4.0.0.Final > Reporter: Radim Hopp > Assignee: Snjezana Peco > Priority: Optional > Fix For: 4.1.0.Alpha2 > > Attachments: help.png > > > Right now, there is help button (question mark in lower left corner) in wizards of project examples and quickstarts with no content (nothing is shown when it's clicked on). > Shouldn't we provide some basic help or hide the help button completely? > !help.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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13665) In BPEL editor design mode and source mode differs

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBIDE-13665: ----------------------------------------- Summary: In BPEL editor design mode and source mode differs Key: JBIDE-13665 URL: https://issues.jboss.org/browse/JBIDE-13665 Project: Tools (JBoss Tools) Issue Type: Bug Components: BPEL Affects Versions: 3.3.3.Final-SOA Reporter: Andrej Podhradsky Assignee: Robert (Bob) Brodt Attachments: Salutations.zip In 'If' activity the BPEL editor allows to add 'ElseIf' after 'Else'. So, the result is something like If -> Else -> ElseIf By doing this, the editor displays diagrams in this order (and also this order in in source). But when you close and reopen the bpel process the editor shows If -> ElseIf -> Else but the source includes the previous oder. This can be confusing since the editor shows something which looks good but in fact it is not. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13665) In BPEL editor design mode and source mode differs

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13665?page=com.atlassian.jira.plugi... ] Andrej Podhradsky updated JBIDE-13665: -------------------------------------- Attachment: Salutations.zip > In BPEL editor design mode and source mode differs > -------------------------------------------------- > > Key: JBIDE-13665 > URL: https://issues.jboss.org/browse/JBIDE-13665 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: BPEL > Affects Versions: 3.3.3.Final-SOA > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Attachments: Salutations.zip > > > In 'If' activity the BPEL editor allows to add 'ElseIf' after 'Else'. So, the result is something like > If > -> Else > -> ElseIf > By doing this, the editor displays diagrams in this order (and also this order in in source). But when you close and reopen the bpel process the editor shows > If > -> ElseIf > -> Else > but the source includes the previous oder. > This can be confusing since the editor shows something which looks good but in fact it is not. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-10633) No changed items were selected. Do you wish to amend the last commit?

by Stefan Bunciak (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10633?page=com.atlassian.jira.plugi... ] Stefan Bunciak closed JBIDE-10633. ---------------------------------- > No changed items were selected. Do you wish to amend the last commit? > --------------------------------------------------------------------- > > Key: JBIDE-10633 > URL: https://issues.jboss.org/browse/JBIDE-10633 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.M5 > Environment: Mac OS X Lion > Reporter: Burr Sutter > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha1 > > Attachments: Screen Shot 2012-01-13 at 1.37.47 PM.png > > > This message is problematic. It says that nothing changed, when in fact, everything changed - the project's contents are 100% different from what they were. > See video for complete workflow - > http://vimeo.com/35023638 > 1) New HTML5 Project called "test40" > 2) New OpenShift Express project called "test40" > 3) Copy existing project > 4) Team-Commit and Push -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2483) In BPEL editor design mode and source mode differs

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBDS-2483: --------------------------------------- Summary: In BPEL editor design mode and source mode differs Key: JBDS-2483 URL: https://issues.jboss.org/browse/JBDS-2483 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: SOA Tooling / Platform Affects Versions: 5.0.3.GA-SOA Reporter: Andrej Podhradsky Assignee: Robert (Bob) Brodt Attachments: Salutations.zip In 'If' activity the BPEL editor allows to add 'ElseIf' after 'Else'. So, the result is something like If -> Else -> ElseIf By doing this, the editor displays diagrams in this order (and also this order in in source). But when you close and reopen the bpel process the editor shows If -> ElseIf -> Else but the source includes the previous oder. This can be confusing since the editor shows something which looks good but in fact it is not. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2483) In BPEL editor design mode and source mode differs

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBDS-2483?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBDS-2483: ------------------------------------ Attachment: Salutations.zip > In BPEL editor design mode and source mode differs > -------------------------------------------------- > > Key: JBDS-2483 > URL: https://issues.jboss.org/browse/JBDS-2483 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: SOA Tooling / Platform > Affects Versions: 5.0.3.GA-SOA > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Attachments: Salutations.zip > > > In 'If' activity the BPEL editor allows to add 'ElseIf' after 'Else'. So, the result is something like > If > -> Else > -> ElseIf > By doing this, the editor displays diagrams in this order (and also this order in in source). But when you close and reopen the bpel process the editor shows > If > -> ElseIf > -> Else > but the source includes the previous oder. > This can be confusing since the editor shows something which looks good but in fact it is not. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13664) tracing options for openshift client not showing up not is logging working when configured

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13664?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13664: ---------------------------------------- Priority: Blocker (was: Major) > tracing options for openshift client not showing up not is logging working when configured > ------------------------------------------------------------------------------------------ > > Key: JBIDE-13664 > URL: https://issues.jboss.org/browse/JBIDE-13664 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.1.0.Alpha2 > > > tracing options in .options in openshiftclient is not showing up. > And when starting with -debug .options > and .options contains: > org.jboss.tools.openshift.express.client/debug=true > org.jboss.tools.openshift.express.client/debug/client=true > You get: > SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". > SLF4J: Defaulting to no-operation (NOP) logger implementation > SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. > Application Started: 37798 > log4j:WARN No appenders could be found for logger (com.openshift.internal.client.RestService). > log4j:WARN Please initialize the log4j system properly. > log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > So this is not working at all. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13664) tracing options for openshift client not showing up not is logging working when configured

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13664?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13664: ---------------------------------------- Description: tracing options in .options in openshiftclient is not showing up. And when starting with -debug .options and .options contains: org.jboss.tools.openshift.express.client/debug=true org.jboss.tools.openshift.express.client/debug/client=true You get: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. Application Started: 37798 log4j:WARN No appenders could be found for logger (com.openshift.internal.client.RestService). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. So this is not working at all. was: tracing options in .options in openshiftclient is not showing up and if you enable it explicitly by using -debug .options and .options contains: You get: "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. Application Started: 37798 log4j:WARN No appenders could be found for logger (com.openshift.internal.client.RestService). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info." > tracing options for openshift client not showing up not is logging working when configured > ------------------------------------------------------------------------------------------ > > Key: JBIDE-13664 > URL: https://issues.jboss.org/browse/JBIDE-13664 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha2 > > > tracing options in .options in openshiftclient is not showing up. > And when starting with -debug .options > and .options contains: > org.jboss.tools.openshift.express.client/debug=true > org.jboss.tools.openshift.express.client/debug/client=true > You get: > SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". > SLF4J: Defaulting to no-operation (NOP) logger implementation > SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. > Application Started: 37798 > log4j:WARN No appenders could be found for logger (com.openshift.internal.client.RestService). > log4j:WARN Please initialize the log4j system properly. > log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > So this is not working at all. -- 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

13 years, 1 month

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 February 2013