DiskBackedContent: use a different approach for deprecation
It turns out that calling @deprecated on Content alter the class, and any instantion of "Content" will be wrongly marked as deprecated… So use a different approach too preserve compatibility (and we won't keep it long).
Please register or sign in to comment