Re: Setup and build issues

2018-12-06 Thread Benoit Tellier
Hi, I wonder if there is not some cleaner ways of doing this. Could you share the exact stack-trace you have? (for license reasons I don't have a windows machine at hand...) With the exact maven goals and maven versions you are running... Previously we choose to not play Dockerized test if a doc

Re: Setup and build issues

2018-12-06 Thread Garry Hurley
Bill I got past those same errors in cassandra. What I had to do was comment out the references to 'test' in the pom file of apache-james-backends-cassandra. I attached it here. Rebuild with this POM file and you should get past it. The thing is, you don't need to do that if you build on a Lin

Re: Setup and build issues

2018-12-06 Thread Garry Hurley
Yeah, we are there too. Docker is apparently only used for testing. What errors are you hitting? I probably hit the same ones and fixed them. Worst case scenario, join the developer list as well and vote on the “are we ready for a release?” questions. That is what one of the devs told me. Sent

Re: Setup and build issues

2018-12-06 Thread Bill Warner
Thank you! I got past my classpath issue; but now I have many cassandra errors. I'm wondering if there is an existing build and config that is closer to what I'm looking for, but I will soldier on if there isn't! On 12/5/18 6:07 PM, Garry Hurley wrote: That is an easy fix. You have to download

Re: run.sh vs james start, run james as service best practice

2018-12-06 Thread Raphael OUAZANA
Hi, On Debian you should probably safely use this script: https://github.com/apache/james-project/blob/master/dockerfiles/packaging/guice/cassandra/scripts/james.service And this one on RHEL: https://github.com/apache/james-project/blob/master/dockerfiles/packaging/guice/cassandra/scripts/james.s