On 7/31/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote: > Robert Burrell Donkin ha scritto: > > On 7/31/07, norman <[EMAIL PROTECTED]> wrote: > >> Hi Paulo, > >> > >> I think it whould be enough to put the jars > >> in /path/to/james/apps/james/SAR-INF/lib/ directory ( You need to create > >> the lib after james was started once) > > > > IMHO it would be useful to have an extensions directory whose contents > > would be automatically copied into the SAR. can anyone think of any > > good reasons for me not to just go ahead and add it to the code? > > > > - robert > > What is the use case for this need? > > Ironically I ask this question because adding a folder to be packaged in > the sar was the first thing I did in my local JAMES Server 3 years ago > when I started using it. I then removed it because it did not save me > from any manual task ;-) > > I'm no more able to figure an application of such "directory": whenever > you add a jar you also have to change the config and the config most > time have to be changed in the deployed folder once the sar has been > exploded. When you do this you can also copy the needed jars.
ATM to produce a completely configured alternative SAR, the configuration and the build file need to be edited. with an ext directory only the configuration files would need to be altered. - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
