[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakartaee-platform-dev] [External] : Re: Pushing RCx or Mx to maven central
|
On 1/13/22 12:06 PM, Emily Jiang via jakartaee-platform-dev wrote:
Hi Mark,
Can you explain why you think the artifacts should not be pushed to
maven central? One of the reasons for pushing the artifacts to maven
central is to make it easier for others to access the artifacts and then
provide feedback. If all of the artifacts are in staging, only the
projects under EE4J can access them freely, which creates a barrier for
other projects to obtain these artifacts.
Some of these RC/M spec project builds may depend on final builds of
other spec projects. Final build of the spec project cannot be published
to maven central (or basically anywhere from where it cannot be
immediately deleted should the request for it come) with out prior
approvals from EF (release review process) and spec committee (ballot).
What is the point of pushing knwown-to-be broken for some undefined
period of time broken RC/M builds to maven central?
Should anyone have a need to use artifacts from the staging repo in his
project, adding the staging repo to his pom is relatively easy to find
and simple thing to do.
thanks,
--lukas
Thanks
Emily
On Thu, Jan 13, 2022 at 8:12 AM Mark Thomas <markt@xxxxxxxxxx
<mailto:markt@xxxxxxxxxx>> wrote:
For Servlet, Pages, EL, WebSocket: No.
Implementations should use the staging repository if they want
access to
non-final release artifacts.
Mark
On 12/01/2022 23:12, Emily Jiang via jakartaee-platform-dev wrote:
> At the moment, some specs push RCx or Mx to maven central, which is
> great so that implementations can easily pick them up and provide
> feedback if anything is not working. However, not all specs
follow this
> approach. Can we get the following specs to push their latest Mx
or RCx
> to maven central so that implementations can easily consume them?
Open
> Liberty would like to consume the artifacts as soon as possible
so that
> we can provide timely feedback if we find any issues.
>
> * authentication 3.0
> * authorization 2.1
> * concurrency 3.0
> * connectors 2.1
> * expression language 5.0
> * faces 4.0
> * jsonp 2.1
> * jsonb 3.0
> * jstl 3.0
> * messaging 3.1
> * pages 3.1
> * persistence 3.1
> * restfulWS 3.1
> * security 3.0
> * servlet 6.0
> * websocket 2.1
>
>
> Your help is greatly appreciated!
> --
> Thanks
> Emily
>
>
> _______________________________________________
> jakartaee-platform-dev mailing list
> jakartaee-platform-dev@xxxxxxxxxxx
<mailto:jakartaee-platform-dev@xxxxxxxxxxx>
> To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
<https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev__;!!ACWV5N9M2RV99hQ!bvJ5yq_ICNrO7Qo9vE23jE1ShXJEaCLmt1BNr25Kr1YNe1W2gFCKpbLA06wuvx3Axd8$>
>
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
<mailto:jakartaee-platform-dev@xxxxxxxxxxx>
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
<https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev__;!!ACWV5N9M2RV99hQ!bvJ5yq_ICNrO7Qo9vE23jE1ShXJEaCLmt1BNr25Kr1YNe1W2gFCKpbLA06wuvx3Axd8$>
--
Thanks
Emily
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev__;!!ACWV5N9M2RV99hQ!bvJ5yq_ICNrO7Qo9vE23jE1ShXJEaCLmt1BNr25Kr1YNe1W2gFCKpbLA06wuvx3Axd8$
