I am of the opinion that having a single codebase will make life much easier in the long run for everybody. Separate codebases or even branches adds a lot of complexity in terms of managing fixes and changes to any core code. And it would be a nightmare to depend on the automated tests because you would have to make sure nothing is broken in multiple codebases whenever you do need to make core changes.
I prefer the option of enhancing the build system to do multiple targets for the different portals. This can be somewhat offset by adhering to the principle of coding to interfaces and letting Spring wire up the actual implementations. This is a matter of enduring the pain now but for a much shorter period of time (customizing the build process), or defer the pain but have it last forever (dealing with multiple codebases). I personally prefer a cold that goes away quickly rather than getting cancer that eats away at you until you die. Cynick On Mar 6, 12:56 am, "Hiroki Terashima" <[EMAIL PROTECTED]> wrote: > Hi everybody, > > We (Tony and I) see a potential road-block in the TELS Portal > development: Separation of TELS Portal and PAS Portal, in terms of codebase > and database. > > Should we develop TELS Portal and PAS Portal in the same repository? > Should we add extra fields in the database schema that was defined for PAS > Portal (ex: TELS Portal requires birthday, birthmonth, email besides just > firstname/lastname). Where should the separation happen? > > If you have any thoughts, please let us know. > > Thank you, > Hiroki --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
