Re: [DISCUSS] CXF 3.5.x and beyond

2021-09-24 Thread Andriy Redko
I will check it out shortly, thanks a lot Jim!

Best Regards,
Andriy Redko

JM> @Andriy,  I finally get time to back on this task. I just sent a PR as you
JM> suggested : https://github.com/apache/cxf/pull/855
JM> and labeled it with "work-in-progress".

JM> If anyone has any idea to improve this, feel free to comment, update or
JM> replace it with another PR.

JM> Thanks,
JM> Jim

JM> On Wed, Sep 8, 2021 at 8:55 AM Jim Ma  wrote:



>> On Tue, Sep 7, 2021 at 4:56 AM Andriy Redko  wrote:

>>> Hey Jim,

>>> No, we don't have a branch just yet, primarily because we depend on the
>>> few
>>> snapshots in 3.5.0/master.

>>> @Colm do you have an idea regarding xmlschema 2.3.0 release timelines?
>>> @Dan do you have an idea regarding neethi 3.2.0 release timelines?

>>> At worst, you could create a new branch for this feature, or submit a
>>> pull request against master which we should be able to re-target later
>>> against the right branch (should be easy). What do you think?


>> This is a good idea. I'll send a PR against the master, and later we can
>> decide the place to merge.
>> Thanks, Andriy.




>>> Best Regards,
>>> Andriy Redko

>>> JM> Thanks for more updates , Andriy.
>>> JM> Is there  a place/workspace branch, I can send a PR for this change?

>>> JM> On Fri, Sep 3, 2021 at 9:20 PM Andriy Redko  wrote:

>>> >> Hey Jim,

>>> >> Thanks a lot for taking the lead on this one. Just want to chime in on
>>> a
>>> >> few points. Indeed, as
>>> >> per previous discussion in this thread, it seems like it make sense to
>>> >> provide only the subset
>>> >> of shaded modules with Jakarta namespace. Also, it was confirmed
>>> yesterday
>>> >> that Spring Framework
>>> >> 6 milestones will be available in November this year but the first
>>> >> snapshots will be out in late
>>> >> September / early October, looks pretty promising. One **unexpected**
>>> part
>>> >> of the announcement
>>> >> is JDK17 baseline for Spring Framework & Co, that could be a bummer
>>> but I
>>> >> have the feeling that
>>> >> it will be lowered to JDK11. Thank you.

>>> >> Best Regards,
>>> >> Andriy Redko


>>> >> JM> Good point, Romain. We need to look at what to do to make sure all
>>> >> JM> artifacts are included and transformed if this becomes a cxf
>>> module.

>>> >> JM> BTW, Spring 6 GA  supports jakarta ee9 will come in Q4 2022 :
>>> >> JM>
>>> >>
>>> https://spring.io/blog/2021/09/02/a-java-17-and-jakarta-ee-9-baseline-for-spring-framework-6

>>> >> JM> On Fri, Sep 3, 2021 at 6:20 PM Romain Manni-Bucau <
>>> >> rmannibu...@gmail.com>
>>> >> JM> wrote:




>>> >> >> Le ven. 3 sept. 2021 à 11:30, Jim Ma  a
>>> écrit :



>>> >> >>> On Wed, Aug 25, 2021 at 9:39 PM Romain Manni-Bucau <
>>> >> rmannibu...@gmail.com>
>>> >> >>> wrote:



>>> >>  Le mer. 25 août 2021 à 13:39, Jim Ma  a
>>> écrit :



>>> >> > On Fri, Aug 20, 2021 at 2:10 PM Romain Manni-Bucau <
>>> >> > rmannibu...@gmail.com> wrote:



>>> >> >> Le jeu. 19 août 2021 à 22:45, Andriy Redko  a
>>> >> >> écrit :

>>> >> >>> Hi Romain,

>>> >> >>> Sorry for the delayed response. I have been thinking about your
>>> >> (and
>>> >> >>> Jim) suggestions
>>> >> >>> and came to surprising conclusion: do we actually need to
>>> >> officially
>>> >> >>> release anything
>>> >> >>> to shade/overwrite javax <-> jakarta? Generally, we could shade
>>> >> >>> Spring or/and any other
>>> >> >>> dependency but we would certainly not bundle it as part of CXF
>>> >> >>> distribution (I hope you
>>> >> >>> would agree), so not really useful unless we publish them. As
>>> such,
>>> >> >>> probably the best
>>> >> >>> interim solution is to document what it takes to shade CXF
>>> (javax
>>> >> <->
>>> >> >>> jakarta) and let
>>> >> >>> the end users (application/service developers) use that when
>>> >> needed?
>>> >> >>> In this case
>>> >> >>> basically CXF, Spring, Geronimo, Swagger, ... would follow the
>>> same
>>> >> >>> shading rules. At
>>> >> >>> least, we could start with that (documenting the shading
>>> process)
>>> >> and
>>> >> >>> likely get some
>>> >> >>> early feedback while working on full-fledged support? WDYT?



>>> >> >> This is what is done and makes it hard for nothing to
>>> maintain/fix -
>>> >> >> dont even look at tomee solution for shading please ;) - IMHO.
>>> >> >> Being said it costs nothing to cxf to produce jakarta jars,
>>> that it
>>> >> >> makes it ee 9 compliant and more consistent for all but spring
>>> >> usage (ee
>>> >> >> integrators, plain tomcat 10 users etc...), I think it is worth
>>> >> doing it,
>>> >> >> at minimum.
>>> >> >> At least a jakarta jaxrs (over jakarta servlet) bundle would be
>>> a
>>> >> good
>>> >> >> progress, not sure jaxws and other parts would be helpful since
>>> >> they tend
>>> >> >> to be in maintainance mode from what I saw.
>>> >> >> So IMHO the best is a 

Re: [DISCUSS] CXF 3.5.x and beyond

2021-09-24 Thread Jim Ma
@Andriy,  I finally get time to back on this task. I just sent a PR as you
suggested : https://github.com/apache/cxf/pull/855
and labeled it with "work-in-progress".

If anyone has any idea to improve this, feel free to comment, update or
replace it with another PR.

Thanks,
Jim

On Wed, Sep 8, 2021 at 8:55 AM Jim Ma  wrote:

>
>
> On Tue, Sep 7, 2021 at 4:56 AM Andriy Redko  wrote:
>
>> Hey Jim,
>>
>> No, we don't have a branch just yet, primarily because we depend on the
>> few
>> snapshots in 3.5.0/master.
>>
>> @Colm do you have an idea regarding xmlschema 2.3.0 release timelines?
>> @Dan do you have an idea regarding neethi 3.2.0 release timelines?
>>
>> At worst, you could create a new branch for this feature, or submit a
>> pull request against master which we should be able to re-target later
>> against the right branch (should be easy). What do you think?
>>
>
> This is a good idea. I'll send a PR against the master, and later we can
> decide the place to merge.
> Thanks, Andriy.
>
>
>
>>
>> Best Regards,
>> Andriy Redko
>>
>> JM> Thanks for more updates , Andriy.
>> JM> Is there  a place/workspace branch, I can send a PR for this change?
>>
>> JM> On Fri, Sep 3, 2021 at 9:20 PM Andriy Redko  wrote:
>>
>> >> Hey Jim,
>>
>> >> Thanks a lot for taking the lead on this one. Just want to chime in on
>> a
>> >> few points. Indeed, as
>> >> per previous discussion in this thread, it seems like it make sense to
>> >> provide only the subset
>> >> of shaded modules with Jakarta namespace. Also, it was confirmed
>> yesterday
>> >> that Spring Framework
>> >> 6 milestones will be available in November this year but the first
>> >> snapshots will be out in late
>> >> September / early October, looks pretty promising. One **unexpected**
>> part
>> >> of the announcement
>> >> is JDK17 baseline for Spring Framework & Co, that could be a bummer
>> but I
>> >> have the feeling that
>> >> it will be lowered to JDK11. Thank you.
>>
>> >> Best Regards,
>> >> Andriy Redko
>>
>>
>> >> JM> Good point, Romain. We need to look at what to do to make sure all
>> >> JM> artifacts are included and transformed if this becomes a cxf
>> module.
>>
>> >> JM> BTW, Spring 6 GA  supports jakarta ee9 will come in Q4 2022 :
>> >> JM>
>> >>
>> https://spring.io/blog/2021/09/02/a-java-17-and-jakarta-ee-9-baseline-for-spring-framework-6
>>
>> >> JM> On Fri, Sep 3, 2021 at 6:20 PM Romain Manni-Bucau <
>> >> rmannibu...@gmail.com>
>> >> JM> wrote:
>>
>>
>>
>>
>> >> >> Le ven. 3 sept. 2021 à 11:30, Jim Ma  a
>> écrit :
>>
>>
>>
>> >> >>> On Wed, Aug 25, 2021 at 9:39 PM Romain Manni-Bucau <
>> >> rmannibu...@gmail.com>
>> >> >>> wrote:
>>
>>
>>
>> >>  Le mer. 25 août 2021 à 13:39, Jim Ma  a
>> écrit :
>>
>>
>>
>> >> > On Fri, Aug 20, 2021 at 2:10 PM Romain Manni-Bucau <
>> >> > rmannibu...@gmail.com> wrote:
>>
>>
>>
>> >> >> Le jeu. 19 août 2021 à 22:45, Andriy Redko  a
>> >> >> écrit :
>>
>> >> >>> Hi Romain,
>>
>> >> >>> Sorry for the delayed response. I have been thinking about your
>> >> (and
>> >> >>> Jim) suggestions
>> >> >>> and came to surprising conclusion: do we actually need to
>> >> officially
>> >> >>> release anything
>> >> >>> to shade/overwrite javax <-> jakarta? Generally, we could shade
>> >> >>> Spring or/and any other
>> >> >>> dependency but we would certainly not bundle it as part of CXF
>> >> >>> distribution (I hope you
>> >> >>> would agree), so not really useful unless we publish them. As
>> such,
>> >> >>> probably the best
>> >> >>> interim solution is to document what it takes to shade CXF
>> (javax
>> >> <->
>> >> >>> jakarta) and let
>> >> >>> the end users (application/service developers) use that when
>> >> needed?
>> >> >>> In this case
>> >> >>> basically CXF, Spring, Geronimo, Swagger, ... would follow the
>> same
>> >> >>> shading rules. At
>> >> >>> least, we could start with that (documenting the shading
>> process)
>> >> and
>> >> >>> likely get some
>> >> >>> early feedback while working on full-fledged support? WDYT?
>>
>>
>>
>> >> >> This is what is done and makes it hard for nothing to
>> maintain/fix -
>> >> >> dont even look at tomee solution for shading please ;) - IMHO.
>> >> >> Being said it costs nothing to cxf to produce jakarta jars,
>> that it
>> >> >> makes it ee 9 compliant and more consistent for all but spring
>> >> usage (ee
>> >> >> integrators, plain tomcat 10 users etc...), I think it is worth
>> >> doing it,
>> >> >> at minimum.
>> >> >> At least a jakarta jaxrs (over jakarta servlet) bundle would be
>> a
>> >> good
>> >> >> progress, not sure jaxws and other parts would be helpful since
>> >> they tend
>> >> >> to be in maintainance mode from what I saw.
>> >> >> So IMHO the best is a shade/relocation in the parent to deliver
>> a
>> >> >> jakarta artifact for all module + a few jakarta bom. But if too
>> >> much -
>> >> 

Re: Releases next week?

2021-09-24 Thread Andriy Redko
Hello Colm,

Sure, no objections (from my side), let's do 3.3.x and 3.4.x, thank you!

Best Regards,
Andriy Redko

COh> Hey Andriy,

COh> If possible I'd like a little more time on 3.5.0 (a month?). I'd love
COh> to get new major releases of XML Security and WSS4J out. But we could
COh> get the 3.4.x + 3.3.x patch releases out now, because it's been a
COh> while since the last releases.

COh> Colm.

COh> On Fri, Sep 24, 2021 at 3:42 AM Andriy Redko  wrote:

>> Hey guys,

>> It seems like we are all set to release 3.3.12, 3.4.5 ... and 3.5.0 next 
>> week! There is one issue [1] which
>> is already fixed but I have asked the user to reconfirm with latest 
>> 3.4.5-SNAPSHOT, should be resolved in a
>> few days (hopefully). Also, for 3.5.0, all SNAPSHOTs have been replaced with 
>> release versions (thanks Colm
>> and Dan for pulling that off), so we should be all set to have releases next 
>> week (a bit late than planned).
>> Thank you!

>> Best Regards,
>> Andriy Redko

>> [1] https://issues.apache.org/jira/browse/CXF-8597

>> DK> I guess the question is:  Which releases?

>> DK> 3.4.5 and 3.3.12 are a certain YES!

>> DK> The question I have is whether 3.5.0 is ready for release next week or 
>> should we wait another couple weeks to double check the Java17 stuff 
>> assuming java17 release happens tomorrow as planned.

>> DK> Dan



>> >> On Sep 13, 2021, at 11:48 AM, Colm O hEigeartaigh  
>> >> wrote:

>> >> I believe we are well overdue getting new releases out, how does early
>> >> next week sound?

>> >> Colm.



Re: Releases next week?

2021-09-24 Thread Jim Ma
+1 for 3.4.5 and 3.3.12 release.


On Fri, Sep 24, 2021 at 1:41 PM Colm O hEigeartaigh 
wrote:

> Hey Andriy,
>
> If possible I'd like a little more time on 3.5.0 (a month?). I'd love
> to get new major releases of XML Security and WSS4J out. But we could
> get the 3.4.x + 3.3.x patch releases out now, because it's been a
> while since the last releases.
>
> Colm.
>
> On Fri, Sep 24, 2021 at 3:42 AM Andriy Redko  wrote:
> >
> > Hey guys,
> >
> > It seems like we are all set to release 3.3.12, 3.4.5 ... and 3.5.0 next
> week! There is one issue [1] which
> > is already fixed but I have asked the user to reconfirm with latest
> 3.4.5-SNAPSHOT, should be resolved in a
> > few days (hopefully). Also, for 3.5.0, all SNAPSHOTs have been replaced
> with release versions (thanks Colm
> > and Dan for pulling that off), so we should be all set to have releases
> next week (a bit late than planned).
> > Thank you!
> >
> > Best Regards,
> > Andriy Redko
> >
> > [1] https://issues.apache.org/jira/browse/CXF-8597
> >
> > DK> I guess the question is:  Which releases?
> >
> > DK> 3.4.5 and 3.3.12 are a certain YES!
> >
> > DK> The question I have is whether 3.5.0 is ready for release next week
> or should we wait another couple weeks to double check the Java17 stuff
> assuming java17 release happens tomorrow as planned.
> >
> > DK> Dan
> >
> >
> >
> > >> On Sep 13, 2021, at 11:48 AM, Colm O hEigeartaigh <
> cohei...@apache.org> wrote:
> >
> > >> I believe we are well overdue getting new releases out, how does early
> > >> next week sound?
> >
> > >> Colm.
> >
>