So we should talk about the layout of the subversion repository. We had talked about each project getting its own "module" in the repository with its own trunk/branches/tags structure.
This is easy enough for the core stuff. But has implications for all of the current HibernateExt subprojects. Specifically, the biggest issue is the use of HibernateExt/common and how y'all want to deal with that (plus the dependency on core). Three options: (1) keep doing what you do now in terms of checking out each individually (2) use of svn:externals to link-in the common stuff (3) removal of common and reworking the builds ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
