+1
In ReleaseBuilder class >> #prepareSourceCode, we need another script for fixing those obsolete classes. Or at least a check. #checkForObsoleteClasses.
Unfortunately, only #prepareEnvironment is called in our CI.
Best,
Marcel
Am 30.12.2019 11:24:47 schrieb Eliot Miranda <[hidden email]>:
> On Dec 29, 2019, at 2:18 PM, Nicolas Cellier wrote:
>
>
> Hi all,
> I noticed two obsolete classes related to Preferences.
> They disappear if evaluating:
>
> PreferenceViewRegistry removeObsolete.
>
> I did not see that in ReleaseBuilder, is it missing?
> Or should we just put that in package postscript?
For me it definitely belongs in ReleaseBuilder