[JBoss JIRA] Created: (RFPL-1413) Develop sandbox workspace for reproducing bugs
by Lukas Fryc (JIRA)
Develop sandbox workspace for reproducing bugs
----------------------------------------------
Key: RFPL-1413
URL: https://issues.jboss.org/browse/RFPL-1413
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
Components: features
Reporter: Lukas Fryc
Fix For: 4.Future
Currently, many forum issues contains difficult to reproduce conditions, it may be worth to provide developers application for quick starting bug reproduction sample:
We should provide both:
1. archetype
2. prepared workspace
We can publish workspace on GitHub repository, from which can developers fork.
They can provide branch or tag which reproduces issue separately from their env.
Following aspects should be provided in sample application:
* complex model for iteration
** needs to be modifiable
** possibly JPA entities
Additionally, we need to announce such example and provide following tools to support it:
* how-to use it
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 12 months
[JBoss JIRA] Created: (RFPL-1253) components: effects support to be added
by Ilya Shaikovsky (JIRA)
components: effects support to be added
---------------------------------------
Key: RFPL-1253
URL: https://issues.jboss.org/browse/RFPL-1253
Project: RichFaces Planning
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: components
Reporter: Ilya Shaikovsky
Priority: Critical
Fix For: 4.Next
Need to review subj and define tasks (analysis, specifications, impls)
That's are really big one and frequently asked ehcancement so should be carefully designed prior to impl. So RFPL created as initially that is really task for discussion and planning.
Initially I'm thinking about some set of predefined effects which could be added by additional attributes for corresponding components events like:
<panelMenuGroup expandEffect="rf.effects.slide">
...
which could be later expanded to use custom JS functions like mySlide to trigger some custom effect.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 12 months
[JBoss JIRA] Created: (RFPL-486) Consider during development and QE that exceptions and console diagnostic messages should be informative and has good spelling
by Ilya Shaikovsky (JIRA)
Consider during development and QE that exceptions and console diagnostic messages should be informative and has good spelling
------------------------------------------------------------------------------------------------------------------------------
Key: RFPL-486
URL: https://jira.jboss.org/jira/browse/RFPL-486
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
Components: CDK, components
Affects Versions: 4.0.0.ALPHA1
Reporter: Ilya Shaikovsky
Assignee: Jay Balunas
Jay, we asked about that much times during 3.x development. And also have "improved diagnostic" as one of the goals for 4.x.
Sometimes we have just not informative exceptions at all(them just not caught and re-thrown properly). E.g. indexOutOfBounds exception while just parsing attribute (really there should be message about wrong attribute value)
Sometimes just English is not really good in message. E.g. "javax.faces.FacesException: Target pointed Attribute for of AjaxStatus component with id status not is AjaxContainer" in Ajax status.
So think I could add to one of the core 4.x planning pages at wiki and then I think this should be assigned to Prabhat for inclusion into check list and considering during QE.
WDYT?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 12 months