[JBoss JIRA] (JBIDE-22371) Allow users easily manage environment variables of OpenShift application
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-22371:
-------------------------------------
Summary: Allow users easily manage environment variables of OpenShift application
Key: JBIDE-22371
URL: https://issues.jboss.org/browse/JBIDE-22371
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.4.0.Alpha2
Reporter: Marián Labuda
Priority: Minor
At the moment to add a new environment variable/edit an existing one. Environment variables are located at deployment configuration. At the moment it requires to open Properties view, select a deployment config, open context menu Edit... and find in json where the spot with env. vars is located and add more key:value pair or edit existing ones. It would be nice if we would have some dialog/wizard to easily manage variables.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22371) Allow users easily manage environment variables of OpenShift application
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22371?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22371:
----------------------------------
Labels: openshift_v3 (was: )
> Allow users easily manage environment variables of OpenShift application
> ------------------------------------------------------------------------
>
> Key: JBIDE-22371
> URL: https://issues.jboss.org/browse/JBIDE-22371
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Priority: Minor
> Labels: openshift_v3
>
> At the moment to add a new environment variable/edit an existing one. Environment variables are located at deployment configuration. At the moment it requires to open Properties view, select a deployment config, open context menu Edit... and find in json where the spot with env. vars is located and add more key:value pair or edit existing ones. It would be nice if we would have some dialog/wizard to easily manage variables.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22283) reveng *.java emitter does not escape java keyword 'return' as variable name
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22283?page=com.atlassian.jira.plugi... ]
Koen Aers reassigned JBIDE-22283:
---------------------------------
Assignee: Koen Aers
> reveng *.java emitter does not escape java keyword 'return' as variable name
> ----------------------------------------------------------------------------
>
> Key: JBIDE-22283
> URL: https://issues.jboss.org/browse/JBIDE-22283
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.3.x
> Environment: Eclipse Mars
> Reporter: Darryl Miles
> Assignee: Koen Aers
>
> reveng *.java emitter does not escape java keyword 'return' as variable name
> <table name="oc_return_history">
> <foreign-key constraint-name="FK_oc_return_history__return_id" foreign-table="oc_return">
> <column-ref local-column="return_id" foreign-column="return_id"/>
> <!-- this breaks the generator trying to name local variable as a java keyword -->
> <many-to-one property="return"/>
> </foreign-key>
> </table>
> The expected output would be:
> private Return _return;
> but actual output is:
> private Return return;
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBTIS-709) Extend SmokeTests for Fuse Tooling
by Tomáš Sedmík (JIRA)
[ https://issues.jboss.org/browse/JBTIS-709?page=com.atlassian.jira.plugin.... ]
Tomáš Sedmík closed JBTIS-709.
------------------------------
Resolution: Duplicate Issue
> Extend SmokeTests for Fuse Tooling
> ----------------------------------
>
> Key: JBTIS-709
> URL: https://issues.jboss.org/browse/JBTIS-709
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: Fuse IDE, QE
> Affects Versions: 4.3.0.Final
> Reporter: Andrej Podhradsky
> Assignee: Tomáš Sedmík
>
> Extend SmokeTests for Fuse Tooling so that they will take no more than 30 minutes. Also improve the performance of the tests as follows:
> 1. Do not use any runtime
> 2. Do not set any preferences via dialog 'Preferences' (instead of that set them via direct API)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months