Sure, but when updating the javamail package, you will be providing
compatibility aliases for the old maven coordinates using %mvn_alias and
compatibility symlinks for the old filename using %mvn_file in order to not
break dependent packages, right? Right? ;-)
Unless a package somehow is not using
Hey Mat,
On further investigation, the compatibility changes that require
attention are made in javamail 1.6.3 and later, see:
https://eclipse-ee4j.github.io/mail/docs/COMPAT.txt
The maven coordinates are changed, generally javax -> jakarta. This
also affects the osgi provides.
Regards,
Jie Ka
Thanks for the insight and link Fabio and Mat. I'll look into the
compatibility and verify if any changes need to be made and if so,
contact the maintainers. Following a week or two for responses, I'll
submit an update for rawhide.
Regards,
Jie Kang
Senior Software Engineer, Red Hat Canada
On Th
On Wed, 1 Jul 2020 at 15:05, Fabio Valentini wrote:
> On Mon, Jun 29, 2020 at 4:06 PM Jie Kang wrote:
> >
> > Hi all,
> >
> > javamail ursine is using version 1.5.2 while there are some module
> > streams at 1.6.x
> >
> > The upstream project also moved to the eclipse foundation and these
> > 1.
On Mon, Jun 29, 2020 at 4:06 PM Jie Kang wrote:
>
> Hi all,
>
> javamail ursine is using version 1.5.2 while there are some module
> streams at 1.6.x
>
> The upstream project also moved to the eclipse foundation and these
> 1.6.x releases have different exports for OSGi, making an update to
> them
Hi all,
javamail ursine is using version 1.5.2 while there are some module
streams at 1.6.x
The upstream project also moved to the eclipse foundation and these
1.6.x releases have different exports for OSGi, making an update to
them potentially breaking for users.
I'd like to update ursine to 1.
