Re: Migration from James 2.3

2019-03-19 Thread Garry Hurley
There is a migration guide, but it is very skeletal. It doesn’t work as well with 3.1 and beyond as it did for the 3.0 betas. The thing you have to realize is that the config.xml file has been separated into its relevant sections, with each having its own XML file. For example, there is now a

Re: Migration from James 2.3

2019-03-19 Thread cryptearth
Hey Amichai, I can't tell you about upgrading, but as there're some 3.x builds (3.0, 3.1, 3.2, there's also a 3.3 tag on github, but it isn't its own branch), as long as you use one of those "final stable" builds, yea, it's final and stable. Changes are only to be expected if you keep follow