[JBoss JIRA] (JBIDE-15161) warn users that phpmyadmin may not get embedded into a scalable application
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15161?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-15161:
----------------------------------------
Labels: new_and_noteworthy (was: )
> warn users that phpmyadmin may not get embedded into a scalable application
> ---------------------------------------------------------------------------
>
> Key: JBIDE-15161
> URL: https://issues.jboss.org/browse/JBIDE-15161
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.0.CR1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha1
>
> Attachments: adding-phpmyadmin-to-scaling-2.png, adding-phpmyadmin-to-scaling-3.png, adding-phpmyadmin-to-scaling-4.png, adding-phpmyadmin-to-scaling.png, phpmyadmin-not-scalable.png
>
>
> phpmyadmin may not get embedded into a scalable application.
> # EXEC: create a scalable application on OpenShift
> # EXEC: try to embed phpmyadmin to it
> Result:
> !phpmyadmin-not-scalable.png!
> We should therefore warn the user when he tries to achieve this.
--
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, 8 months
[JBoss JIRA] (JBIDE-15653) Import application wizard: Errors "Could not publish: Attempted to begin rule"
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15653?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-15653:
------------------------------------------
reverting the above, since turns out to be a complex workaround. I'll go for a simple patch that overrides the server adapter flag:
{code}
@Override
public boolean isUseProjectSpecificSchedulingRuleOnPublish() {
// ensure we're locking the whole workspace while publishing.
return false;
}
{code}
> Import application wizard: Errors "Could not publish: Attempted to begin rule"
> ------------------------------------------------------------------------------
>
> Key: JBIDE-15653
> URL: https://issues.jboss.org/browse/JBIDE-15653
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Blocker
> Fix For: 4.2.0.Alpha1
>
> Attachments: could-not-import.png, gitignore-committed-locally.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, 8 months
[JBoss JIRA] (JBIDE-14591) Properties Tab for html elements
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14591?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-14591:
----------------------------------------
[~scabanovich], can one attribute be in multiple categories?
> Properties Tab for html elements
> --------------------------------
>
> Key: JBIDE-14591
> URL: https://issues.jboss.org/browse/JBIDE-14591
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.1.0.Beta1
> Reporter: Burr Sutter
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1
>
> Attachments: 2013-05-22_1333.png, button.png, collapsible.png, image.png, listview.png, page.png, slider.png, video.png
>
>
> The Properties Tab currently only has a General category. I would like to see us have another category where we have identified the most used jQuery/jQuery mobile widget properties such as:
> id (always at the top)
> data-role
> data-icon
> data-iconpos
> other data-* set of properties
> value (for input fields, value is pretty important)
> type (for input fields, critical)
> placeholder
> The available properties can be more extensive than what was originally shown in the wizard/dialog when the widget was dragged from the palette. Any property deemed important enough to show in the wizard/dialog should also be promoted into this new category.
> My proposal for the category name: jQuery
--
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, 8 months
[JBoss JIRA] (JBIDE-12812) Provide user-friendly way to increase Git timeout
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12812?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-12812:
----------------------------------------
As EGit default timeout is 30 and OpenShift requires at least 60 for good first impression, I would agree with [~maxandersen] that it makes sense to have 2 preferences: one for OpenShift (default 60 or more), and one for EGit (default 30). If the OpenShift preference is unset, OpenShift would use the default from EGit.
> Provide user-friendly way to increase Git timeout
> -------------------------------------------------
>
> Key: JBIDE-12812
> URL: https://issues.jboss.org/browse/JBIDE-12812
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.0.0.Alpha1
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.2.0.Alpha1
>
> Attachments: pushtimeout.png
>
>
> With the default timeout (30s) everytime I follow these steps I get an TimoutException:
> * Import rich-faces project from JBoss Central
> * Create application on OpenShift and merge it with the rich-faces project
> * Select the project - context menu - Team - Push to Upstream
> * Timeout Exception:
> !pushtimeout.png|thumbnail!
> So we should provide a link to
> {code}Preferences - Team - Git - Remote connection timeout{code} to prevent JBIDE-12430 with some basic explanation of the most probable situation - that the timeout is set too small (like when timed out while creating 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, 8 months