[jbosstools-issues] [JBoss JIRA] (JBIDE-18750) Make CDI validation messages dependent on version

[Alexey Kazakov (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-18750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020626#comment-13020626 ] 

Alexey Kazakov edited comment on JBIDE-18750 at 11/17/14 9:29 PM:
------------------------------------------------------------------

For example:
CDI 1.0 validation message: "There is no class "blah-blah-blah" [JSR-299 §8.2]"
!cdi10.png!


CDI 1.1/1.2 validation message: "There is no class "blah-blah-blah" [JSR-346 §8.2]"
!CDI12.png!


was (Author: akazakov):
For example:
CDI 1.0 validation message: "There is no class "blah-blah-blah" [JSR-*299* §8.2]"
!cdi10.png!

CDI 1.1/1.2 validation message: "There is no class "blah-blah-blah" [JSR-*346* §8.2]"
!CDI12.png!

> Make CDI validation messages dependent on version
> -------------------------------------------------
>
>                 Key: JBIDE-18750
>                 URL: https://issues.jboss.org/browse/JBIDE-18750
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: cdi
>            Reporter: Viacheslav Kabanovich
>            Assignee: Viacheslav Kabanovich
>              Labels: new_and_noteworthy
>             Fix For: 4.3.0.Alpha1
>
>         Attachments: cdi10.png, CDI12.png
>
>
> All cdi validation messages in our tool now reference JSR-299, which is CDI 1.0. Validation of CDI 1.1 and 1.2 project should reference JSR-346, besides numbers of sections for many messages are changed. Even if in most cases wording of a message may remain the same, the necessity to provide relevant references requires separating messages for each version. That will also let change wording as needed.
> The proposed solution to the task is such that in cases when a validation rule logic is the same through several versions, its implementation will not be affected other than by replacing MY_MESSAGE by MY_MESSAGE[versionIndex].



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)