Re: MalformedURLException: unknown protocol: classpath

2019-02-17 Thread Marc Chamberlin
On 02/17/2019 06:01 AM, cryptearth wrote: > git clone -b master https://github.com/apache/james-project james folder> > > branch 3.2.0 is completed and isn't worked on anymore, branch 3.2.x > got last update in Dec 10, 2018 - so you have to use master branch to > get current fixes > to compile

Re: MalformedURLException: unknown protocol: classpath

2019-02-17 Thread Benoit Tellier
I am not sure you can use "james script" directly like this as a initd script. What we do use in docker (and thus is maintained) is ./bin/wrapper-linux-x86-64 conf/wrapper.conf wrapper.syslog.ident=james wrapper.pidfile=var/james.pid wrapper.daemonize=FALSE Cheers, Benoit On 2/18/19 7:39 a

Re: MalformedURLException: unknown protocol: classpath

2019-02-17 Thread Marc Chamberlin
Hi Matt, thanks for responding!  It appears to me that "classpath" is actually defined in the startup scripts. There are two different scripts used to start the james server, either "james" or "run.sh". I do not believe "classpath" is defined in any of the config files themselves. I am not using

Re: MalformedURLException: unknown protocol: classpath

2019-02-17 Thread cryptearth
Hey Marc, Matt here. The provided stack only says that you given "classpath" to some parameter wich expectes a url in some config file. So I guess it could help if you also show the config where you set "classpath" so one can figure out, if "classpath" is a legal input for the setting you set