RE: Modules and common files

I am doing the same with ant/build process, is there any aother way? Is there a way to keep these files in a acommon place? -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: , 1 2003 6:15 To: 'Struts Users Mailing List' Subject: RE: Modules and common files Thanks

Re: Modules and common files

I have not done it, but there are definitions in each request processor that can tell whether or not paths are relative. So the struts-config for the module has a request processor element that has global configuration info for the module. sandeep --- [EMAIL PROTECTED] wrote: Hi, We have

Re: Modules and common files

There were some discussions in the developer list about sharing common properties in modules. A *root* module carries common properties while child modules *inherit* these properties. Wish that could address your problems in the future. It is quite painful to have so many common files. In our

RE: Modules and common files

Geoff wrote: We have just started using modules and have run into a problem when it comes to common files between the modules (eg: javascript, stylesheets, images). Has anyone else had this problem? If so, what did you do? I have Apache serve these static resources. For example, off the

RE: Modules and common files

respond to Struts Users Mailing List [EMAIL PROTECTED] To 'Struts Users Mailing List' [EMAIL PROTECTED] cc Subject RE: Modules and common files Geoff wrote: We have just started using modules and have run into a problem when it comes to common files between the modules (eg: javascript

RE: Modules and common files

Thanks Wendy, but the situation is a little different. They are common resources, not necessarily static resources. Hmmm... in that case, I'd maintain them in one place in the source tree and use the build process to put copies everywhere they're needed. Disk space is cheaper than maintaining