[JBoss JIRA] (RF-13778) RF-45 cyclic dependency on richfaces-parent
by Pavel Slegr (JIRA)
[ https://issues.jboss.org/browse/RF-13778?page=com.atlassian.jira.plugin.s... ]
Pavel Slegr commented on RF-13778:
----------------------------------
Actually, when I removed the dependency on richfaces-parent in .../jsf-tests/pom.xml and define the correct properties (I tried to use the whole bunch of those defined in the former parent) then I was able to build jsf-tests successfully
> RF-45 cyclic dependency on richfaces-parent
> -------------------------------------------
>
> Key: RF-13778
> URL: https://issues.jboss.org/browse/RF-13778
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Affects Versions: 4.5.0.Alpha3
> Reporter: Pavol Pitonak
> Priority: Blocker
> Fix For: 4.5.0.Beta1
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Historically there is a dependency in .../jsf-tests/pom.xml on richfaces-parent which used to be a standalone project/repo in 4.3.x
> {code}
> <parent>
> <groupId>org.richfaces</groupId>
> <artifactId>richfaces-parent</artifactId>
> <version>12</version>
> </parent>
> {code}
> However nowadays in 4.5.x there is playing the role of parent the
> richfaces/pom.xml
> https://github.com/richfaces/richfaces/blob/master/pom.xml
> {code}
> <groupId>org.richfaces</groupId>
> <artifactId>richfaces-parent</artifactId>
> <packaging>pom</packaging>
> <version>4.5.0-SNAPSHOT</version>
> <name>RichFaces Parent</name>
> {code}
> which makes a cyclic dependency
> jsf-test --> richfaces --> jsf-test
> as there are inside https://github.com/richfaces/richfaces/blob/master/build/pom.xml
> referenced dependencies for jsf-tests
> {code}
> <dependency>
> <groupId>org.jboss.test-jsf</groupId>
> <artifactId>htmlunit-client</artifactId>
> <version>${version.jsf-test}</version>
> <exclusions>
> <exclusion>
> <groupId>javax.servlet</groupId>
> <artifactId>javax.servlet-api</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
> <dependency>
> <groupId>org.jboss.test-jsf</groupId>
> <artifactId>jsf-test-stage</artifactId>
> <version>${version.jsf-test}</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.test-jsf</groupId>
> <artifactId>jsf-mock</artifactId>
> <version>${version.jsf-test}</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.test-jsf</groupId>
> <artifactId>jsf-mockito</artifactId>
> <version>${version.jsf-test}</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.test-jsf</groupId>
> <artifactId>jsf-test-scriptunit</artifactId>
> <version>${version.jsf-test}</version>
> </dependency>
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 3 months
[JBoss JIRA] (RF-11453) Add autocomplete functionality to the rich:select component
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-11453?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-11453:
------------------------------------
Based on a conversation with [~clerum] in IRC, I've changed the implementation to use the _itemValue_ and _itemLabel_ attributes and dynamically build the list of selectItems (as is currently done in the orderingList) using the autocompleteMethod as an object source, and the _var_ attribute.
We can then use this same approach to build the single selectItem when the select backing bean already has a value. This last bit specifically addresses the concern [~clerum] raised in the above comment.
> Add autocomplete functionality to the rich:select component
> -----------------------------------------------------------
>
> Key: RF-11453
> URL: https://issues.jboss.org/browse/RF-11453
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-selects
> Reporter: Cody Lerum
> Assignee: Brian Leathem
> Fix For: 4.5.0.Beta1
>
> Original Estimate: 3 days
> Time Spent: 2 days
> Remaining Estimate: 1 day
>
> Add an "autocompleteMethod" to rich:select
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 3 months