[JBoss JIRA] (JBIDE-22695) Environment Variables of application deployment should have different workflow
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-22695?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-22695:
-------------------------------------
Priority: Major (was: Critical)
> Environment Variables of application deployment should have different workflow
> ------------------------------------------------------------------------------
>
> Key: JBIDE-22695
> URL: https://issues.jboss.org/browse/JBIDE-22695
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM1
> Reporter: Marián Labuda
> Priority: Major
> Labels: env_var_wizard, openshift_v3
> Fix For: 4.12.x
>
>
> Reset All button in Environment Var wizard dialog should get application to default state. At the moment it reset environment variables in the table just to the values at the point of opening the wizard. If I would delete some environment variables and confirm changes, but I would find out I broke something and I would like to rollback it to original state, I would try to reset it with Reset All button. But it won't work for me. This is causing the more serious issue:
> Because we edit same deployment configuration and start deployments from it and in the same time we set number of replicas in other deployment configs to zero. So we don't have the original deployment config and thus we cannot rollback easily (well there is a way but nasty one - edit replication controller, copy and paste environment variables to the deployment config, save it and deploy latest).
> There are 2 options:
> a) Create a new deployment configuration for a new (modified) set of environment variables and create a new replication controller (deployment) from this deployment configuration. There is one con - it can lead to many deployment configurations and replication controllers (for each deployment configuration there would be one replication controller).
> b) Just edit current replication controller (deployment) of an application or create a new one from an existing but with modified env. vars and with correct amount of replicas and set replicas in the previous to 0. And then let respin pods with correct setup. One of those approaches (create/edit RC) would be, I think, more satisfying.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-11172) Database Development: Postgres 9.1 tables are not listed
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-11172?page=com.atlassian.jira.plugi... ]
André Dietisheim commented on JBIDE-11172:
------------------------------------------
[~koen.aers] is this still a valid issue?
> Database Development: Postgres 9.1 tables are not listed
> --------------------------------------------------------
>
> Key: JBIDE-11172
> URL: https://issues.jboss.org/browse/JBIDE-11172
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate, upstream
> Environment: Mac OS X Lion
> Reporter: Burrsitis Sutter
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.12.x
>
> Attachments: Screen Shot 2012-03-05 at 7.52.01 PM.png, Screen Shot 2012-03-05 at 7.55.21 PM.png, Screen Shot 2012-03-05 at 8.00.22 PM.png, Screen Shot 2012-03-05 at 8.00.38 PM.png, pagila-ds.xml, postgresql-9.1-901.jdbc4.jar
>
>
> Postgres 9.1 - connection to a pagila database schema does not return a list of tables in the database explorer, nor in the Hibernate configuration. See attached screenshots.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-17443) CordovaSim crash on Fedora 20 when browsing a jQueryMobile based app
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-17443?page=com.atlassian.jira.plugi... ]
André Dietisheim commented on JBIDE-17443:
------------------------------------------
[~jeffmaury] not even sure if this is still an issue. This was early when GTK3 was in it's early stages and FC20 a new'ish distro. Not even sure if we can even reproduce this. Given that cordovasim was deprecated, shouldnt we close this as WONTDO or OUTDATED?
> CordovaSim crash on Fedora 20 when browsing a jQueryMobile based app
> --------------------------------------------------------------------
>
> Key: JBIDE-17443
> URL: https://issues.jboss.org/browse/JBIDE-17443
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cordovasim
> Affects Versions: 4.2.0.Beta1
> Environment: Fedora 20
> JBoss Developer Studio 8.0.0.Beta1
> webkitgtk-2.2.7-1.fc20.x86_64
> Reporter: Vineet Reynolds
> Assignee: Ilya Buziuk
> Priority: Major
> Fix For: 4.12.x
>
>
> The root cause appears to be whatever is causing JBIDE-17442 to manifest. Raising this to track CordovaSim behavior, since it relies on the BrowserSim component.
> CordovaSim crashes when launching the TicketMonster app (from WFK 2.6). The offending line of code seems to be :
> {noformat}
> $("#container").enhanceWithin();
> {noformat}
> in the mobile {{router.js}}. The [enhanceWithin API|http://api.jquerymobile.com/enhanceWithin/] is new in jQueryMobile 1.4.x. The same line works without any flaw in CordovaSim on Windows and Mac OS X.
> Additional notes - strace output reveals that BrowserSim is terminated due to a SIGTRAP event, which is a bit weird.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-17944) BrowserSim: Use http: protocol instead of file: for accessing local files
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-17944?page=com.atlassian.jira.plugi... ]
André Dietisheim commented on JBIDE-17944:
------------------------------------------
[~jeffmaury] given that cordovasim was deprecated, shouldnt we close this as WONTDO or OUTDATED?
> BrowserSim: Use http: protocol instead of file: for accessing local files
> -------------------------------------------------------------------------
>
> Key: JBIDE-17944
> URL: https://issues.jboss.org/browse/JBIDE-17944
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim, cordovasim
> Affects Versions: 4.2.2.Final
> Reporter: Alexey Kazakov
> Assignee: Ilya Buziuk
> Priority: Major
> Fix For: 4.12.x
>
> Attachments: ripple.png
>
>
> Currently, BrowserSim works through file: protocol but this protocol doesn't work well with paths relative to the webroot (which start with "/").
> So if a local file contains any links to local resources (css, js, ...) via relative paths then these resources are not available in BrowserSim.
> For example all official ionic example projects use such paths. It makes "open with BrowserSim" feature useless for those projects.
> It would be great if BrowserSim uses http: as our HTML5 preview does.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months