Mario Ivankovits schrieb: > And - IMHO the killer, the shared is not interoperable, means it cant > put stuff in the request and use it again if called from another package > as they are different classes - different package names. > See my other thread regarding ExtensionsFilter and Dummyform. > Actually this is a serious showstopper, due to the fact that often some kind of request singleton is absolutely needed.
I think a debian like unstable, testing, stable system is better to keep the conflicts out. The commons should be for the most stable code there is, the rest has to be maintained by the subprojects themselves and once the stuff is stable enough it should be moved into commons.(Btw. we have to push the sandbox to tomahawk moving after 1.1.2 the sandbox is getting too big) I think this is a way better approach than refactoring different classes into the jars via precompilation. Btw. there is another huge showstopper, refactoring from the commons into the submodules and vice versa basically cannot work with the current approach, debuggers cannot work, and some ides probably have outright problems to even compile and deploy the integrated webapps decently.
