james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Burrell Donkin" <robertburrelldon...@gmail.com>
Subject Re: ext directory [WAS Re: Imap Function]
Date Wed, 01 Aug 2007 08:09:08 GMT
On 7/31/07, Stefano Bagnara <apache@bago.org> wrote:
> Robert Burrell Donkin ha scritto:
> > On 7/31/07, norman <norman@apache.org> 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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message