Hi, Since the procrun is fairly generic application that might have it's usage beyond the Tomcat5 scope, after some consultations with remm, I propose the following reorganization:
1. All the TC specific code and resources will be moved to j-t-c/procrun. 2. There will be no build files in the bin neither they will be maintained. 3. The binaries will be in the j-t-c/procrun/bin so that we can use them in the installation build. 4. Make the needed callback mechanism to enable the separation. There is another approach; that we make the subfolder 'tomcat' in the procrun and keep all the tomcat specific code in there. It could have its purpose too, cause it will show how to customize the procrun to a specific application look and feel, without the need to download from j-t-c. MT. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
