We want 0.10.0 to stabilise the API for the 1.0 release. There are some places where our APIs don't meet current Shibboleth conventions and this is probably the last time we have the option of aligning those.
So, review all APIs and check against current conventions; separate sub-tasks should be created for places where we discover discrepancies for correction in 0.10.0.
Environment
None
100% Done
Activity
Ian YoungSeptember 5, 2018 at 2:49 PM
Note that this affects API only, and not things like field names. For example, a property called xslResource should be renamed as XSLResource, which is to say that it should have getXSLResource and setXSLResource. The associated field shouldn't be changed to XSLResource, though, because that breaks Java's own conventions.
We want 0.10.0 to stabilise the API for the 1.0 release. There are some places where our APIs don't meet current Shibboleth conventions and this is probably the last time we have the option of aligning those.
So, review all APIs and check against current conventions; separate sub-tasks should be created for places where we discover discrepancies for correction in 0.10.0.