Of course, one solution is to have only one project file in project/XXX.xml which defines a "XXX" module and have several projects within it.
However, this is not satisfying as the whole XXX/ directory is about 400 Mo and contains a lot more than just code and I only need to build some projects. So you're going to ask, 'why not define "real" modules' ? The answer is that we wanted to keep the directory structure so that everyone has the same on his workspace and also, for our Ant build files, we use a default.properties which contains default locations of all needed jars within that directory structure, which makes it easy to build our projects. Is there a solution within gump or do I really have to create real modules for gump in our CVS modules list, as in : gump-dev-common XXX/development/common ? Thanks -Vincent > -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED]] > Sent: 30 March 2002 17:07 > To: [EMAIL PROTECTED] > Subject: [Gump] CVS modules and aliases problem > > I have a problem. Gump requires "real" CVS modules whereas we are using > aliases on our project, i.e. we have the following directory structure : > > XXX > |_ development > |_ common > |_ [...] > |_ [...] > > And in our CVS modules file we have : > > icom-dev-common -a XXX/development/common > > (which means that although we have several projects, we have a single > "real" module). > > However, if I define the following in a Gump project file, it doesn't > work : > > <module name="XXX/development/common"> > [...] > > It also doesn't work if I use : > > <module name="icom-dev-common"> > [...] > > because icom-dev-common is an alias and the generated build.bat doesn't > know about it and this thinks the code is in > ${basedir}\cvs\icom-dev-common ... whereas it is in > ${basedir}\cvs\XXX\development\common ... > > Any idea ? > Thanks > -Vincent > > > > -- > To unsubscribe, e-mail: <mailto:alexandria-dev- > [EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:alexandria-dev- > [EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
