[JBoss JIRA] Created: (RFPL-486) Consider during development and QE that exceptions and console diagnostic messages should be informative and has good spelling
11:17 a.m.
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
1:42 p.m.
New subject: [JBoss JIRA] Commented: (RFPL-486) Consider during development and QE that exceptions and console diagnostic messages should be informative and has good spelling
[
https://jira.jboss.org/jira/browse/RFPL-486?page=com.atlassian.jira.plugi...
]
Jay Balunas commented on RFPL-486:
----------------------------------
Agreed, this needs to addressed. I believe we will set this to M1.
The task here is to create a wiki page describing the requirements, and examples of impl.
Followed by QE have the checklist that you mention.
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
Fix For: 4.0.0.M1
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
1:42 p.m.
New subject: [JBoss JIRA] Updated: (RFPL-486) Consider during development and QE that exceptions and console diagnostic messages should be informative and has good spelling
[
https://jira.jboss.org/jira/browse/RFPL-486?page=com.atlassian.jira.plugi...
]
Jay Balunas updated RFPL-486:
-----------------------------
Fix Version/s: 4.0.0.M1
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
Fix For: 4.0.0.M1
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:28 p.m.
New subject: [JBoss JIRA] Updated: (RFPL-486) Consider during development and QE that exceptions and console diagnostic messages should be informative and has good spelling
[
https://jira.jboss.org/browse/RFPL-486?page=com.atlassian.jira.plugin.sys...
]
Jay Balunas updated RFPL-486:
-----------------------------
Assignee: Ilya Shaikovsky (was: Jay Balunas)
Fix Version/s: 4.0.0.Milestone2
(was: 4.0.0.Milestone1)
Ilya, please work on the first part of this task. Creating a wiki page with requirements,
examples, etc... that we can build tasks from. We also need to consider jboss common
logging requirements. We can discuss those when you are ready to work on this.
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/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: Ilya Shaikovsky
Fix For: 4.0.0.Milestone2
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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:52 p.m.
New subject: [JBoss JIRA] Updated: (RFPL-486) Consider during development and QE that exceptions and console diagnostic messages should be informative and has good spelling
[
https://jira.jboss.org/browse/RFPL-486?page=com.atlassian.jira.plugin.sys...
]
Jay Balunas updated RFPL-486:
-----------------------------
Fix Version/s: Future_4.X
(was: 4.0.0.Milestone2)
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/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: Ilya Shaikovsky
Fix For: Future_4.X
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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:45 p.m.
New subject: [JBoss JIRA] Updated: (RFPL-486) Consider during development and QE that exceptions and console diagnostic messages should be informative and has good spelling
[
https://jira.jboss.org/browse/RFPL-486?page=com.atlassian.jira.plugin.sys...
]
Jay Balunas updated RFPL-486:
-----------------------------
Fix Version/s: 4.0.0.Milestone2
(was: Future_4.X)
This will go hand in hand with development guidelines, and debugging wiki pages, and
articles planned - like RFPL-80. We should at least get this started
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/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: Ilya Shaikovsky
Fix For: 4.0.0.Milestone2
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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:46 p.m.
New subject: [JBoss JIRA] Updated: (RFPL-486) Consider during development and QE that exceptions and console diagnostic messages should be informative and has good spelling
[
https://jira.jboss.org/browse/RFPL-486?page=com.atlassian.jira.plugin.sys...
]
Jay Balunas updated RFPL-486:
-----------------------------
Fix Version/s: 4.0.0.Milestone3
(was: 4.0.0.Milestone2)
Priority: Critical (was: Major)
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/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: Ilya Shaikovsky
Priority: Critical
Fix For: 4.0.0.Milestone3
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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:57 p.m.
New subject: [JBoss JIRA] Updated: (RFPL-486) Consider during development and QE that exceptions and console diagnostic messages should be informative and has good spelling
[
https://jira.jboss.org/browse/RFPL-486?page=com.atlassian.jira.plugin.sys...
]
Jay Balunas updated RFPL-486:
-----------------------------
Fix Version/s: Future_4.X
(was: 4.0.0.Milestone3)
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/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: Ilya Shaikovsky
Priority: Critical
Fix For: Future_4.X
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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:33 p.m.
New subject: [JBoss JIRA] Updated: (RFPL-486) Consider during development and QE that exceptions and console diagnostic messages should be informative and has good spelling
[
https://issues.jboss.org/browse/RFPL-486?page=com.atlassian.jira.plugin.s...
]
Jay Balunas updated RFPL-486:
-----------------------------
Fix Version/s: Post_4.F
(was: Future_4.X)
Consider during development and QE that exceptions and console
diagnostic messages should be informative and has good spelling
------------------------------------------------------------------------------------------------------------------------------
Key: RFPL-486
URL: https://issues.jboss.org/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: Ilya Shaikovsky
Priority: Critical
Fix For: Post_4.F
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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:31 p.m.
New subject: [JBoss JIRA] Updated: (RFPL-486) Consider during development and QE that exceptions and console diagnostic messages should be informative and has good spelling
[
https://issues.jboss.org/browse/RFPL-486?page=com.atlassian.jira.plugin.s...
]
Jay Balunas updated RFPL-486:
-----------------------------
Fix Version/s: 4.Future
(was: 4.Next)
Consider during development and QE that exceptions and console
diagnostic messages should be informative and has good spelling
------------------------------------------------------------------------------------------------------------------------------
Key: RFPL-486
URL: https://issues.jboss.org/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: Ilya Shaikovsky
Priority: Critical
Fix For: 4.Future
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:05 p.m.
New subject: [JBoss JIRA] (RFPL-486) Consider during development and QE that exceptions and console diagnostic messages should be informative and has good spelling
[
https://issues.jboss.org/browse/RFPL-486?page=com.atlassian.jira.plugin.s...
]
Brian Leathem reassigned RFPL-486:
----------------------------------
Assignee: Brian Leathem (was: Ilya Shaikovsky)
Consider during development and QE that exceptions and console
diagnostic messages should be informative and has good spelling
------------------------------------------------------------------------------------------------------------------------------
Key: RFPL-486
URL: https://issues.jboss.org/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: Brian Leathem
Priority: Critical
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, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:05 p.m.
New subject: [JBoss JIRA] (RFPL-486) Consider during development and QE that exceptions and console diagnostic messages should be informative and has good spelling
[
https://issues.jboss.org/browse/RFPL-486?page=com.atlassian.jira.plugin.s...
]
Brian Leathem resolved RFPL-486.
--------------------------------
Fix Version/s: (was: 5-Future)
Resolution: Rejected
Rather than doing an audit, let's report individual errors as they are discovered, and
treat them individually.
Consider during development and QE that exceptions and console
diagnostic messages should be informative and has good spelling
------------------------------------------------------------------------------------------------------------------------------
Key: RFPL-486
URL: https://issues.jboss.org/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: Ilya Shaikovsky
Priority: Critical
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, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4194
days inactive
5153
days old
richfaces-planning-issues@lists.jboss.org
11 comments
3 participants
participants (3)
-
Brian Leathem (JIRA) -
Ilya Shaikovsky (JIRA)
-
Jay Balunas (JIRA)