[JBoss JIRA] (JBIDE-16272) Having both RichFaces 4.5 and 5.x taglibs in one JSF project malfunction components auto completion
by Juraj Húska (JIRA)
Juraj Húska created JBIDE-16272:
-----------------------------------
Summary: Having both RichFaces 4.5 and 5.x taglibs in one JSF project malfunction components auto completion
Key: JBIDE-16272
URL: https://issues.jboss.org/browse/JBIDE-16272
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsf
Affects Versions: 4.1.0.1.Final
Reporter: Juraj Húska
When I create new JSF project, where I add RichFaces libraries needed to create _RichFaces 4.5_ (a special version which should be some kind of bridge between RichFaces 4 and 5) application:
* richfaces-5.0.0.Alpha2.jar
* richfaces-components-a4j-4.5.0.Alpha1.jar
* richfaces-components-rich-4.5.0.Alpha1.jar
Then if you have all supported namespaces included, auto completion triggered e.g. on {{<a4j:}} will provides also non existing components, like {{<a4j:calendar}} (it should be {{<rich:calendar}} )
Please see steps to reproduce.
--
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, 4 months
[JBoss JIRA] (JBIDE-15380) EGit: Show Git Hooks output and reset timeout when a new receiving new output (WATCHER)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15380?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15380:
-------------------------------------
Summary: EGit: Show Git Hooks output and reset timeout when a new receiving new output (WATCHER) (was: EGit: Show Git Hooks output and reset timeout when a new receiving new output (WATCHER=)
> EGit: Show Git Hooks output and reset timeout when a new receiving new output (WATCHER)
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-15380
> URL: https://issues.jboss.org/browse/JBIDE-15380
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.1.0.Final
> Reporter: Mickael Istria
> Assignee: Andre Dietisheim
> Fix For: LATER
>
>
> When pushing to Openshift with JBT, it is very common to get a Timeout because the hooks take too much time to run.
> Instead of this simple timeout, I'd rather see:
> * The hooks output shown in the push dialog
> * The timeout counting time since the last received output message (by monitoring at the inputStream I guess) instead of counting time since the push was triggered.
--
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, 4 months
[JBoss JIRA] (JBIDE-11881) Explorer, Properties: Display application state
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11881?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-11881:
-------------------------------------
Fix Version/s: LATER
(was: 4.2.x)
> Explorer, Properties: Display application state
> -----------------------------------------------
>
> Key: JBIDE-11881
> URL: https://issues.jboss.org/browse/JBIDE-11881
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Beta3
> Reporter: Xavier Coulon
> Assignee: Andre Dietisheim
> Labels: explorer, new_and_noteworthy, properties
> Fix For: LATER
>
>
> From Bugzilla#805989
> The state of the application on each gear can be checked using the gear_groups
> rest api.
> /broker/rest/domains/<domain-name>/applications/<app-name>/gear_groups
> This rest call reflects the state of the application on each gear based on the
> contents of the file $OPENSHIFT_GEAR_DIR/runtime/.state
> The following states should be tracked in ~/runtime/.state
> stopped
> building
> deploying
> started
> idle
> unknown
--
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, 4 months
[JBoss JIRA] (JBIDE-11881) Explorer, Properties: Display application state
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11881?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-11881:
------------------------------------------
bumping to LATER since it is unlikely that we'll have the time to implement this in the near future, there are many more items with higher priorities.
> Explorer, Properties: Display application state
> -----------------------------------------------
>
> Key: JBIDE-11881
> URL: https://issues.jboss.org/browse/JBIDE-11881
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Beta3
> Reporter: Xavier Coulon
> Assignee: Andre Dietisheim
> Labels: explorer, new_and_noteworthy, properties
> Fix For: LATER
>
>
> From Bugzilla#805989
> The state of the application on each gear can be checked using the gear_groups
> rest api.
> /broker/rest/domains/<domain-name>/applications/<app-name>/gear_groups
> This rest call reflects the state of the application on each gear based on the
> contents of the file $OPENSHIFT_GEAR_DIR/runtime/.state
> The following states should be tracked in ~/runtime/.state
> stopped
> building
> deploying
> started
> idle
> unknown
--
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, 4 months