Hi  Jörg,

yes you are of course right that this restructuring of the module should have 
been advertised more. OTOH the API was already broken at the point when we 
decided to not further develop and therefor not bundle compatibility modules. 
The classes in this new stk compatibility module did not work correctly in all 
cases due to undeclared dependencies. Some functions would simply fail with 
ClassNotFoundException at runtime. To fix this we were faced with difficult 
choice to either re-add dependency to templating compatibility modules or to 
drop the STK code that depended on it completely. We choose the middle ground - 
classes that needed tempting compatibility modules to function properly were 
simply moved to other module, while the package and class names stayed 
unchanged, but new compatibility module is not packaged by default. This 
ensured that nobody will not start using them by mistake thinking that this 
should still work out of the box and only discover issues at runtime. Instead 
if you still rely on this old code you now need to bring extra module in your 
war file, but can find out at the build time instead of having to face it much 
later.

Hope this clarifies  why we chose to do this change in minor release.

Regards,
Jan

On Nov 8, 2012, at 3:17 PM, Jörg von Frantzius <[email protected]> 
wrote:

> Hi,
> 
> http://documentation.magnolia-cms.com/releases/4-5-6.html lists the following:
>> Creates a standard-templating-kit-compatibility module which contains all 
>> deprecated code from the standard-templating-kit.
> It seems that this should in fact be 
> "magnolia-module-standard-templating-kit-compatibility"? Maybe this should be 
> corrected, so people don't confuse it with "m 
> agnolia-templating-compatibility".
> 
> Also it would be great if you could accompany API changes like this (moving 
> classes to different modules) by blog posts, so people will take proper 
> notice? After all, this happened in a minor release; if somebody simply 
> upgraded to 4.5.6 from previous 4.5.x releases, he might think some API was 
> simply dropped, while the above sentence in the release notes doesn't point 
> to the right module.
> 
> Regards,
> Jörg
> 
> -- 
> Dipl. inf. Jörg von Frantzius, System Architect
> 
> Email mailto:[email protected]
> Phone +49 30 283921-318
> Fax +49 30 283921-29
> 
> Aperto AG - In der Pianofabrik
> Chausseestraße 5, D-10115 Berlin-Mitte
> http://www.aperto.de
> http://www.facebook.com/aperto
> https://www.xing.com/companies/apertoag
> 
> HRB 77049, AG Berlin Charlottenburg
> Vorstand: Dirk Buddensiek (Vorsitzender), Kai Großmann, Stephan Haagen
> Aufsichtsrat: Bernd Hardes (Vorsitzender)
> 
> 
> ----------------------------------------------------------------
> For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
> Alternatively, use our forums: http://forum.magnolia-cms.com/
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------



----------------------------------------------------------------
For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to