You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by "A. Rothman" <am...@amichais.net> on 2019/03/19 20:58:10 UTC
Migration from James 2.3
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-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: Migration from James 2.3
Posted by Garry Hurley <ga...@gmail.com>.
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 <cr...@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-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-user-help@james.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: Migration from James 2.3
Posted by cryptearth <cr...@cryptearth.de>.
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-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: Call for vote: MIME4J 0.8.3
Posted by Duc Tran <dt...@linagora.com>.
I agree with the release
+1
Tran Tien Duc
> Hi,
>
> I would like to propose the 0.8.3 release of the Apache MIME4J library.You can see changes proposed to the website at the occasion
> of that release, as well as communication on this GitHub pull request:
> https://github.com/linagora/james-project/pull/2243
>
> - The maven release staged inhttp://repository.apache.org/ as the
> artifact #1043
> - 0.8.3 sources and binaries are uploaded on Apache dist
> https://dist.apache.org/repos/dist/release/james/mime4j/0.8.3/
>
> Changes includes in this release:
>
> - MIME4J-270: Using "alternative" as default subtype
> - MIME4J-263: decoding encoded words with empty encoded-text
> - MIME4J-279: Fixed JavaDoc errors to comply with Java8
> - MIME4J-280: Improve exception handling
> - MIME4J-283: DecoderUtil performance fix
>
> Voting rules:
> - This is a majority approval: this release may not be vetoed.
> - A quorum of 3 binding votes is required
> - The vote starts at Tuesday 14th of March 2019, 5pm UTC
> - The vote ends at Tuesday 21th of March 2019, 5pm UTC
>
> You can answer to it just with +1 and -1. Down-votes may be motivated.
>
> Cheers,
>
> Benoit Tellier
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
> For additional commands, e-mail: server-dev-h...@james.apache.org
>
Re: Call for vote: Apache James 3.3.0
Posted by Rémi Kowalski <re...@gmail.com>.
+1
Le mer. 20 mars 2019 à 10:04, Gautier DI FOLCO <gd...@linagora.com> a
écrit :
> +1
>
> Le 20/03/2019 à 08:27, Duc Tran a écrit :
> > Hi, I agree with the release
> >
> > +1
> >
> > Regards,
> > Tran Tien Duc
> >> Hi,
> >>
> >> I would like to propose the 3.3.0 release of the Apache James server.
> >> You can see changes proposed to the website at the occasion
> >> of that release, as well as communication on this GitHub pull
> >> request:https://github.com/linagora/james-project/pull/2169
> >>
> >> You can find:
> >>
> >> - The maven release staged inhttp://repository.apache.org/ as the
> >> artifact #1042
> >> - 3.3.0 sources and binaries are uploaded on Apache dist. Please note
> >> that we included JPA Guice and JPA SMTP guice.
> >> - The changelog for
> >> 3.3.0:
> https://github.com/linagora/james-project/blob/9706e15a627ee0cb9065980899f5e817d2817057/CHANGELOG.md
> >>
> >> - The compatibility instructions/upgrade
> >> recommendation:
> https://github.com/linagora/james-project/blob/9706e15a627ee0cb9065980899f5e817d2817057/upgrade-instructions.md
> >>
> >>
> >> Voting rules:
> >> - This is a majority approval: this release may not be vetoed.
> >> - A quorum of 3 binding votes is required
> >> - The vote starts at Monday 18th of March 2019, 9pm00 UTC
> >> - The vote ends at Monday 25th of March 2019, 9pm00 UTC
> >>
> >> You can answer to it just with +1 and -1. Down-votes may be motivated.
> >>
> >> Cheers,
> >>
> >> Antoine
> >>
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
Re: Call for vote: Apache James 3.3.0
Posted by Gautier DI FOLCO <gd...@linagora.com>.
+1
Le 20/03/2019 à 08:27, Duc Tran a écrit :
> Hi, I agree with the release
>
> +1
>
> Regards,
> Tran Tien Duc
>> Hi,
>>
>> I would like to propose the 3.3.0 release of the Apache James server.
>> You can see changes proposed to the website at the occasion
>> of that release, as well as communication on this GitHub pull
>> request:https://github.com/linagora/james-project/pull/2169
>>
>> You can find:
>>
>> - The maven release staged inhttp://repository.apache.org/ as the
>> artifact #1042
>> - 3.3.0 sources and binaries are uploaded on Apache dist. Please note
>> that we included JPA Guice and JPA SMTP guice.
>> - The changelog for
>> 3.3.0:https://github.com/linagora/james-project/blob/9706e15a627ee0cb9065980899f5e817d2817057/CHANGELOG.md
>>
>> - The compatibility instructions/upgrade
>> recommendation:https://github.com/linagora/james-project/blob/9706e15a627ee0cb9065980899f5e817d2817057/upgrade-instructions.md
>>
>>
>> Voting rules:
>> - This is a majority approval: this release may not be vetoed.
>> - A quorum of 3 binding votes is required
>> - The vote starts at Monday 18th of March 2019, 9pm00 UTC
>> - The vote ends at Monday 25th of March 2019, 9pm00 UTC
>>
>> You can answer to it just with +1 and -1. Down-votes may be motivated.
>>
>> Cheers,
>>
>> Antoine
>>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Call for vote: Apache James 3.3.0
Posted by Duc Tran <dt...@linagora.com>.
Hi, I agree with the release
+1
Regards,
Tran Tien Duc
> Hi,
>
> I would like to propose the 3.3.0 release of the Apache James server.
> You can see changes proposed to the website at the occasion
> of that release, as well as communication on this GitHub pull
> request:https://github.com/linagora/james-project/pull/2169
>
> You can find:
>
> - The maven release staged inhttp://repository.apache.org/ as the
> artifact #1042
> - 3.3.0 sources and binaries are uploaded on Apache dist. Please note
> that we included JPA Guice and JPA SMTP guice.
> - The changelog for
> 3.3.0:https://github.com/linagora/james-project/blob/9706e15a627ee0cb9065980899f5e817d2817057/CHANGELOG.md
> - The compatibility instructions/upgrade
> recommendation:https://github.com/linagora/james-project/blob/9706e15a627ee0cb9065980899f5e817d2817057/upgrade-instructions.md
>
> Voting rules:
> - This is a majority approval: this release may not be vetoed.
> - A quorum of 3 binding votes is required
> - The vote starts at Monday 18th of March 2019, 9pm00 UTC
> - The vote ends at Monday 25th of March 2019, 9pm00 UTC
>
> You can answer to it just with +1 and -1. Down-votes may be motivated.
>
> Cheers,
>
> Antoine
>
>
>