- http://www.marcosaurelio.com *1984 +2057
"Do not read beauty magazines, they will only make you feel ugly" On Sun, Jul 13, 2008 at 2:40 PM, Michiel van der Wulp <[EMAIL PROTECTED]> wrote: > Hi *, > > To be able to solve issue 4994 (which is holding back the 0.26 release), I > need some explanation about how the Profiles work. Some of it I may be able > to find out by reading the code, but any help is welcome! > > 1. > The ProfileManagerImpl keeps track of 2 lists of Profiles: > "defaultProfiles" and "profiles". > What is the difference? When are they filled and emptied? > defaultProfiles are the profiles that are added to a new project profiles are the currently loaded profiles > > 2. > The ProfileConfiguration is a ProjectMember. Are ProfileConfigurations > reused between projects, or how come that the profiles are not reloaded when > loading a new project? > They are not reused... But they contain only references to the profile objects... that contain references to the profile models. so when a profile model changes, neither of them knows about it. Maybe a simple way to tackle this would be changing the profile to return a clone of its model in getProfilePackages(). Can a model be cloned? or creating a "reload()" or something like that in he profiles, that would substitute the current model object by a clone of the initial one... can't we just *maas* > > Regards, > Michiel > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
