[
https://issues.apache.org/jira/browse/SLING-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793627#comment-13793627
]
Carsten Ziegeler commented on SLING-3168:
-----------------------------------------
Ok, unfortunately the damage is already done as we released the Job interface
with the last version.
However, I suggest to add JobPriority as an enum to the job interface,
deprecate the old getJobPriority method and add a new getPriority() method
returning the new enum.
Then move all constants wrt notification into a separate constants class and
deprecate the whole JobUtil class
[[email protected]] WDYT?
> Deprecating JobUtil class?
> --------------------------
>
> Key: SLING-3168
> URL: https://issues.apache.org/jira/browse/SLING-3168
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Extensions Event 3.3.0
>
>
> This is a follow up from SLING-3028 based on comments by Stefan Seifert:
> the JobUtil class is deprecated by 90%. perhaps its better to deprecated it
> completely and move the remaining 10% to a new location or other classes more
> suitable. This would solve the inconsistency with the JobUtil.JobPriority
> enum as well, which is not part of the Job interface, whereas JobType is part
> of the Job interface.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
