Is there a reason @Option is not available in the public API for usage in custom tasks?
I’d consider it handy to be able to define @Options on custom tasks instead of having to use project properties for this purpose.
There’s technically nothing stopping you from using this feature. It being “internal” simply means it’s not a stable or documented public API so it may change/break/disappear in the future. That said, there have been discussions about promoting this to public.
1 Like
Ah, nice, thanks for the info. 
+1 for adding promoting to public