[EMAIL PROTECTED] wrote: [...]
http://lenya.apache.org/1_4/reference/modules/index.html suggests that Modules will be able to add protocols. Protocols are part of the platform and should not be added dynamically. Anyone adding a protocol would have a development environment.
Yes, but this doesn't mean that adding Java code to modules is a bad thing, does it?
Lenya has been usable and very flexible without a development environment. A binary version of Lenya is very flexible. I realize that most Committers and some Developers have a development environment, but most Developers do not, and should not, need one. If Modules can contain Java, then: 1. Every Lenya Developer must have a development environment.
I don't understand this implication. You're not required to add Java code to your modules.
2. We have the dependency issues that started this thread.
Yes, they have to be solved.
I cannot see how it is good to force Users to install a development environment.
We're not forcing anyone. We're allowing to use Java.
It increases the complexity and reduces the audience.
It allows modularization. We have to break up our monolithic core into modules, otherwise we'll end up with too many connections between components and circular dependencies. If we don't allow Java code in modules, people will start to implement their stuff using server pages and other suboptimal technologies.
Lenya should become both easier and more powerful. Modules including Java that needs to be compiled is a step in the wrong direction.
I disagree. -- Andreas -- Andreas Hartmann Wyona Inc. - Open Source Content Management - Apache Lenya http://www.wyona.com http://lenya.apache.org [EMAIL PROTECTED] [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
