Claudio, Nathan,
A quick excerpt from a mail I sent to the dev-list yesterday:
[...]
5. The main point which is probably unclear at the moment, is that
your own webapp, if any, should depend on magnolia-empty-webapp, and
add the dependencies to the modules you need. (i.e you should clone
the magnolia-bundled-webapp and tailor it to your needs rather than
extend/depend on it)
[...]
Another point to keep in mind (same idea) is that the "new" magnolia-
bundle project and subprojects are not meant to be used as-is by
projects extending magnolia, but only as packaging projects for
actual Magnolia releases as a product.
[...]
Does that answer your question ?
HTH
Cheers,
greg
On Dec 13, 2007, at 17:36 , Nathan Russell wrote:
I've just downloaded magnolia-bundled-webapp-3.5.war and from the
release notes (in the war) it contains:
magnolia-empty-webapp 3.5
magnolia-module-dms 1.2
magnolia-module-samples 3.5
So its probably fair to expect that magnolia-empty-webapp-3.5.war
contains ... well, just the magnolia-empty-webapp 3.5
Hope this helps (but I agree it would be useful to have the release
notes available outside of the war file so you know whats in them
before
you download :) )
Cheers
Nathan
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
