[JBoss JIRA] (RF-13300) Page Fragments: refine module dependencies
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13300?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč reassigned RF-13300:
-------------------------------
Assignee: Lukáš Fryč
> Page Fragments: refine module dependencies
> ------------------------------------------
>
> Key: RF-13300
> URL: https://issues.jboss.org/browse/RF-13300
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: page-fragments
> Affects Versions: 5.0.0.Alpha2
> Reporter: Lukáš Fryč
> Assignee: Lukáš Fryč
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> During the review, I have found out we may need to fine module dependencies:
> https://github.com/richfaces/richfaces/pull/55#issuecomment-27339441
> ----
> {code}
> joda-time:2.3
> - DateTime
> commons-lang:2.6
> - Validate.isTrue
> - StringEscapeUtils.unescapeJava
> json-simple:1.1.1
> - JSONParser
> org.jodah:typetools:0.3.0
> - TypeResolver.resolveRawArguments
> {code}
> I'm fine with {{DateTime}}, since it's going to be standardized - even though we may consider making it optional dependency and provide alternative in form of {{java.util.Date}}.
> I didn't found reason to leave {{Validate.isTrue}} - this should be replaced by more verbose but dependency free code.
> I did some googling for alternatives to {{StringEscapeUtils.unescapeJava}} and found out few suggestions for dependency free Java-unescaping.
> {{JSONParser}} seems to be necessary (even though we don;t use it extensively yet), but I would favor standard APIs in form of JSR-353.
> I believe {{TypeResolver}} can be re-written from scratch, but since it's one-class ASL dependency, we might consider shading it.
--
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] (RF-13325) pickList: onmouseout/onmouseover is triggered even when pointer button is not moved out/over element
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13325?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-13325:
----------------------------------
Assignee: Brian Leathem
> pickList: onmouseout/onmouseover is triggered even when pointer button is not moved out/over element
> ----------------------------------------------------------------------------------------------------
>
> Key: RF-13325
> URL: https://issues.jboss.org/browse/RF-13325
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-selects
> Affects Versions: 5.0.0.Alpha2
> Reporter: Juraj Húska
> Assignee: Brian Leathem
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> {{r:pickList}} event callback for *onmouseout* and *onmouseover* is called even when the mouse pointer does not leave the {{r:pickList}} element itself.
> I believe issue for both event handlers is the same, as both occurs when moving the mouse pointer in one of the lists (source list or target list). They should not.
--
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