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 spoolmanager.xml file, an smtpserver.xml file and a mailetcontainer.xml file (to name a few). You basically go to the corresponding sections in the old file and copy them to the new counterpart. That sounds easier than it is.
What does not come out are the changes in formatting of the xml. For example, in the processors section of the config.xml, you might have the following: <processor name=“Finished”/> and it is perfectly acceptable. Not so in 3.x. Now, it is more like: <processor state=“Finished” enableJmx=“true”> <mailet match=“All” class=“Null”/> </processor> Now, the enableJmx is optional as far as I can tell, but it will throw an error if you do not explicitly define a mailet in the processor. Sent from my iPhone > On Mar 19, 2019, at 5:02 PM, cryptearth <cryptea...@cryptearth.de> wrote: > > 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 the active main branch. > > Matt > >> Am 19.03.2019 um 21:58 schrieb A. Rothman: >> Hi, >> >> Is there a migration guide or any official or unofficial references for >> upgrading from 2.3.x to 3.x? >> >> Also, is 3.x stable in terms of database, data formats and >> configuration? i.e. is it safe to upgrade now without worrying about >> additional data migrations in the near future? >> >> Thanks, and it's great to see all the recent work on James after years >> of being dormant - kudos to all involved! >> >> Amichai >> >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org >> For additional commands, e-mail: server-user-h...@james.apache.org >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org > For additional commands, e-mail: server-user-h...@james.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org
