batchee-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Reinhard Sandtner (JIRA)" <>
Subject [jira] [Commented] (BATCHEE-122) @Deprecated should describe alternatives
Date Tue, 27 Jun 2017 07:35:00 GMT


Reinhard Sandtner commented on BATCHEE-122:

[~rmannibucau] i'd like to keep it in 0.5-incubating and remove it in 0.6-incubating to give
the users the chance to remove it properly without blowing up with a ClassNotFoundException
- of course we are incubating and version is < 1.0 and users have to expect API breaks
but keep it one version doesn't hurt - wdyt?

imo the compiler warning is fine to catch it if someone misses the realease notes

i thought i've documented it in the homepage but seems i've not - will do if we decide to
keep the listener for one version

> @Deprecated should describe alternatives
> ----------------------------------------
>                 Key: BATCHEE-122
>                 URL:
>             Project: BatchEE
>          Issue Type: Improvement
>    Affects Versions: 0.5-incubating
>            Reporter: Alexander Falb
>            Priority: Minor
> {{BeforeStepScopeListener}} is deprecated according the JavaDoc, but missing the {{@Deprecated}}
annotation. The annotation produces compiler warnings if the class is used.
> Also it does not have any migration advises for users of the deprecated class.

This message was sent by Atlassian JIRA

View raw message