[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakarta.ee-spec.committee] Possible issue with Servlet spec PR
|
Correct, it needs to be changed to remove the addition of the annotation. There can’t be an addition that impacts the signatures, and the TCK run has to be using the candidate 4.0.3 staging release.
> On Aug 20, 2019, at 10:19 AM, Alasdair Nottingham <alasdair.nottingham@xxxxxxxxx> wrote:
>
> Hi,
>
> On the jakartaee-tck-dev mail list Scott Marlow is having issues getting a pass on the servlet API due to the addition of the @Deprecated annotation to the ServletRequest.getRealPath method: https://www.eclipse.org/lists/jakartaee-tck-dev/msg00230.html
>
> It was added in this commit: https://github.com/eclipse-ee4j/servlet-api/commit/7ee900a78b2679bf7c9a4c83633eda36acc657f3
>
> The Servlet spec PR has this comment:
>
> https://github.com/eclipse-ee4j/servlet-api/issues/262#issuecomment-521094783
>
> which Arjan said had been done, but I can’t see sign in the output of the signature verification tests being run. Since they are breaking I’m assuming that the signature verification tests either haven’t run, or weren’t run on the Jakarta Servlet API, but on the Java EE Servlet API.
>
> Not sure what the right thing to do is, but right now I don’t think servlet should be approved without undoing the addition of @Deprecated.
>
> Thoughts?
> Alasdair
> _______________________________________________
> jakarta.ee-spec.committee mailing list
> jakarta.ee-spec.committee@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
