Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to firstname.lastname@example.org.
Modules and Modules2 have the problem that they are not tagged. So using them on anything but the simplest level causes problems if you branch and expect to get the right collection of source on both the branch and the trunk. Consider the case where you want to add a sub-module on the branch only. Like Dan and Dave we bailed on them. chuck David Somers wrote: > Dan Pupek wrote: > > >>I've been struggling over whether to stop using modules2 since for several >>reasons: >> > > http://dan-thinks.blogspot.com/2007/01/problems-with-modules2-and-cvsnt.html > >> >>Does anyone else have any insights or suggestions on using modules2? > > > I've been using modules2 in a very simple way: to bring one module into > another module as a sub-module (which I use to bring common code - > typically libraries and configuration data - in projects). > > And by "in a very simple way" I mean that: > - only pull top-level modules into other top-level modules as a sub-module > (IIRC when I tried to alias a module as a sub-sub-module things went > terribly wrong). > - never add sub-modules into an aliased module: only add them into the > concrete module. > > >>Is it considered stable? > > > I belive the official status is "Experimental" (i.e. use at your own risk > and don't complain if you get bit on the <insert suitable body part here>). >