[JBoss JIRA] (JBDS-2739) Support per-application environment variables for OpenShift
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2739?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2739:
--------------------------------------
Priority: Blocker (was: Critical)
> Support per-application environment variables for OpenShift
> -----------------------------------------------------------
>
> Key: JBDS-2739
> URL: https://issues.jboss.org/browse/JBDS-2739
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: openshift
> Reporter: Andy Goldstein
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: openshift
>
> OpenShift will soon add support for per-application environment variables. This includes:
> - specifying 1 or more environment variables at app creation
> - adding 1 or more environment variables to an app
> - deleting 1 or more environment variables from an app
> - listing an app's environment variables
> - showing the values of 1 or more environment variables for an app
--
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, 6 months
[JBoss JIRA] (JBDS-2738) Support OpenShift 2.0 features
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2738?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2738:
--------------------------------------
Priority: Blocker (was: Major)
> Support OpenShift 2.0 features
> ------------------------------
>
> Key: JBDS-2738
> URL: https://issues.jboss.org/browse/JBDS-2738
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Priority: Blocker
>
> OpenShift 2.0 is coming, needs to investigate when that happens and what it implies for eclipse (and eventually Forge) tooling.
> This functionallity would need to be added without breaking how we work with current openshift online and openshift enterprise which has 1.x api's.
> Opening this issue to track issues related to this (please create subtasks)
--
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, 6 months
[JBoss JIRA] (JBDS-2738) Support OpenShift 2.0 features
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-2738?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-2738:
-----------------------------
CDW release: ?
> Support OpenShift 2.0 features
> ------------------------------
>
> Key: JBDS-2738
> URL: https://issues.jboss.org/browse/JBDS-2738
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Priority: Blocker
>
> OpenShift 2.0 is coming, needs to investigate when that happens and what it implies for eclipse (and eventually Forge) tooling.
> This functionallity would need to be added without breaking how we work with current openshift online and openshift enterprise which has 1.x api's.
> Opening this issue to track issues related to this (please create subtasks)
--
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, 6 months
[JBoss JIRA] (JBDS-2740) Support multiple namespaces in OpenShift
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2740?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2740:
--------------------------------------
Priority: Critical (was: Major)
> Support multiple namespaces in OpenShift
> ----------------------------------------
>
> Key: JBDS-2740
> URL: https://issues.jboss.org/browse/JBDS-2740
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: openshift
> Reporter: Andy Goldstein
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift
> Attachments: namespace.png
>
>
> OpenShift will soon add support for a user to have access to multiple namespaces. This includes:
> - a user creates and owns multiple namespaces
> - a user has permission to work with a domain owned by another user (with differing permission levels)
--
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, 6 months
[JBoss JIRA] (JBDS-2739) Support per-application environment variables for OpenShift
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2739?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2739:
--------------------------------------
Priority: Critical (was: Major)
> Support per-application environment variables for OpenShift
> -----------------------------------------------------------
>
> Key: JBDS-2739
> URL: https://issues.jboss.org/browse/JBDS-2739
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: openshift
> Reporter: Andy Goldstein
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: openshift
>
> OpenShift will soon add support for per-application environment variables. This includes:
> - specifying 1 or more environment variables at app creation
> - adding 1 or more environment variables to an app
> - deleting 1 or more environment variables from an app
> - listing an app's environment variables
> - showing the values of 1 or more environment variables for an app
--
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, 6 months
[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by seb win (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
seb win commented on JBIDE-2720:
--------------------------------
Hi,
I faced the same issue I used process explorer and found that it was using the one located in c:\windows\System32 I have an other one in c:\windows\SysWOW64 i assume that eclipse should use the last one but I don't know how to configure it. Can you please help ?
Many thnaks
> Need 64-bit windows support
> ---------------------------
>
> Key: JBIDE-2720
> URL: https://issues.jboss.org/browse/JBIDE-2720
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha
> Reporter: Samuel Mendenhall
> Assignee: Yahor Radtsevich
> Fix For: 4.1.x
>
> Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1, mozconfig2, vpe-win-jdk64.png
>
>
> If you use a 64-bit JVM, the XULRunner parts of JBoss Tools does not load.
> We should look into providing a xulrunner for Windows 64-bit.
> *Update:*
> In JBoss Tools 4.1.0 and JBoss Developer Studio 7.0.0 XULRunner for 64-bit Windows is provided via experimental update site: http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulr...
> {color:red}*Known problems:*{color}
> * XULRunner for 64-bit Windows is incompatible with Intel OpenCL SDK
> *If you get [R6034 error|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=1277169...] you may:*
> * Try to uninstall Intel OpenCL SDK
> * *OR* Disable XULRunner by adding the option {{-Dorg.jboss.tools.vpe.loadxulrunner=false}} to the {{eclipse.ini}} (or {{jbdevstudio.ini}} if you use JBoss Developer Studio)
> If you do not have Intel OpenCL SDK installed but still getting the R6034 error, we will very appreciate if you run Process Explorer as described in [this comment|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=12772...] and help us to find conflicting library.
--
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, 6 months
[JBoss JIRA] (JBIDE-15593) WS Tester should put a warning when parameter is not valid
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15593?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-15593:
-------------------------------------------
Really? Why do we want to allow users to shoot themselves in the foot like that?
> WS Tester should put a warning when parameter is not valid
> ----------------------------------------------------------
>
> Key: JBIDE-15593
> URL: https://issues.jboss.org/browse/JBIDE-15593
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: webservices
> Affects Versions: 4.1.0.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.1.1.Beta1
>
>
> WS Tester input parameter dialog should display a warning and not prevent dialog close instead of displaying an error if the value of a parameter is not compatible with its type.
> User should be allowed to submit the request with bad parameters if she really wants to.
--
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, 6 months