[JBoss JIRA] (RF-12784) Showcase readme - update deployment from eclipse part
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12784?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12784:
-------------------------------
Fix Version/s: 4.3.1
> Showcase readme - update deployment from eclipse part
> -----------------------------------------------------
>
> Key: RF-12784
> URL: https://issues.jboss.org/browse/RF-12784
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: doc, showcase
> Affects Versions: 4.3.0.Final, 5-Tracking
> Reporter: Juraj Húska
> Priority: Trivial
> Fix For: 4.3.1
>
>
> The deployment of the showcase from eclipse needs to be written down in in more details, because it is not trivial:
> An user needs to be aware of:
> * select correct maven profile
> * alter the deployment assembly
> * be aware of wrong context root load in the eclipse browser
> I will send pull request for this one.
--
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
11 years, 4 months
[JBoss JIRA] (RF-12781) The kitchensink-rf quickstart uses obsolete property names and values
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12781?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12781:
-------------------------------
Fix Version/s: 4.3.1
> The kitchensink-rf quickstart uses obsolete property names and values
> ----------------------------------------------------------------------
>
> Key: RF-12781
> URL: https://issues.jboss.org/browse/RF-12781
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Reporter: Sande Gilda
> Fix For: 4.3.1
>
>
> The POM file currently contains:
> {code}
> <jboss.as.plugin.version>7.1.1.Final</jboss.as.plugin.version>
> {code}
> The correct name/value is:
> {code}
> <version.org.jboss.as.plugins.maven.plugin>7.3.Final</version.org.jboss.as.plugins.maven.plugin>
> {code}
> It also defines:
> {code}
> <!-- Define the version of the JBoss BOMs we want to import. The
> JBoss BOMs specify tested stacks. -->
> <jboss.bom.version>1.0.0.Final</jboss.bom.version>
> <!-- Alternatively, comment out the above line, and un-comment the
> line below to use version 1.0.2.Final-redhat-1 which is a release
> certified to work with JBoss EAP 6. It requires you have access
> to the JBoss EAP 6 maven repository. -->
> <!-- <jboss.bom.version>1.0.2.Final-redhat-1</jboss.bom.version> -->
> {code}
> That section should be defined as follows:
> {code}
> <!-- Define the version of the JBoss BOMs we want to import to specify tested stacks. -->
> <version.org.jboss.bom>1.0.4.Final</version.org.jboss.bom>
> <!-- Alternatively, comment out the above line, and un-comment the
> line below to use version 1.0.4.Final-redhat-1 which is a release certified
> to work with JBoss EAP 6. It requires you have access to the JBoss EAP 6
> maven repository. -->
> <!-- <version.org.jboss.bom>1.0.4.Final-redhat-1</version.org.jboss.bom> -->
> {code}
--
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
11 years, 4 months
[JBoss JIRA] (RF-12781) The kitchensink-rf quickstart uses obsolete property names and values
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12781?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12781:
-------------------------------
Description:
The POM file currently contains:
{code}
<jboss.as.plugin.version>7.1.1.Final</jboss.as.plugin.version>
{code}
The correct name/value is:
{code}
<version.org.jboss.as.plugins.maven.plugin>7.3.Final</version.org.jboss.as.plugins.maven.plugin>
{code}
It also defines:
{code}
<!-- Define the version of the JBoss BOMs we want to import. The
JBoss BOMs specify tested stacks. -->
<jboss.bom.version>1.0.0.Final</jboss.bom.version>
<!-- Alternatively, comment out the above line, and un-comment the
line below to use version 1.0.2.Final-redhat-1 which is a release
certified to work with JBoss EAP 6. It requires you have access
to the JBoss EAP 6 maven repository. -->
<!-- <jboss.bom.version>1.0.2.Final-redhat-1</jboss.bom.version> -->
{code}
That section should be defined as follows:
{code}
<!-- Define the version of the JBoss BOMs we want to import to specify tested stacks. -->
<version.org.jboss.bom>1.0.4.Final</version.org.jboss.bom>
<!-- Alternatively, comment out the above line, and un-comment the
line below to use version 1.0.4.Final-redhat-1 which is a release certified
to work with JBoss EAP 6. It requires you have access to the JBoss EAP 6
maven repository. -->
<!-- <version.org.jboss.bom>1.0.4.Final-redhat-1</version.org.jboss.bom> -->
{code}
was:
The POM file currently contains:
<jboss.as.plugin.version>7.1.1.Final</jboss.as.plugin.version>
The correct name/value is: <version.org.jboss.as.plugins.maven.plugin>7.3.Final</version.org.jboss.as.plugins.maven.plugin>
It also defines:
<!-- Define the version of the JBoss BOMs we want to import. The
JBoss BOMs specify tested stacks. -->
<jboss.bom.version>1.0.0.Final</jboss.bom.version>
<!-- Alternatively, comment out the above line, and un-comment the
line below to use version 1.0.2.Final-redhat-1 which is a release
certified to work with JBoss EAP 6. It requires you have access
to the JBoss EAP 6 maven repository. -->
<!-- <jboss.bom.version>1.0.2.Final-redhat-1</jboss.bom.version> -->
That section should be defined as follows:
<!-- Define the version of the JBoss BOMs we want to import to specify tested stacks. -->
<version.org.jboss.bom>1.0.4.Final</version.org.jboss.bom>
<!-- Alternatively, comment out the above line, and un-comment the
line below to use version 1.0.4.Final-redhat-1 which is a release certified
to work with JBoss EAP 6. It requires you have access to the JBoss EAP 6
maven repository. -->
<!-- <version.org.jboss.bom>1.0.4.Final-redhat-1</version.org.jboss.bom> -->
> The kitchensink-rf quickstart uses obsolete property names and values
> ----------------------------------------------------------------------
>
> Key: RF-12781
> URL: https://issues.jboss.org/browse/RF-12781
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: examples
> Reporter: Sande Gilda
>
> The POM file currently contains:
> {code}
> <jboss.as.plugin.version>7.1.1.Final</jboss.as.plugin.version>
> {code}
> The correct name/value is:
> {code}
> <version.org.jboss.as.plugins.maven.plugin>7.3.Final</version.org.jboss.as.plugins.maven.plugin>
> {code}
> It also defines:
> {code}
> <!-- Define the version of the JBoss BOMs we want to import. The
> JBoss BOMs specify tested stacks. -->
> <jboss.bom.version>1.0.0.Final</jboss.bom.version>
> <!-- Alternatively, comment out the above line, and un-comment the
> line below to use version 1.0.2.Final-redhat-1 which is a release
> certified to work with JBoss EAP 6. It requires you have access
> to the JBoss EAP 6 maven repository. -->
> <!-- <jboss.bom.version>1.0.2.Final-redhat-1</jboss.bom.version> -->
> {code}
> That section should be defined as follows:
> {code}
> <!-- Define the version of the JBoss BOMs we want to import to specify tested stacks. -->
> <version.org.jboss.bom>1.0.4.Final</version.org.jboss.bom>
> <!-- Alternatively, comment out the above line, and un-comment the
> line below to use version 1.0.4.Final-redhat-1 which is a release certified
> to work with JBoss EAP 6. It requires you have access to the JBoss EAP 6
> maven repository. -->
> <!-- <version.org.jboss.bom>1.0.4.Final-redhat-1</version.org.jboss.bom> -->
> {code}
--
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
11 years, 4 months
[JBoss JIRA] (RF-12779) dropdown menu onclick event
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12779?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12779:
-------------------------------
Labels: waiting_on_user (was: )
> dropdown menu onclick event
> ---------------------------
>
> Key: RF-12779
> URL: https://issues.jboss.org/browse/RF-12779
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Environment: microsoft xp
> Reporter: Deepak Salve
> Labels: waiting_on_user
>
> In my project i have toolbar.
> On that toolbar I have added 4 menus.
> in that 4 menus 2 menu have sub menu items and working fine.
> but for other, they dont have submenu.
> i want to navigate to other page on clicking that menu itself.
> but currently there is no onclick event so how should manage that click operation.
--
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
11 years, 4 months
[JBoss JIRA] (RF-12779) dropdown menu onclick event
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12779?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-12779:
------------------------------------
Can you include some sample code demonstrating what you are trying to achieve? Also, try asking on the user forum, as you are likely to get a more timely response for what sounds like a common use case.
> dropdown menu onclick event
> ---------------------------
>
> Key: RF-12779
> URL: https://issues.jboss.org/browse/RF-12779
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Environment: microsoft xp
> Reporter: Deepak Salve
>
> In my project i have toolbar.
> On that toolbar I have added 4 menus.
> in that 4 menus 2 menu have sub menu items and working fine.
> but for other, they dont have submenu.
> i want to navigate to other page on clicking that menu itself.
> but currently there is no onclick event so how should manage that click operation.
--
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
11 years, 4 months
[JBoss JIRA] (RF-12777) rich:picklist restriction
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12777?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12777:
-------------------------------
Fix Version/s: 5-Tracking
> rich:picklist restriction
> -------------------------
>
> Key: RF-12777
> URL: https://issues.jboss.org/browse/RF-12777
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-selects
> Affects Versions: 4.2.3.Final
> Environment: ie browser
> Reporter: Shireen O
> Labels: picklist
> Fix For: 5-Tracking
>
>
> Hello,
> I have 3 issues related to rich:picklist component, and I need solution immediately:-
> 1- I wanna add tooltip for selected item in both source and target lists,
> because not all item data is shown clear,and I am restricted with list width.
> 2- I wanna add horizontal scroll for source & target lists alone, Not for the whole rich:picklist component. Only the vertical scroll is appear.
> 3- When I changed style for selected item using selectItemClass property,
> the move controls (Add & Remove) are disabled, I need them to be enabled.
--
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
11 years, 4 months