The repository can actually contain all the Projects and code that are shared
between multiple versions of VAJ. Remeber, the repository is just a database
of versions of various entities (Projects, Packages, Classes, Methods, etc.) -
it's your workspace that is the view (see
"How does the repository/workspace combination work?" for a detailed
explanation).

I've actually had one repository serving three different versions of VAJ at one
time - 2.0, 3.0, and 3.0 Java2. I can't imagine it will be a problem doing the same for 3.02 and 3.5.3.
Just upgrade the users who want/need the latest and let the others continue
as they are -their workspaces will still find the older versions of the core
Projects they need.


Eventually, you may want to purge the old versions once everyone has been
upgraded to the new version.