Hi Magnolians,

magnolia-enterprise-webapp 5.2.1 pulls in magnolia-module-legacy-admininterface 
5.0.2 via magnolia-bundled-webapp, magnolia-empty-webapp and 
magnolia-module-cache....  that definitely seems to be an error, it should be 
version 5.2.1. This error requires us to add the dependency explicitly to our 
WAR overlay, so please correct this...

Also:
magnolia-module-legacy-admininterface 5.2.1 has an incorrect dependency on 
magnolia-i18n 5.2  (should be 5.2.1).
magnolia-module-legacy-admininterface 5.2.1 has an incorrect dependency on 
magnolia-rendering 5.2  (should be 5.2.1).
This forces you to additionally write an excludes when adding 
magnolia-module-legacy-admininterface. :-(

magnolia-module-groovy 2.2.1 has an incorrect dependency on magnolia-ui-api 5.2 
(should be 5.2.1).
magnolia-module-groovy 2.2.1 has an incorrect dependency on 
magnolia-ui-contentapp 5.2 (should be 5.2.1).

magnolia-module-activation 5.2.1 has incorrect dependency on magnolia-ui-api 
5.2 (should be 5.2.1).

magnolia-contacts 1.2 (pulled in by magnolia-bundled-webapp) should be bumped 
to 1.2.1 and dependency on magnolia-ui-contentapp bumped to 5.2.1.

magnolia-module-standard-templating-kit 2.7.1 has incorrect dependency on 
magnolia-module-rssaggregator 2.2 (should be 2.2.1).
magnolia-module-standard-templating-kit 2.7.1 has incorrect dependency on 
magnolia-module-forum 3.2 (should be 3.2.1).
magnolia-module-standard-templating-kit 2.7.1 has incorrect dependency on 
magnolia-module-form 2.1 (should be 2.2.1).
magnolia-module-standard-templating-kit 2.7.1 has incorrect dependency on 
magnolia-module-inplace-templating 2.2 (should be 2.2.1).
magnolia-module-standard-templating-kit 2.7.1 has incorrect dependency on 
magnolia-module-imaging 3.0.2 (should be 3.0.3).
magnolia-module-standard-templating-kit 2.7.1 has incorrect dependency on 
magnolia-module-resources 2.2 (should be 2.2.1).

รจ Basically, it looks like you didn't update any of these dependencies for the 
release!?!?

magnolia-module-imaging is also included incorrectly (3.0.1) via 
magnolia-ui-admincentral.

magnolia-module-rssaggregator 2.2.1 has incorrect dependency on magnolia-dam 
1.2 (should be 1.2.1).

magnolia-module-resources 2.2.1 has incorrect dependency on magnolia-ui-form 
5.2 (should be 5.2.1).

magnolia-module-mail 5.1.1 has incorrect dependency on magnolia-dam 1.1 (should 
be 1.2.1).

Also, there is a problem with tika-core:
magnolia-enterprise-webapp gets version 1.3 via jackrabbit-core, but needs 
version 1.4 to match tika-parsers 1.4 pulled in by magnolia-empty-webapp. You 
should add an explicit dependency on tika-core-1.4, and add exclude rules for 
the 1.3 versions...


Finally I note both antlr-2.7 and antlr-3.3 are both pulled in, both JARs get 
included in the webapp. Is that necessary and deliberate?


I have to say, it is quite annoying to have to manually check the dependencies 
each time we up the version number in magnolia.
I think there seems to be some problem with the way the releases are made. 
Clearly you developers at magnolia are getting the correct dependencies by some 
other method, or you would not be releasing the code as it is (since it doesn't 
run).
The question is, is there something wrong with my maven setup, or are people 
just being lazy at your end?


Thanks!

Regards from Vienna,

Richard




----------------------------------------------------------------
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