Hi List
I think the answer to the "contribution jungle" probably lies with
having a nice clean module (plugin) system.
I just like to give a short outlook about this topic related to the
soon coming 3.0 release:
- we improved the module mechanism a lot (dropping one jar as you
proposed will be possible)
- content (dialogs, paragraphs, ...) are kept together
- we modularized magnolia (we made subprojects including some default
modules)
- maven: to mavenize your code will be quite easy (copy a already
existing module and use it as a skeleton)
- we plan to keep a module section in the svn to give contributors
the possibility to share and manage there code
- Attention: the 2.1 modules will not run under 3.0 without
modification!
without moving them into specific places in the file system, but it
must be possible surely ?
Was you ever able to run a jsp from the classpath? If so let me know
how to achieve this. Currently we moved what ever possible to the
classpath. The modules should only extract what is meant to get
changed by the enduser.
About taglibs:
- there is no need to register them in web.xml or to extract the tld
(as long found anywhere in the classpath)
I hope we are making progress in the desired direction.
Regards,
Philipp Bracher
obinary ltd.
-----------------------------------------------------
[EMAIL PROTECTED] http://obinary.com
magnolia content management http://magnolia.info
-----------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
