Joern Nettingsmeier schrieb: > by the way, this issue is a perfect example of why it is preferrable to > first *document* any convention and then implementing it.
Well, it is generally very hard to specify first and implement later. Most specifications are built based on real products which were developed over many years. It is very good that you comment on the modularization and dependency resolving, so we have the chance to improve them. > frankly the lenya codebase is not very good in sticking to its own > conventions, Yes, as soon as they proved useful (see above) ... > and it's by a huge margin the most difficult-to-learn > project i have ever worked with, because you can't learn from the code > since the code often does it wrong. I don't think its that bad. We have quite a lot of complexity and different technologies, so the learning curve is steep. One problem is that there are often many ways to do something, and that people have different "best practises" depending on their preferences and needs. No idea if we can do something about that. > there will always be legacy code in > any project and that's fine, but i have no chance in hell to find out > what is legacy and what is current best practice. How can we improve this? -- Andreas > Jörn Nettingsmeier wrote: >> how do we use the <depends/> relation in module.xml? >> does it only list java dependencies that will prevent compilation if >> unsatisfied, or also functional dependencies where stuff will break at >> runtime? >> >> if the former, i think the dependency of default/defaultusecases on >> sitemanagement is erroneous. can anyone confirm that? >> >> if the latter, workflow should depend on sitemanagement, because it >> provides jxtemplates that call sitemanagement usecases. that would >> also mean we have a circular dependency, because sitemanagement >> depends on workflow already. >> >> waiting for enlightenment, >> >> jörn >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
