> I didn't mean the act of the generation, I know this is but executing > a command - but if I need to develop on the implementation or the > components source code and have to execute the command whenever I > change something in the share classes, I promise this makes developing > much more tedious, and this is probably not what we should encourage.
We make heavy use of code generation in ADF Faces, and do not find it to be a huge issue in practice. That might well be due to the fact that, in practice, the source of those generated files have a low frequency of update. When such an update is necessary, and we run the command line build tool, the generated files are still part of the IDE experience, so the overall development impact is slight. > Rather than imposing this on the developers, I would impose on the > users to either download and use myfaces-all.jar if they use > components and implementation or myfaces-components.jar if they just > use the components (and implicitly package share along with that). > > Not so much more inconvenience for the users, a lot more convenient > for us developers! I might be missing something, but this proposal doesn't seem to address the runtime eclipsing of shared classes, which looks to still be an issue because core and extensions are released independently. Given the choice of whether to impose upon developers who understand the implications of their decisions or upon users who often do not understand the subtleties, IMHO, I would suggest the former, since developers are better equipped to deal with it. Kind Regards, John Fallows
