[JBoss JIRA] (JBIDE-16039) Environment variables persists in manager after delete
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16039?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16039:
-------------------------------------
Steps to Reproduce:
# ASSERT: Have connection with domain and app on server supporting environment variables.
# EXEC: Open application context menu and choose Edit environment variables
# EXEC: Create new environment variable and close wizard
# ASSERT: new environment variable is listed
# EXEC: Open Edit environment variables and remove that environment variable. Close wizard
# ASSERT: Open Edit environment variables and assert that variable is not presented there too.
In last assert environment variable is shown in table of variables, although it has been successfully removed.
Screenshot has been taken in last assert
!env_vars_bug.png!
was:
# ASSERT: Have connection with domain and app on server supporting environment variables.
# EXEC: Open application context menu and choose Edit environment variables
# EXEC: Create new environment variable.
# EXEC: Show all environment variables
# ASSERT: New variable is shown.
# EXEC: Open Edit environment variables and remove that environment variable.
# EXEC: Show all environment variables
# ASSERT: Removed variable is not presented
# ASSERT: Open Edit environment variables and assert that variable is not presented there too.
In last assert environment variable is shown in table of variables, although it has been successfully removed.
Screenshot has been taken in last assert
!env_vars_bug.png!
> Environment variables persists in manager after delete
> ------------------------------------------------------
>
> Key: JBIDE-16039
> URL: https://issues.jboss.org/browse/JBIDE-16039
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Attachments: env_vars_bug.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, 5 months
[JBoss JIRA] (JBIDE-14597) ng-app AngularJS
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14597?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-14597:
-----------------------------------------
Do we need some preference page to control the exclusion of ng-* attributes from the validation? Or we have just to ignore these attributes at all?
> ng-app AngularJS
> ----------------
>
> Key: JBIDE-14597
> URL: https://issues.jboss.org/browse/JBIDE-14597
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing, upstream
> Reporter: Burr Sutter
> Assignee: Victor Rubezhny
> Priority: Critical
> Fix For: 4.2.x
>
> Attachments: 2013-05-23_0752.png, 2013-05-23_1548.png, html5_demo.fsh, Screen Shot 2013-05-23 at 3.51.53 PM.png
>
>
> Warning:
> Undefined attribute name (ng-app).
> Undefined attribute name (ng-controller).
> AngularJS is part of the new HTML5 Scaffolding feature in Forge 1.3
> forge install-plugin angularjs
--
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, 5 months